You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Missing insecure-skip-tls-verify flag in command jx gitops helm release, so jx gitops helm release could not be used in minikube cluster for local development/tryout.
Command jx gitops helm release internally runs helm push command, however jx gitops helm release does not support the flag like helm push --insecure-skip-tls-verify does.
This bug causes error tls: failed to verify certificate: x509: certificate is valid for ingress.local.
If flag would be added, docker-registry-jx could be used to store application promotion charts instead of the bucketrepo-jx.
app pipeline does not work due to error tls: failed to verify certificate: x509: certificate is valid for ingress.local
to fix the error internal helm push command triggered by jx gitops helm release must use flag --insecure-skip-tls-verify.
Missing
insecure-skip-tls-verify
flag in commandjx gitops helm release
, sojx gitops helm release
could not be used in minikube cluster for local development/tryout.Command
jx gitops helm release
internally runshelm push
command, howeverjx gitops helm release
does not support the flag likehelm push --insecure-skip-tls-verify
does.This bug causes error
tls: failed to verify certificate: x509: certificate is valid for ingress.local
.If flag would be added, docker-registry-jx could be used to store application promotion charts instead of the bucketrepo-jx.
jx-requirements.yml
cluster:
chartKind: oci
chartRepository: docker-registry-jx.A.B.C.D.nip.io
app pipeline:
app pipeline does not work due to error
tls: failed to verify certificate: x509: certificate is valid for ingress.local
to fix the error internal
helm push
command triggered byjx gitops helm release
must use flag--insecure-skip-tls-verify
.working app pipeline:
The text was updated successfully, but these errors were encountered: