kubernetes-helm

问题 I have a Kubernetes cluster(Azure) with nginx-ingress, certmanager and one application, and I was wondering if there's a way of making the whole system as one single package so if there's any problem with the cluster it'd be easier to spin up another one. My main idea is to make the manual configuration of nginx-ingress and certmanager automatic, but I'm not sure how it'd included in a helm chart, if possible. If not possible, is there a way(or tool) for minimising the manual configuration of

问题 I have a Kubernetes cluster(Azure) with nginx-ingress, certmanager and one application, and I was wondering if there's a way of making the whole system as one single package so if there's any problem with the cluster it'd be easier to spin up another one. My main idea is to make the manual configuration of nginx-ingress and certmanager automatic, but I'm not sure how it'd included in a helm chart, if possible. If not possible, is there a way(or tool) for minimising the manual configuration of

问题 I have a Kubernetes cluster(Azure) with nginx-ingress, certmanager and one application, and I was wondering if there's a way of making the whole system as one single package so if there's any problem with the cluster it'd be easier to spin up another one. My main idea is to make the manual configuration of nginx-ingress and certmanager automatic, but I'm not sure how it'd included in a helm chart, if possible. If not possible, is there a way(or tool) for minimising the manual configuration of

问题 I am trying to add a new dashboard to the below helm chart https://github.com/helm/charts/tree/master/stable/prometheus-operator The documentation is not very clear. I have added a config map to the name space like the below - apiVersion: v1 kind: ConfigMap metadata: name: sample-grafana-dashboard namespace: monitoring labels: grafana_dashboard: "1" data: etcd-dashboard.json: |- {JSON} According to the documentation, this should just be "picked" up and added, but its not. https://github.com

问题 I am trying to add a new dashboard to the below helm chart https://github.com/helm/charts/tree/master/stable/prometheus-operator The documentation is not very clear. I have added a config map to the name space like the below - apiVersion: v1 kind: ConfigMap metadata: name: sample-grafana-dashboard namespace: monitoring labels: grafana_dashboard: "1" data: etcd-dashboard.json: |- {JSON} According to the documentation, this should just be "picked" up and added, but its not. https://github.com

问题 I am trying to add a new dashboard to the below helm chart https://github.com/helm/charts/tree/master/stable/prometheus-operator The documentation is not very clear. I have added a config map to the name space like the below - apiVersion: v1 kind: ConfigMap metadata: name: sample-grafana-dashboard namespace: monitoring labels: grafana_dashboard: "1" data: etcd-dashboard.json: |- {JSON} According to the documentation, this should just be "picked" up and added, but its not. https://github.com

问题 I am looking for a way to rollback a helm release to its previous release without specifying the target release version as a number. Something like helm rollback <RELEASE> ~1 (like git reset HEAD~1 ) would be nice. 回答1: As it turns out, there is an undocumented option to rollback to the last successful release by defining the target release version as 0. like: helm rollback <RELEASE> 0 Source: https://github.com/helm/helm/issues/1796 回答2: If you just want to rollback to the previous release,

问题 I am looking for a way to rollback a helm release to its previous release without specifying the target release version as a number. Something like helm rollback <RELEASE> ~1 (like git reset HEAD~1 ) would be nice. 回答1: As it turns out, there is an undocumented option to rollback to the last successful release by defining the target release version as 0. like: helm rollback <RELEASE> 0 Source: https://github.com/helm/helm/issues/1796 回答2: If you just want to rollback to the previous release,

问题 I have my own Python module (an '.so' file that I'm able to import locally) that I want to make available to my application running in Kubernetes. I am wholly unfamiliar with Kubernetes and Helm, and the documentation and attempts I've made so far haven't gotten me anywhere. I looked into ConfigMaps, trying kubectl.exe create configmap mymodule --from-file=MyModule.so , but kubectl says "Request entity too large: limit is 3145728". (My binary file is ~6mb.) I don't know if this is even the

问题 I have my own Python module (an '.so' file that I'm able to import locally) that I want to make available to my application running in Kubernetes. I am wholly unfamiliar with Kubernetes and Helm, and the documentation and attempts I've made so far haven't gotten me anywhere. I looked into ConfigMaps, trying kubectl.exe create configmap mymodule --from-file=MyModule.so , but kubectl says "Request entity too large: limit is 3145728". (My binary file is ~6mb.) I don't know if this is even the