I have installed ISTIO using Helm . I forgot to enable grafana, kiali and jaeger. How can i enable all these above services after i have installed istio?
Here is howto: from official repository.
you need to update values.yaml.
and turn on grafana, kiali and jaeger. For example with kiali change:
kiali:
enabled: false
to
kiali:
enabled: true
than rebuild the Helm dependencies:
helm dep update install/kubernetes/helm/istio
than upgrade your istio inside kubernetes:
helm upgrade install/kubernetes/helm/istio
that's it, hope it was helpful
So did you install direct or created a yaml from the templates ?
I would run the command you used to install but with template function and then add the options for jaeger,Kiali and grafana.
Related
I can see the Argo seems to support OCI repositories but I can't seem to get this to work.
First I can only seem to add repositories through the CLI because there is no option for enabling OCI.
argocd repo add <uri> --type helm --name name --enable-oci
However, when adding an app using the UI the argo server is logging "unsupported protocol scheme ''" when selecting the repository. I have tried a URI with HTTPS and empty (as mentioned in the issues).
Is it possible to use the UI for OCI repositories or is it a command line thing only?
I am using Argo version 2.0.4
I used the following command and it worked for me.
argocd repo add <acr name>.azurecr.io --type helm --name <some name> --enable-oci --username <username> --password <password>.
You can also try to configure it declartively: issue-7121
apiVersion: v1
stringData:
enableOCI: "true"
name: my-oci-charts
password: token-password
type: helm
url: registry.gitlab.com/asdasd/charts
username: token-name
kind: Secret
metadata:
labels:
argocd.argoproj.io/secret-type: repository
name: my-oci-charts
I'm trying to install
[ec2-user#ip-*********** ~]$ helm install stable/prometheus-operator --generate-name
Error: failed to download "stable/prometheus-operator" (hint: running `helm repo update` may help)
And also installing the monitoring doesn't work :
helm install monitoring --namespace monitoring stable/prometheus-operator
Produces :
[ec2-user#ip-&&&&&&&&&&& ~]$ helm install monitoring --namespace monitoring
Error: must either provide a name or specify --generate-name
[ec2-user#ip-&&&&&&&&&&& ~]$ helm install monitoring --namespace monitoring --generate-name
Error: failed to download "monitoring" (hint: running `helm repo update` may help)
Any idea how to solve this ?
you need to add the repo first, and there is updated/latest kube-prometheus-stack (prometheus-operator)
helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
helm repo add stable https://kubernetes-charts.storage.googleapis.com/
helm repo update
helm -n monitoring install [RELEASE_NAME] prometheus-community/kube-prometheus-stack
ref:
https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack
I've installed prometheus more recently than above (may 2021) and it seems that they changed the syntax again. The correct commands is as below, so I think it might help if you want to install it now:
helm repo add stable https://charts.helm.sh/stable
helm repo update
helm install [pod name] prometheus-community/kube-prometheus-stack
You are slightly missing the syntax: try
helm install --name prometheus --namespace monitoring stable/prometheus-operator
Here --name mean name of helm deployment, and stable/prometheus-operator is helm chart to be used.
I've installed prometheus just yesterday and it seems that they changed the syntax again. Took me an hour to research the correct commands, so I think it might help if you want to install it now - in 2021:
helm repo add stable https://charts.helm.sh/stabled
helm repo update
helm install [pod name] stable/prometheus
TO INSTALL PROMETHEUS THROUGH HELM
helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
helm repo add kube-state-metrics https://kubernetes.github.io/kube-state-metrics
helm repo update
helm install [RELEASE_NAME]/ANY-NAME-GIVE prometheus-community/prometheus
EXAMPLE BELOW
CHART NAME :- prometheus-community/prometheus
RELEASE NAME :- monitoring
We have installed Istio manually on GKE cluster. We want to install/add istio stack driver adapter so that Istio metrics are available on Stack Driver monitoring Dashboard of GCP. I am not able to get the metrics despite add the CRD as mentioned in
https://github.com/GoogleCloudPlatform/istio-samples/blob/master/common/install_istio.sh
git clone https://github.com/istio/installer && cd installer
helm template istio-telemetry/mixer-telemetry --execute=templates/stackdriver.yaml -f global.yaml --set mixer.adapters.stackdriver.enabled=true --namespace istio-system | kubectl apply -f -
I feel we are missing the authentication part. Can anyone help in resolving this?
I was unable to replicate your set up and I notice that the Istio version downloaded by the script was 1.4.2 which is not supported by GKE at this moment.
Nonetheless, I’d recommend you to check this document for troubleshooting and consult this guide to get Istio installed on GKE.
You should also be aware of couple of limitations when using Istio on GKE
I installed Jenkins via Helm in a k8s cluster in AWS:
helm install --name my-jenkins stable/jenkins
However I don't see the external endpoint service. How do I access Jenkins URL?
Am I missing something?
I found out after a bit of research. Here are the steps to be followed.
1) helm search jenkins
2) Change stable/jenkins default values:
helm inspect values stable/jenkins > /tmp/jenkins.values
sudo vi /tmp/jenkins.values
3) Update the following values in the jenkins.values file:
serviceType: LoadBalancer
4) Install helm stable/jenkins
helm install stable/jenkins --values /tmp/jenkins.values --name myjenkins --namespace jenkins
5) Get status:
kubectl get svc --namespace jenkins
You can view the external-IP
Having my cluster up and running on AWS EKS, I'm finding trouble running helm init with the following error:
$ helm init --service-account tiller --upgrade
Error: error installing: deployments.extensions is forbidden: User "system:anonymous" cannot create deployments.extensions in the namespace "kube-system"
kubectl works properly (object retrieval, creation and cluster administration), authenticating and authorizing correctly by running heptio-authenticator-aws at connection time ( with an exec section in the kubectl config).
In order to prepare the cluster for helm, I created the service account and role binding as specified in the helm docs.
I've heard of people having helm running on EKS, and I'm guessing they're skipping the exec section of the kubectl config by hardcoding the token... I'd like to avoid that!
Any ideas on how to fix this? My guess is that it is related to helm not being able to execute heptio-authenticator-aws properly
I was running helm version 2.8.2 when obtaining this error, upgrading to v2.9.1 fixed this!