Hot answers tagged

3

Generally, a Helm chart would cover all your microservices - ideally, you should be able to deploy whole application in one chart. It may get a little messy if you include external 3rd party dependencies, where you would need to handle dependent charts, but I assume this is out of scope of your question. More so, if your microservices are very similar you ...


2

Helm isn't made to be used this way. If you'd prefer to use a static deployment, you're better off using a plain Kubernetes manifest. Then, people changing the image field won't break your release. You can easily convert it to one simply by running helm get manifest command Helm is used to manage release versions. I.e. every new release (and a docker ...


2

I believe what you're asking is: "Is there any way to create just one helm chart that can be used for all microservices in my application?". If so, then you can just use the values.yaml file to store all the values for your templates. This is not considered good practice, considering your template file needs to hold the information for each of your ...


2

I tend to prefer infra code living separately from application deployment code. Multiple reasons for this: You want your infra team to make infra changes. You want your app team to make application changes (including application configuration). Putting them separately lets you specify separate guard rails on them (for example, only the infra team is ...


1

Managed to solve this by changing the values.yaml in the loki-stack helm chart to the following: promtail: enabled: true pipelineStages: - cri: {} Enjoy.


1

Yeah, this is what I had in mind all along. Blue/Green Deployments on Kubernetes. So in short, Helm as it stands, is not for me since it doesn't have the concept of a blue/green deployment. With Helm, when you install a new package, the Deployment gets updated with the new Pod versions, but the Service is still pointing to the Deployment. Helm doesn't have ...


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 ...


1

If you could let us know what helm chart you have used to install prom-operator, that might help refine the answer. But in case of kube-prometheus-stack, in the values.yaml of the , use the additionalScrapeConfigs section to describe jobs that are external to k8s system and re-deploy. Or use serviceMonitors as described in this article


1

This is not a Helm issue. You are probably trying to update the LabelSelector fields which are immutable. This is expected behaviour as per the kubernetes.


1

You're missing namespace in the upgrade command. Following should work: helm upgrade chart-repository chart-repository/ -n charts


1

i'm guessing the problem is that the name of the service port is not configured, and in the ingress you specified the http name and it can not find it. name your port http , or give the port that you want to use (80) to the servicePort in the ingress file


1

Helm charts should not be built for a specific environment, IMHO. You can see that many of the official helm charts have a set of default values and they are configurable from outside. You also can create a helm chart like that and declare your deployment + environment-specific values with another tool like Helm Operator or ArgoCD. In this way, you can both ...


1

I educated myself more about helm and it looks like it has these features that I need packaging templating release management, including rollbacks so I'll study it more.


1

Couple of possible solutions: Control the configmap from a third chart and add the third chart as a dependency in both the charts. This will duplicate the secret and can cause a skew in the values being used both the charts since if they have independent release cycles Create the configmap in one namespace and refer to it using an external reference. You ...


1

Well that's a legit question IMHO, but there are multiple way of doing things (and no one is worth than other). 1- Everything from dev to prod at the same place If you want to grab everything from dev to production in a single project, it's possible, but you cannot build the docker image from hell command. Helm is only here to organize, use template in yaml ...


1

The error you are getting is from your Kubernetes cluster being unable to pull container image from GitLab. Providing a temporary credential to pull the containers as deploy time is not a great solution. For example, say your Kubernetes cluster needs to scale up by adding another node, the node will come up and try and pull the container, but the secret will ...


Only top voted, non community-wiki answers of a minimum length are eligible