We changed our privacy policy. Read more.

New answers tagged

0

In a simple words and correct me If I am wrong, kubectl create namespace ingress-nginx -> this creates a namespace called ingress-nginx Correct ! helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx -> This add a chart repository called ingress-nginx from the URL mentioned (Am I free to name it to something else!?) Correct too ! ...


0

I would suggest try out Terraform with the helm provider. I work with this every day and all of our helm charts have custom values files for deployment. I guess this can be considered a "best practice" depending on the company. So how the flow goes: We have a custom app all in K8S. We set up a helm_release with terraform. We specify the custom ...


1

You explained what each does pretty well! I strongly suggest reading the documentation, especially for the commands, don't rely on tutorials only.helm commands helm repo add => This is what it stands for, it adds a new helm chart repository. helm repo update => Update gets the latest information about charts from the respective chart repositories. When ...


0

I found the issue in your helm templates. The charts directory inside the helm chart must be charts, not chart. I tried to simulate your issue and am able to fix it now. I refactored the directory structure like below . ├── Chart.yaml ├── charts │   └── subchart │   ├── Chart.yaml │   ├── charts │   ├── templates │   │   └── configMap.yaml │  ...


0

Seems like these commands are sufficient $ kubectl rollout history deployment myapp $ kubectl rollout history deployment myapp --revision=76 and to check the difference (use diff or colordiff) colordiff \ <(kubectl rollout history deployment myapp --revision=76) \ <(kubectl rollout history deployment myapp --revision=81)


0

I had the same problem. I double checked my folder structure. Instead of templates I named my folder template.


Top 50 recent answers are included