We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should probably have a sleep or poll loop after CRDs are installed until API is settled. Happens on GKE every other time.
kubectl --context="arkadi-gke.smoke-arkadi-gcp01.superhub.io" --namespace="cert-manager" apply -f https://raw.githubusercontent.com/jetstack/cert-manager/release-0.9/deploy/manifests/00-crds.yaml customresourcedefinition.apiextensions.k8s.io/certificates.certmanager.k8s.io created customresourcedefinition.apiextensions.k8s.io/certificaterequests.certmanager.k8s.io created customresourcedefinition.apiextensions.k8s.io/challenges.certmanager.k8s.io created customresourcedefinition.apiextensions.k8s.io/clusterissuers.certmanager.k8s.io created customresourcedefinition.apiextensions.k8s.io/issuers.certmanager.k8s.io created customresourcedefinition.apiextensions.k8s.io/orders.certmanager.k8s.io created helm --kube-context="arkadi-gke.smoke-arkadi-gcp01.superhub.io" --tiller-namespace="kube-system" list -q --namespace cert-manager | grep -E '^cert-manager$' || \ helm --kube-context="arkadi-gke.smoke-arkadi-gcp01.superhub.io" --tiller-namespace="kube-system" install charts/cert-manager \ --name cert-manager \ --namespace cert-manager \ --replace \ --wait \ --values values.yaml \ \ --version v0.9.1 Error: Could not get apiVersions from Kubernetes: unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server is currently unable to handle the request make[1]: Leaving directory '/workspace/repo/components/cert-manager' --- make[1]: *** [Makefile:46: install] Error 1 2019/10/25 19:05:28 State lifecycle operation `deploy` log appended: /usr/bin/make [deploy] (components/cert-manager): exit status 2\n--- stdout:\nmake[1]: Entering dire... 2019/10/25 19:05:28 Component `cert-manager` failed to deploy: /usr/bin/make [deploy] (components/cert-manager): exit status 2 2019/10/25 19:05:28 State component `cert-manager` status: error 2019/10/25 19:05:28 State lifecycle phase `cert-manager` status: error 2019/10/25 19:05:28 State stack status: incomplete 2019/10/25 19:05:28 State lifecycle operation `deploy` status: error 2019/10/25 19:05:28 Wrote state `.hub/arkadi-gke.smoke-arkadi-gcp01.superhub.io.state` 2019/10/25 19:05:28 Wrote state `gs://agilestacks-smoke-arkadi-gcp01-superhub-io/arkadi-gke.smoke-arkadi-gcp01.superhub.io/hub/gke/hub.state` make: *** [Makefile:58: deploy] Error 1 ===> arkadi-gke [14] stackInstance update success ===> arkadi-gke [14] stackInstance update success ===> arkadi-gke [14] stackInstance deploy fail ===> arkadi-gke [14] stackInstance update success gmake: *** [Makefile:259: deploy-instance-k8s-gke] Error 2
The text was updated successfully, but these errors were encountered:
Cert-manager wait for CRDs to settle #310
51ba2fa
This is going to be fixed in Helm 2.16.4 helm/helm#7196
Sorry, something went wrong.
Helm 2.16.4 released.
helm/helm#7797
helm/helm#7812
Helm 2.16.6 released.
arkadijs
No branches or pull requests
Should probably have a sleep or poll loop after CRDs are installed until API is settled. Happens on GKE every other time.
The text was updated successfully, but these errors were encountered: