Skip to content
#

helm

Here are 2,948 public repositories matching this topic...

stephanECD
stephanECD commented Feb 3, 2022

The InstallOrder should contain IngressClass, and it should happen before Ingress. Otherwise a helm install or helm upgrade will produce an error:

Error: UPGRADE FAILED: failed to create resource: admission webhook "vingress.elbv2.k8s.aws" denied the request: invalid ingress class: IngressClass.networking.k8s.io "name-of-ingressclass" not found

Besides that (but that might be

jannfis
jannfis commented Dec 19, 2021

Summary

The Argo CD core mode should allow the user to set a permanent path to a K8s client configuration file, instead of either using ~/.kube/config per default or having to specify --kubeconfig for each command.

Motivation

Some K8s distributions by default install a Kubernetes client CLI (kubectl) which uses a custom path for its configuration. For example, K3s uses `/etc/ran

k3sup
LukasGentele
LukasGentele commented Jan 13, 2020

Is your feature request related to a problem?
"DevSpace should use the current docker behavior for dockerignore:
Dockerfile + .dockerignore
Dockerfile + Dockerfile.dockerignore
Dockerfile.frontend + Dockerfile.frontend.dockerignore
"

Which solution do you suggest?
Delegating the dockerignore file search to Docker if possible, otherwise copying the behavior as best as possible

arkade

Improve this page

Add a description, image, and links to the helm topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the helm topic, visit your repo's landing page and select "manage topics."

Learn more