kubernetes-helm

问题 Given a following scheme of services and their dependencies I would like to engineer a set of Helm charts. API Gateway calls Service A and Service C Service A calls Service B Service B calls Database Service C calls Service B and Service D At the moment I see two alternatives: Each of the 6 components in a diagram below is a single chart and each arrow in a diagram is a single dependency. There's an Umbrella chart that has a dependency on all other charts. The Database chart is a dependency

问题 I am trying to use it to run some integration tests, so to verify the service code I am deploying is actually doing the right thing. Basically how I setup is (as described here: https://docs.helm.sh/developing_charts/#chart-tests) creating this templates/tests/integration-test.yaml chart test file, and inside it specify to run a container, which basically is a customized maven image with test code added in and the test container is simply started by command “mvn test”, which does some simple

问题 I am trying to use it to run some integration tests, so to verify the service code I am deploying is actually doing the right thing. Basically how I setup is (as described here: https://docs.helm.sh/developing_charts/#chart-tests) creating this templates/tests/integration-test.yaml chart test file, and inside it specify to run a container, which basically is a customized maven image with test code added in and the test container is simply started by command “mvn test”, which does some simple

问题 I am getting below error while doing the installation of RabbitMQ through helm install. MountVolume.SetUp failed for volume "config-volume" : couldn't propagate object cache: timed out waiting for the condition Below is the details of kubectl version: Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2", GitCommit:"17c77c7898218073f14c8d573582e8d2313dc740", GitTreeState:"clean", BuildDate:"2018-10-24T06:54:59Z", GoVersion:"go1.10.4", Compiler:"gc", Pl atform:"linux/amd64"}

问题 There is a helm chart for nexus: https://github.com/helm/charts/tree/master/stable/sonatype-nexus I installed it like using helm: helm install stable/sonatype-nexus --name=nexus But it didn't work because of nexus-proxy. There is logs for nexus-proxy container: [vert.x-eventloop-thread-0] [io.vertx.ext.web.impl.RoutingContextImplBase] Unexpected exception in route So, i started to google and found that post: https://github.com/travelaudience/nexus-proxy/issues/4 There we no answer except this

问题 There is a helm chart for nexus: https://github.com/helm/charts/tree/master/stable/sonatype-nexus I installed it like using helm: helm install stable/sonatype-nexus --name=nexus But it didn't work because of nexus-proxy. There is logs for nexus-proxy container: [vert.x-eventloop-thread-0] [io.vertx.ext.web.impl.RoutingContextImplBase] Unexpected exception in route So, i started to google and found that post: https://github.com/travelaudience/nexus-proxy/issues/4 There we no answer except this

问题 There is a helm chart for nexus: https://github.com/helm/charts/tree/master/stable/sonatype-nexus I installed it like using helm: helm install stable/sonatype-nexus --name=nexus But it didn't work because of nexus-proxy. There is logs for nexus-proxy container: [vert.x-eventloop-thread-0] [io.vertx.ext.web.impl.RoutingContextImplBase] Unexpected exception in route So, i started to google and found that post: https://github.com/travelaudience/nexus-proxy/issues/4 There we no answer except this

问题 I'm trying to add my Azure AKS Kubernetes cluster to my GitLab CI/CD Kubernetes integration. I can execute kubectl commands on the cluster from my pc, after I ran this command: az aks get-credentials --resource-group <resource-group-name> --name <kubernetes-cluster-name> It created a .kube/config file with a content like this: apiVersion: v1 clusters: - cluster: certificate-authority-data: <some long base64 string here> server: https://<resource-group-name+some-hexadecimal-chars>.hcp

问题 I have an umbrella chart with multiple sub-charts, I simply want to make sure that subchart1 runs before subchart2, etc. How can we define the order of subchart execution? Seems like hook-weights only apply relative to the chart that declares them. 回答1: Here is a part of the Helm documentation related to execution order of charts: The above sections explain how to specify chart dependencies, but how does this affect chart installation using helm install and helm upgrade? Suppose that a chart

问题 So I am trying to build a helm chart. in my templates file I've got a file like: apiVersion: v1 kind: ConfigMap metadata: name: config-map data: {{ Do something here to load up a set of files | indent 2 }} I have another directory in my chart: configmaps where a set of json files, that themselves will have templated variables in them: a.json b.json c.json Ultimately I'd like to be sure in my chart I can reference: volumes: - name: config-a configMap: name: config-map items: - key: a.json path