kubernetes-helm

问题 According to cert-manager installation docs jetstack repository should be added: $ helm repo add jetstack https://charts.jetstack.io It gives error message: Error: looks like "https://charts.jetstack.io" is not a valid chart repository or cannot be reached: error unmarshaling JSON: while decoding JSON: json: unknown field "serverInfo" What are the ways to fix the issue? 回答1: This looks to be caused by a patch done in Version 3.3.2 of Helm for security based issues. Reference Issue: https:/

问题 I'm trying to template variables from a map inside the values.yaml into my final Kubernetes ConfigMap YAML. I've read through https://github.com/helm/helm/issues/2492 and https://helm.sh/docs/chart_template_guide/ but can't seem to find an answer. For some context, this is roughly what I'm trying to do: values.yaml config: key1: value key2: value-{{ .Release.Name }} configmap.yaml kind: ConfigMap data: config-file: | {{- range $key, $value := .Values.config }} {{ $key }} = {{ $value }} {{-

问题 I'm trying to template variables from a map inside the values.yaml into my final Kubernetes ConfigMap YAML. I've read through https://github.com/helm/helm/issues/2492 and https://helm.sh/docs/chart_template_guide/ but can't seem to find an answer. For some context, this is roughly what I'm trying to do: values.yaml config: key1: value key2: value-{{ .Release.Name }} configmap.yaml kind: ConfigMap data: config-file: | {{- range $key, $value := .Values.config }} {{ $key }} = {{ $value }} {{-

问题 I'm new to istio. I have a simple ingress gateway yaml file, and the listenling port is 26931, but after I applied the yaml, the port 26931 does not appear in the set of ports which ingress gateway expose. So am I lack of some necessary step or something else? apiVersion: networking.istio.io/v1alpha3 kind: Gateway metadata: name: batman-gateway spec: selector: istio: ingressgateway servers: - port: number: 26931 name: http protocol: HTTP hosts: - "*" 回答1: You are exposing ports not with

问题 I'm new to istio. I have a simple ingress gateway yaml file, and the listenling port is 26931, but after I applied the yaml, the port 26931 does not appear in the set of ports which ingress gateway expose. So am I lack of some necessary step or something else? apiVersion: networking.istio.io/v1alpha3 kind: Gateway metadata: name: batman-gateway spec: selector: istio: ingressgateway servers: - port: number: 26931 name: http protocol: HTTP hosts: - "*" 回答1: You are exposing ports not with

问题 my charts has elasticsearch and mongdb dependencies, and in my charts, the structure like this: ├── [-rw-rw-r--] Chart.yaml ├── [drwxrwxr-x] dependency_charts │ ├── [drwxrwxr-x] elasticsearch │ └── [drwxrwxr-x] mongodb ├── [-rw-rw-r--] deploy.sh ├── [-rw-rw-r--] requirements.yaml ├── [-rw-rw-r--] values.yaml ├── [drwxrwxr-x] templates │ ├── [-rw-rw-r--] proj-deploy.yaml │ └── [-rw-rw-r--] proj-svc.yaml but when I try to install my chart, it will say: Error: found in requirements.yaml, but

问题 my charts has elasticsearch and mongdb dependencies, and in my charts, the structure like this: ├── [-rw-rw-r--] Chart.yaml ├── [drwxrwxr-x] dependency_charts │ ├── [drwxrwxr-x] elasticsearch │ └── [drwxrwxr-x] mongodb ├── [-rw-rw-r--] deploy.sh ├── [-rw-rw-r--] requirements.yaml ├── [-rw-rw-r--] values.yaml ├── [drwxrwxr-x] templates │ ├── [-rw-rw-r--] proj-deploy.yaml │ └── [-rw-rw-r--] proj-svc.yaml but when I try to install my chart, it will say: Error: found in requirements.yaml, but

问题 How to SSH into a Kubernetes Node or Server hosted on AWS? I have hosted a Kubernetes Server and Node on AWS. I'm able to see the nodes and server from my local laptop with the kubectl get node command. I need to create a persistent volume for my node but I'm unable to ssh into it. Is there any specific way to ssh into the node or server? 回答1: Try this: ssh -i <path of the private key file> admin@<ip of the aws kube instances> The perm file should be in $HOME/.ssh/kube_rsa 回答2: Kubernetes

问题 I'm new to Kubernetes and as a tutorial for myself I've been working on deploying a basic project to Kubernetes with helm (v3). I have an image in AWS's ECR as well as a local helm chart for this project. However, I am struggling to run my image with Kubernetes. My image is set up correctly. If I try something like docker run my_image_in_ecr locally it behaves as expected (after configuring my IAM access credentials locally). My helm chart is properly linted and in my image map, it specifies:

问题 I am using Helm kubernetes deployment and I want to run the postman test cases before a final deployment, and if any test case fails then rollback (or retain the current deployment like Blue-Green deployment). How to achieve this? 回答1: I achieved the expected behavior with Helm Chart Tests and the postman/newman Docker image. My Helm template for the test execution: apiVersion: v1 kind: Pod metadata: name: API Test annotations: "helm.sh/hook": test-success spec: containers: - name: