Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

How can I find what options I can set with a `helm install` that the chart provides?

D
Duquan last edited by

Let's say I want to install an arbitrary helm chart like mysql-operator/mysql-innodbcluster how can I find what options I set with --set?
Reply Quote 0
1 Reply Last reply
J
juvenalb last edited by
You can use show values to see what options the chart provides,
```
helm show values mysql-operator/mysql-innodbcluster
```
What you'll get is a YAML file, here is a part of the above YAML output,
```
tls:
  useSelfSigned: false
#  caSecretName:
#  serverCertAndPKsecretName:
#  routerCertAndPKsecretName:
```
You an set the option for useSelfSigned as tls.useSelfSigned like this:
```
helm install mycluster mysql-operator/mysql-innodbcluster --set tls.useSelfSigned=true
```
Reply Quote 0
1 Reply Last reply

helm 66

2
Posts

0
Views

Suggested Topics

S

How to make Tiller highly available?
Continuous Integration and Delivery (CI, CD) • kubernetes helm • • Saumya

2

0
Votes

2
Posts

1
Views

K

Running two tillers does not make it HA. There is an open issue at the moment.
R

Can't install MongoDB docker on raspberry
Continuous Integration and Delivery (CI, CD) • docker • • rielyn

2

0
Votes

2
Posts

1
Views

Z

This means that the container that you are trying to pull is not available for the architecture, in this case it would be linux/arm64. Maybe there is an image available now. I would search for 'docker mongodb arm64' to see. I see support for mongodb under arm64v8 architecture, which would be in Raspberry Pi 4. Maybe you want to upgrade, as your chip is arm64v7. This issue explains error message in a bit more detail. Answers under this issue are going to help you run MongoDB under ARM64.
helm upgrade not working
Continuous Integration and Delivery (CI, CD) • kubernetes helm kubernetes helm • • inna

2

0
Votes

2
Posts

1
Views

E

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

Is there a way to combine helm with some other tool for k8s configuration management without conflicts?
Continuous Integration and Delivery (CI, CD) • jenkins kubernetes deployment helm kubernetes helm • • Burma

2

0
Votes

2
Posts

1
Views

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 image change definitely qualifies as one), you would push a change to your helm chart. The other alternative you have is defining docker image as a value. Then you can pass a command-line argument to replace the image tag with a new one and re-run helm from Jenkins any time you have a new deploy. Example: in values.yaml: image: repo: foo tag: bar On command line when running helm: helm upgrade --install my-app --set image.tag=newtag Final, and least recommended way is to use a mutable tag (i.e. "master") and set your ImagePullPolicy to Always. This way, when you have a deploy, you just need to bounce all the pods in your deployment/daemonset/statefulset object.
J

Is there a way through which I can control type of load balancer like round robin , least-connections
Continuous Integration and Delivery (CI, CD) • kubernetes amazon web services helm load balance • • jonetta

2

0
Votes

2
Posts

1
Views

Well there are 2 possibble options. One is to create a LoadBalancer type for each service you want to be exposed. In case you have just one service that's great. That's rarely the case of course If you build your k8s cluster properly ( having Prometheus-Operator doing the monitoring for example ) most likely besides the business logic service/s, you would want to expose internal cluster valuable services like Grafana. That's why even if you have just 1 service, for future extension of such type of need the best would be to use an Ingress resource. It providees a way to expose multiple services through a single IP address — HTTP level (network layer 7). You could play with HTTP headers essentially and do some path/host routing. You express the definition for your object and helm would do the installation. Another option is to use a tool like ArgoCD, basically sticking to GitOps policy. A fundamnetal knowledge is to be aware that the Load Balancer/Ingress would forward the traffic to the service, not the pods. Services are abstracted entities by kube-proxy, by default kube-proxy uses a round-robin algorithm. https://kubernetes.io/docs/concepts/services-networking/service/ Regarding the definition, it follows the standart K8s scheme [ apiVersion, kind, metadata, spec fields]. Example would be an Ingress created from AWS-Ingress-Controller. apiVersion: extensions/v1beta1 kind: Ingress metadata: name: ingress namespace: management annotations: kubernetes.io/ingress.class: alb alb.ingress.kubernetes.io/scheme: internet-facing spec: rules: - host: grafana.com http: paths: - backend: serviceName: grafana servicePort: 80 path: /* ```
R

How can we setup the services in my EC2 instance to startup automatically on boot?
Continuous Integration and Delivery (CI, CD) • linux amazon ec2 • • Raziyah00

2

0
Votes

2
Posts

0
Views

A

There are a lot of articles online regarding this, but here is one that should be simple enough => https://timleland.com/how-to-run-a-linux-program-on-startup/
How many executors can I have for a Jenkins Windows build node?
Continuous Integration and Delivery (CI, CD) • jenkins • • Demir

2

0
Votes

2
Posts

1
Views

T

You can specify the executors of your node in his configuration. Manage Jenkins -> Manage Nodes -> Configure Node -> Number of build processors In environments where we only run scripts etc. we have one executor per core. But if you have large build jobs and the performance is important for you, you should read this article from the jenkins documentation. https://www.jenkins.io/doc/book/scaling/architecting-for-scale/#Calculating-how-many-jobs
F

How to install Certbot plugins?
Continuous Integration and Delivery (CI, CD) • ssl certbot • • fbio

2

0
Votes

2
Posts

1
Views

E

Better method, thanks to the others responses for helping me get to this. Determine what plugins are installed currently: # certbot-auto plugins Saving debug log to /var/log/letsencrypt/letsencrypt.log - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - * apache Description: Apache Web Server plugin - Beta Interfaces: IAuthenticator, IInstaller, IPlugin Entry point: apache = certbot_apache.entrypoint:ENTRYPOINT * nginx Description: Nginx Web Server plugin Interfaces: IAuthenticator, IInstaller, IPlugin Entry point: nginx = certbot_nginx.configurator:NginxConfigurator * standalone Description: Spin up a temporary webserver Interfaces: IAuthenticator, IPlugin Entry point: standalone = certbot.plugins.standalone:Authenticator * webroot Description: Place files in webroot directory Interfaces: IAuthenticator, IPlugin Entry point: webroot = certbot.plugins.webroot:Authenticator - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Determine where your certbot (in my case certbot-auto) is installed: # find / -name certbot /opt/eff.org/certbot ... Get into the Virtual Env and install plugin cd /opt/eff.org/certbot/venv source bin/activate pip install certbot-dns-google deactivate Verify certbot plugins again # certbot-auto plugins Saving debug log to /var/log/letsencrypt/letsencrypt.log - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - * apache Description: Apache Web Server plugin - Beta Interfaces: IAuthenticator, IInstaller, IPlugin Entry point: apache = certbot_apache.entrypoint:ENTRYPOINT * dns-google Description: Obtain certificates using a DNS TXT record (if you are using Google Cloud DNS for DNS). Interfaces: IAuthenticator, IPlugin Entry point: dns-google = certbot_dns_google.dns_google:Authenticator * nginx Description: Nginx Web Server plugin Interfaces: IAuthenticator, IInstaller, IPlugin Entry point: nginx = certbot_nginx.configurator:NginxConfigurator * standalone Description: Spin up a temporary webserver Interfaces: IAuthenticator, IPlugin Entry point: standalone = certbot.plugins.standalone:Authenticator * webroot Description: Place files in webroot directory Interfaces: IAuthenticator, IPlugin Entry point: webroot = certbot.plugins.webroot:Authenticator - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
K

helm install causes nil pointer
Continuous Integration and Delivery (CI, CD) • kubernetes helm • • Kadyn

2

0
Votes

2
Posts

1
Views

You can try below options to debug this further. First verify values.yaml and check the values for serviceAccount (default value is true ) that means the helm chart when deployed will create a service account for the deployment. When you create a pod, if you do not specify a service account, it is automatically assigned the default service account in the given namespace. serviceAccount: # Specifies whether a service account should be created create: true # Annotations to add to the service account annotations: {} # The name of the service account to use. # If not set and create is true, a name is generated using the fullname template name: Try to deploy your helm chart with create: false and verify if it solves your issue. Else remove the file hello-world/templates/serviceaccount.yaml and mark serviceaccount as create: false in value.yaml and pass name as default service account of your deployment try to deploy as below Note I have removed the serviceaccount.yaml ~/hello$ tree . └── hello-world ├── charts ├── Chart.yaml ├── templates │ ├── deployment.yaml │ ├── _helpers.tpl │ ├── ingress.yaml │ ├── NOTES.txt │ ├── service.yaml │ └── tests │ └── test-connection.yaml └── values.yaml 4 directories, 8 files set create field as false under values.yaml $ cat hello-world/values.yaml | grep -i serviceaccount -A 10 serviceAccount: # Specifies whether a service account should be created create: false # Annotations to add to the service account annotations: {} # The name of the service account to use. # If not set and create is true, a name is generated using the fullname template name: default You can fetch your list of serviceaccounts available as below $ kubectl get serviceaccounts NAME SECRETS AGE default 1 2d4h Once deployed helm list will show the namespace used to deploy your chart and serviceaccount from the name space is used for deploeyemnt $ helm list NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION hello-world-1580665905 default 1 2020-02-02 17:51:45.631330487 +0000 UTC deployed hello-world-0.1.0 1.16.0 Get chart details and values post deploeyemtn as below $ helm show chart hello-world apiVersion: v2 appVersion: 1.16.0 description: A Helm chart for Kubernetes name: hello-world type: application version: 0.1.0 $ helm show values hello-world | grep -i serviceaccount -A 10 serviceAccount: # Specifies whether a service account should be created create: false # Annotations to add to the service account annotations: {} # The name of the service account to use. # If not set and create is true, a name is generated using the fullname template name: default podSecurityContext: {} # fsGroup: 2000 Get deployed resources as below $ kubectl get all -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES pod/hello-world-1580665905-84b9d4d469-xv5mx 1/1 Running 0 118s 192.168.58.215 k8s-node02 <none> <none> NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR service/hello-world-1580665905 ClusterIP 10.108.73.21 <none> 80/TCP 118s app.kubernetes.io/instance=hello-world-1580665905,app.kubernetes.io/name=hello-world service/kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 2d4h <none> NAME READY UP-TO-DATE AVAILABLE AGE CONTAINERS IMAGES SELECTOR deployment.apps/hello-world-1580665905 1/1 1 1 118s hello-world nginx:1.16.0 app.kubernetes.io/instance=hello-world-1580665905,app.kubernetes.io/name=hello-world NAME DESIRED CURRENT READY AGE CONTAINERS IMAGES SELECTOR replicaset.apps/hello-world-1580665905-84b9d4d469 1 1 1 118s hello-world nginx:1.16.0 app.kubernetes.io/instance=hello-world-1580665905,app.kubernetes.io/name=hello-world,pod-template-hash=84b9d4d469
B

Helm: Long Running Jobs vs Long Running Hooks
Continuous Integration and Delivery (CI, CD) • kubernetes helm kubernetes helm • • Burma

2

0
Votes

2
Posts

0
Views

E

A helm hook pretty much has to be a Job or Pod. Thus choosing between using a hook or using a Job doesn't make much sense - you are usually best off using a Job which is annotated as a pre-upgrade hook. And yes, the timeout probably needs to be increased by the users. Unfortunately it's not possible to define the timeout in the chart itself. In some cases it makes sense to have a db upgrade happen after the helm chart has been applied and in that case it can be a "normal" Job. This pattern however requires coordination between the Pods accessing the DB and the upgrade process such as a table in the DB which declares the version(s) of the schema.
A

503 Service Temporarily Unavailable using Kubernetes
Continuous Integration and Delivery (CI, CD) • kubernetes helm • • authera

2

0
Votes

2
Posts

1
Views

A

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
Z

Is this an appropriate architecture, or can improvements be made?
Continuous Integration and Delivery (CI, CD) • azure architecture microservices • • zymir

2

0
Votes

2
Posts

1
Views

G

My largest concern is around the MS SQL Server implementation. Coupling the read only instances so tightly to the services feels wrong. Is there a better way to do this? Essentially what you have designed is a caching system - the service containers have a local copy of the data presumably so that for reads they don't have to make an extra network trip. As you've pointed out, a more standard approach is to have a cluster of read replicas that all of the containers can read from. This allows you to scale them separately from the application servers, which is good, because they generally need different things (do you really want to allocate large amounts of RAM to every application container?). This will add network calls for database reads, but until that's proven to be an issue I wouldn't complicate the architecture to solve it. If it does become an issue, a much more lightweight way of handling the problem is to run an actual cache locally, like memcache or redis. You can tune the TTLs on individual objects to be appropriate, and it will automatically drop off rarely-requested data to keep the application server light.
how to automate helm deployments in github actions
Continuous Integration and Delivery (CI, CD) • github kubernetes helm • • Marcee

2

0
Votes

2
Posts

0
Views

P

Got it working with this helm github action https://github.com/marketplace/actions/helm-3 add secret to github as your .kube/config and this workflow step: steps: - name: 'check it out' uses: actions/checkout@v3 - name: helm-deploy uses: WyriHaximus/github-action-helm3@v2.0 with: exec: helm upgrade logstash /github/workspace/elk/logstash/ --install --wait --atomic --namespace=default --set=app.name=logstash --values=/github/workspace/elk/logstash/values.yaml kubeconfig: '${{ secrets.KUBECONFIG }}'
Y

I can't figure out what I'm doing.
Software Programming • kubernetes helm • • yajahira

2

0
Votes

2
Posts

0
Views

There is no predetermined object in helm .ValueI do. .Values♪ In order to avoid similar errors in the future, the best use of the IDE with support for helm-chart processing and auto-filling.Look at that. https://helm.sh/docs/chart_template_guide/builtin_objects/ for predetermined objects helm.
T

How can I download an artifact from Jenkins using the Google Login Plugin?
Continuous Integration and Delivery (CI, CD) • jenkins continuous integration google cloud platform • • tahishae

2

0
Votes

2
Posts

1
Views

C

Thank you to the comment from user54 for the answer. Both of my pasted wget URLs work as long as I'm using the correct value for password. In this case, I needed to use my user's API Token as described in the answer to another question: https://stackoverflow.com/a/34634247/317951

How can I find what options I can set with a `helm install` that the chart provides?

Suggested Topics

How to make Tiller highly available? Continuous Integration and Delivery (CI, CD) • kubernetes helm • • Saumya

Can't install MongoDB docker on raspberry Continuous Integration and Delivery (CI, CD) • docker • • rielyn

helm upgrade not working Continuous Integration and Delivery (CI, CD) • kubernetes helm kubernetes helm • • inna

Is there a way to combine helm with some other tool for k8s configuration management without conflicts? Continuous Integration and Delivery (CI, CD) • jenkins kubernetes deployment helm kubernetes helm • • Burma

Is there a way through which I can control type of load balancer like round robin , least-connections Continuous Integration and Delivery (CI, CD) • kubernetes amazon web services helm load balance • • jonetta

How can we setup the services in my EC2 instance to startup automatically on boot? Continuous Integration and Delivery (CI, CD) • linux amazon ec2 • • Raziyah00

How many executors can I have for a Jenkins Windows build node? Continuous Integration and Delivery (CI, CD) • jenkins • • Demir

How to install Certbot plugins? Continuous Integration and Delivery (CI, CD) • ssl certbot • • fbio

helm install causes nil pointer Continuous Integration and Delivery (CI, CD) • kubernetes helm • • Kadyn

Helm: Long Running Jobs vs Long Running Hooks Continuous Integration and Delivery (CI, CD) • kubernetes helm kubernetes helm • • Burma

503 Service Temporarily Unavailable using Kubernetes Continuous Integration and Delivery (CI, CD) • kubernetes helm • • authera

Is this an appropriate architecture, or can improvements be made? Continuous Integration and Delivery (CI, CD) • azure architecture microservices • • zymir

how to automate helm deployments in github actions Continuous Integration and Delivery (CI, CD) • github kubernetes helm • • Marcee

I can't figure out what I'm doing. Software Programming • kubernetes helm • • yajahira

How can I download an artifact from Jenkins using the Google Login Plugin? Continuous Integration and Delivery (CI, CD) • jenkins continuous integration google cloud platform • • tahishae

How to make Tiller highly available?
Continuous Integration and Delivery (CI, CD) • kubernetes helm • • Saumya

Can't install MongoDB docker on raspberry
Continuous Integration and Delivery (CI, CD) • docker • • rielyn

helm upgrade not working
Continuous Integration and Delivery (CI, CD) • kubernetes helm kubernetes helm • • inna

Is there a way to combine helm with some other tool for k8s configuration management without conflicts?
Continuous Integration and Delivery (CI, CD) • jenkins kubernetes deployment helm kubernetes helm • • Burma

Is there a way through which I can control type of load balancer like round robin , least-connections
Continuous Integration and Delivery (CI, CD) • kubernetes amazon web services helm load balance • • jonetta

How can we setup the services in my EC2 instance to startup automatically on boot?
Continuous Integration and Delivery (CI, CD) • linux amazon ec2 • • Raziyah00

How many executors can I have for a Jenkins Windows build node?
Continuous Integration and Delivery (CI, CD) • jenkins • • Demir

How to install Certbot plugins?
Continuous Integration and Delivery (CI, CD) • ssl certbot • • fbio

helm install causes nil pointer
Continuous Integration and Delivery (CI, CD) • kubernetes helm • • Kadyn

Helm: Long Running Jobs vs Long Running Hooks
Continuous Integration and Delivery (CI, CD) • kubernetes helm kubernetes helm • • Burma

503 Service Temporarily Unavailable using Kubernetes
Continuous Integration and Delivery (CI, CD) • kubernetes helm • • authera

Is this an appropriate architecture, or can improvements be made?
Continuous Integration and Delivery (CI, CD) • azure architecture microservices • • zymir

how to automate helm deployments in github actions
Continuous Integration and Delivery (CI, CD) • github kubernetes helm • • Marcee

I can't figure out what I'm doing.
Software Programming • kubernetes helm • • yajahira

How can I download an artifact from Jenkins using the Google Login Plugin?
Continuous Integration and Delivery (CI, CD) • jenkins continuous integration google cloud platform • • tahishae