Simone Di Cola comments

Results 35 comments of


                                            Simone Di Cola

"Bootjob" task doesn't work in remote cluster

This is still an open problem.

secure query component with a sidecar

I have hit exactly the same problem. I am going to track this issue. Thanks for the effort!

secure query component with a sidecar

here an example of side car I use in all the other services in my cluster: - image: quay.io/oauth2-proxy/oauth2-proxy:v6.1.1 name: oauth2-proxy ports: - containerPort: 4180 env: - name: KEYCLOAK_CLIENT_SECRET valueFrom:...

Introduce `app upgrade` command

@oren-codefresh is there any update with this? How one can currently update an existing repo from a CI pipeline when a new docker image has been built?

Support helm charts instead of kustomize as part of `bootstrap` command

@Seji64 I can confirm that the approach described by @patrickleet works with that version. I just tried it now with minikube.

Override option for entrypoint

Hi all, I am struggling to understand how to override the entry point of a docker image. Has the functionality been implemented? @bikash001 @cristianrgreco

Override option for entrypoint

I have 0 idea how to implement this. Sorry @cristianrgreco

Changing of underlying type broke pulumi-aws elasticache.Cluster snapshotArn

same here. I am stuck!

tls email not populated

just to add to this: the same applies to everything under ingress in jx-requirements.yaml. An example is externalDNS, which defaults to false even if main.tf says true.

tls email not populated

Strange. Just created 3 new clusters and I see the same behaviour. I can only see this: ingress: domain: data.property.xyz externalDNS: true namespaceSubDomain: -jx. tls: email: "" enabled: true production:...