Skip to content
New issue

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

UPGRADE FAILED: no ServiceAccount with the name #677

Closed
Antiarchitect opened this issue Jun 25, 2018 · 1 comment
Closed

UPGRADE FAILED: no ServiceAccount with the name #677

Antiarchitect opened this issue Jun 25, 2018 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@Antiarchitect
Copy link

Antiarchitect commented Jun 25, 2018

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

What happened:
Trying to deploy cert-manager + ClusterIssuer + nginx-ingress to GKE cluster via Helm. Result:
Error: UPGRADE FAILED: no ServiceAccount with the name "cert-manager-*****" found.

What you expected to happen:
No errors when helm upgrade ...

How to reproduce it (as minimally and precisely as possible):
Get gke cluster v1.10.4-gke.0, create chart, attach cert-manager to requirements.yaml and deploy it.

Anything else we need to know?:
There is actually service account with this name in default namespace.
The minimal configuration of cert-manager helm chart:

cert-manager:
  ingressShim:
    defaultIssuerName: letsencrypt
    defaultIssuerKind: ClusterIssuer

Environment:
kubectl version:
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.4", GitCommit:"5ca598b4ba5abb89bb773071ce452e33fb66339d", GitTreeState:"clean", BuildDate:"2018-06-06T08:13:03Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10+", GitVersion:"v1.10.4-gke.0", GitCommit:"c08fe9548257472151a8fa298bd6c3e9ea1b8c09", GitTreeState:"clean", BuildDate:"2018-06-06T11:34:07Z", GoVersion:"go1.9.3b4", Compiler:"gc", Platform:"linux/amd64"}

helm version:
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}

Chart version: 0.3.2 attached in requirements.

@jetstack-bot jetstack-bot added the kind/bug Categorizes issue or PR as related to a bug. label Jun 25, 2018
@Antiarchitect
Copy link
Author

Antiarchitect commented Jun 27, 2018

Sorry guys, not your issue. It's a venerable bug in Helm I suppose: helm/helm#1193

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants