kubernetes-helm

问题 I want to deploy my own image on JuPyter-hub. However, I need to deploy it to some registry so that the image puller of JHub can pull it from there. In my case, the registry is private. Although I am able to push the image to my registry, I don't know how will I make the jupyterhub release and deployment be able to pull the image. I tried reading this doc (https://github.com/jupyterhub/jupyterhub-deploy-docker) but it could not help me understand how am I to add authentication in the jupyter

问题 For the past couple of days we have been experiencing an intermittent deployment failure when deploying (via Helm) to Kubernetes v1.11.2. When it fails, kubectl describe <deployment> usually reports that the container failed to create: Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 1s default-scheduler Successfully assigned default/pod-fc5c8d4b8-99npr to fh1-node04 Normal Pulling 0s kubelet, fh1-node04 pulling image "docker-registry.internal/pod

问题 Situation: - users A, B, C, D - team 1: user A, user B - team 2: user C, user D Desired: - each user has private volume - each team has a shared volume --> users in team can see shared volume - some users, based on permission, can see both shared volumes Searched for quite some time now, do not see a solution in the Docs. Ideas: - Use Namespaces! problem --> can no longer see shared volume of other Namespace 回答1: This is an example of how you would do it. You can use namespaces for the

问题 Trying to install Che in Kubernertes: from: https://www.eclipse.org/che/docs/che-6/kubernetes-single-user.html Deploying Che: helm upgrade --install my-che-installation --namespace my-che-namespace -f ./ Error: Error: This command needs 2 arguments: release name, chart path 回答1: I think the problem is the -f - that is normally used for a values file but it is pointing to a whole dir and not a values file. If you take that out and run helm upgrade --install my-che-installation --namespace my

问题 istio-pilot pod on minikube kubernetes cluster is always in Pending state. Increased CPU=4 and memory=8GB. Still the status of istio-pilot pod is Pending. Is specific change required to run istio on minikube other than the ones mentioned in documentation? 回答1: Resolved the issue . Im running minikube with Virtual box and running minikube with higher memory and CPU does not reflect until minikube is deleted and started with new parameters. Without this it was resulting in Insufficient memory.

问题 helm get --help says that... [ helm get ] can be used to get extended information about the release, including: The values used to generate the release The chart used to generate the release The generated manifest file The extended information bit is somehow foggy but whatever. Now: The values used to generate the release maps to helm get values -a releasename The chart used to generate the release ... maps to?!? The generated manifest file maps to helm get manifest releasename Thanks! Edit 1

问题 Helm is advertised as pretty much "the way to manage the deployment of apps on k8s". We have microservices whith a 1-to-1 mapping of code repo and deployable, and I would find it much more convenient to have the k8s config map along with the code, so that they evolve together, e.g. when adding a new environment variable for a feature flag. However, we maintain instead a single helm charts git repo, that would need to be occasionally updated in sync with the code. What is the best practice:

问题 So I am using the helm chart stable/traefik to deploy a reverse proxy to my cluster. I need to customise it beyond what is possible with the variables I can set for the template. I want to enable the dashboard service while not creating an ingress for it (I set up OpenVPN to access the traefik dashboard only via VPN). Both dashboard-ingress.yaml and dashboard-service.yaml conditionally include the ingress or the respective service based on the same variable {{- if .Values.dashboard.enabled }}

问题 I'd like to allow our developers to pass dynamic arguments to a helm template (Kubernetes job). Currently my arguments in the helm template are somewhat static (apart from certain values) and look like this Args: --arg1 value1 --arg2 value2 --sql-cmd select * from db If I were run a task using the docker container without Kubernetes, I would pass parameters like so: docker run my-image --arg1 value1 --arg2 value2 --sql-cmd "select * from db" Is there any way to templatize arguments in a helm

问题 I'm trying to install Prometheus on my K8S cluster when I run command kubectl get namespaces I got the following namespace: default Active 26h kube-public Active 26h kube-system Active 26h monitoring Active 153m prod Active 5h49m Now I want to create the Prometheus via helm install stable/prometheus --name prom -f k8s-values.yml and I got error: Error: release prom-demo failed: namespaces "default" is forbidden: User "system:serviceaccount:kube-system:default" cannot get resource "namespaces"