I am working on a toy project and want to connect my GitLab to my GKE. There is a one liner that does it. After creating the GKE, I can run the oneliner and it works fine.
But I don't want to keep the cluster running for long since I don't want to be charged. When I am developing, I want to deploy my infrastructure and with my infrastructure, I want my gitlab connection also setup. And after I stop it, I will run terraform destroy to stop my cluster
I am using terraform to deploy GKE, but I can't find a way to run a command inside the cluster with the deployment of my infrastructure. Is there a way to do this?
Thanks for you help
Please tell me if this works for you:
helm repo add stable https://kubernetes-charts.storage.googleapis.com/
helm repo add stable https://charts.helm.sh/stable
helm repo update
helm install nginx-ingress stable/nginx-ingress
kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v0.16.0/cert-manager.yaml
Related
our team right now is using helm chart to deploy services to k8s cluster, and ArgoCD to sync the helm chart modification to k8s cluster.
My question is that, when ArgoCD performs a helm chart sync, what action does it do under the hood? does it use the command "helm upgrade" to do it? or else?
Thanks
Argo does not perform a helm install or helm upgrade of sorts; it is more closely related to a helm template <cmd+opts> | kubectl apply -f -.
I think you should look into the concept of GitOps.
Argo CD is responsible for pulling updated code from Git repositories
and deploying it directly to Kubernetes resources.
(quoted from https://codefresh.io/learn/argo-cd/)
I think best way is to package the chart into a CR instances in your env and then give argocd credentials to access the charts
The trick is how would you give argocd credentials and also if you have multiple charts how do sync all in one go
I’m quite new to kubernetes and helm (still grasping some of the basic concepts). I’m experimenting with a local deployment with microk8s.
I’m trying to deploy a project locally and the repo’s project has multiple charts. Once installed all the pods work fine except for one. Looking for a solution, I found that the chart needs a different value in the yaml file, however is not possible to edit the file while the pod is installed and running. I deleted and now I want to install this specific pod but edit the values beforehand.
The command I used to install the repo:
helm --namespace [Namespace] install [repo] [Name]/[Name] --create-namespace
So I want to install this pod in the same namespace I created.
I am trying to use helm charts with k0s.
Having my own helm-charts app, I would like to create a local repo. But I cannot use the serve command since I am using version: 3.5.4 and the serve command had been ditched for security concerns.
I am not sure now how to create a local repo ? and where can I find tutorials or examples ?
Also, how to deploy my chart in k0s cluster ?
I would try to use ChartMuseum instead. You can follow the docs to create a local filesystem chart.
You simply deploy the same way as with helm v2. Make sure you add the chart repo and you have kubectl configured to point to the cluster that you want to talk to so that ~/.kube/config has the right configuration.
Yes it does, you can also utilize k8slens.dev to easily deploy helm charts to your Kubernetes clusters. Regardless of the distro..
when I recently tried to use Gitlab Auto DevOps to Kubernetes, my Gitlab GUI cannot see the Helm Tiller application.
Why?
One possible reason could be that you are using Helm 3. The Tiller doesn't exist on Helm 3.
The internal implementation of Helm 3 has changed considerably from Helm 2. The most apparent change is the removal of Tiller.
I am installing Kubernetes in a non-internet environment. I want to use Helm and want to set up a custom chart repository.
helm init barfs after creating ~/.helm/repository/repositories.yaml as it can't reach the default Google repo, so I will end up installing manually via kubectl - what is the format of this chart repository if I want to set up my own?
I will run helm init --dry-run --debug in order to get the manifest and amend this to point at a Docker registry that I have access to then install via kubectl.
I didn't see the section in the docs here: https://github.com/kubernetes/helm/blob/master/docs/chart_repository.md
It's a web server.
A custom helm repository doesnt have to do anything with your kubernetes. Setting up the custom repo can be done without connecting even to any kubernetes cluster.
helm init --client-only
Next step is to set up your custom repository somewhere like a storage account or whatever, then add that custom repo Url to your helm. So far this is all client side; you didnt touch your cluster yet.
helm repo add <HELM-REPO-NAME> <HEM-REPO-URL>
The final step which is where you will need to connect to a real kubernetes cluster to install the helm chart using Tiller which lives inside your cluster.