Problem:
If I try this command per the kubernetes doc
helm install sumologic/sumologic --name collection --namespace sumologic --set sumologic.endpoint=https://api.us2.sumologic.com/api/v1/ --set sumologic.accessId=<access_id> --set sumologic.accessKey=<access_key>
I get this response:
module.presidiohealth-eks-deploy.null_resource.deploy_sumologic (remote-exec): Error: namespaces "sumologic" is forbidden: User "system:serviceaccount:kube-system:default" cannot get resource "namespaces" in API group "" in the namespace "sumologic"
Resolution:
First, delete the tiller-deploy deployment if it exists
kubectl get deployments -n kube-system
This should give you
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
............................
tiller-deploy 1 1 1 1 2m35s
Then you run
kubectl delete deployment tiller-deploy -n kube-system
You should see "deployment.extensions "tiller-deploy" deleted"
Second, please follow the steps in this link
Create this file rbac-config.yaml with following content
apiVersion: v1
kind: ServiceAccount
metadata:
name: tiller
namespace: kube-system
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: tiller
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: cluster-admin
subjects:
- kind: ServiceAccount
name: tiller
namespace: kube-system
Note: The cluster-admin role is created by default in a Kubernetes cluster, so you don’t have to define it explicitly.
$ kubectl create -f rbac-config.yaml
serviceaccount "tiller" created
clusterrolebinding "tiller" created
$ helm init --service-account tiller --history-max 200
The last command may need a "--upgrade" option if you see this error
cloud_user@4ragumurthy1c:~$ helm init --service-account tiller --history-max 200
$HELM_HOME has been configured at /home/cloud_user/.helm.
Warning: Tiller is already installed in the cluster.
(Use --client-only to suppress this message, or --upgrade to upgrade Tiller to the current version.)
Modified command
cloud_user@4ragumurthy1c:~$ helm init --service-account tiller --history-max 200 --upgrade
$HELM_HOME has been configured at /home/cloud_user/.helm.
Tiller (the Helm server-side component) has been upgraded to the current versio
Comments
0 comments
Please sign in to leave a comment.