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

Helm failure on real cluster #108

Closed
devdattakulkarni opened this issue Oct 31, 2018 · 2 comments
Closed

Helm failure on real cluster #108

devdattakulkarni opened this issue Oct 31, 2018 · 2 comments

Comments

@devdattakulkarni
Copy link
Contributor

devdattakulkarni commented Oct 31, 2018

When trying with a real cluster we were seeing helm failure where helm was not able to install a chart.

It got fixed after running following command:
kubectl.sh create clusterrolebinding permissive-binding --clusterrole=cluster-admin --user=admin --user=kubelet --group=system:serviceaccounts

as identified on [1]

[1] https://stackoverflow.com/questions/43499971/helm-error-no-available-release-name-found

We also created a service account for tiller as outlined on [2].

[2] helm/helm#3130

@devdattakulkarni
Copy link
Contributor Author

The problem seemed to be that kubeplus pod was not able to reach out to the world. This was fixed by following the suggestion on following link of updating the kube-dns configmap to add 8.8.8.8 and 8.8.4.4 as nameserver.

flannel-io/flannel#983

@devdattakulkarni
Copy link
Contributor Author

apiVersion: v1
kind: ConfigMap
metadata:
name: kube-dns
namespace: kube-system
labels:
addonmanager.kubernetes.io/mode: EnsureExists
data:
upstreamNameservers: |-
["8.8.8.8", "8.8.4.4"]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant