helm | The Kubernetes Package Manager | Continuous Deployment library

A CrashloopBackOff means that you have a pod starting, crashing, starting again, and then crashing again.

Maybe the error come from the application itself that it can not connect to database, redis,...

You may find something useful here:

My kubernetes pods keep crashing with "CrashLoopBackOff" but I can't find any log

Your second approach can work, but in a roundabout way, as mikefarah/yq does not support updating multi-line block literals yet

One way to solve this, with the existing constructs would be to do below, without having to create a temporary YAML file

In your ingress.yaml put quotes around the host key.

I found a workaround that requires you to refactor the contents of your global ConfigMap into a template in the umbrellas chart. You won't be able to use regular values from the umbrella chart in your ConfigMap, otherwise you'll get an error when trying to render the template in a subchart; you'll have to use global values instead.

You can use the k8sutil repo, see the apply example:

You may use HELM's lookup function to query the cluster

The lookup function can be used to look up resources in a running cluster. The synopsis of the lookup function is lookup apiVersion, kind, namespace, name -> resource or resource list.

parameter type apiVersion string kind string namespace string name string Both name and namespace are optional and can be passed as an empty string ("").

I replicated your issue and got a similar behaviour on the Ubuntu 20.04.3 OS.

The problem is that NGINX Ingress controller Local testing guide did not mention that demo.localdev.me address points to 127.0.0.1 - that's why it works without editing /etc/hosts or /etc/resolve.conf file. Probably it's something like *.localtest.me addresses:

Here’s how it works. The entire domain name localtest.me—and all wildcard entries—point to 127.0.0.1. So without any changes to your host file you can immediate start testing with a local URL.

Also good and detailed explanation in this topic.

So Docker Desktop / Kubernetes change nothing on your host.

The address demo2.localdev.me also points to 127.0.0.1, so it should work as well for you - and as I tested in my environment the behaviour was exactly the same as for the demo.localdev.me.

You may run nslookup command and check which IP address is pointed to the specific domain name, for example:

The easy way store everything into the file and use it directly first

file oidc.config

It's not possible to directly pass the host's env vars to the pods. I often do that by creating a ConfigMap.

1. Create a ConfigMap with from-lireral option: