igor-mendix

It is being created as part of the chart that I linked above. I don't know if there is a way to tell helm to wait for ALBC to become...

So I had to redo my deployment scheme to install ALBC chart separately, before `TargetGroupBinding` resource is created. My initial idea to have it as a dependency apparently wouldn't work...

Oooh, thanks a lot! This is indeed a remnant of previous Helm uninstall. I've just checked and it is not getting deleted when I uninstall the chart even though ALBC...

It's all part of a single chart (ALBC is a dependency) and I don't know if there's a way to control the order in which stuff is deleted during uninstall....

My experiments lead me to this: if I delete last `Ingress` resource, ALBC tries to remove the target group it is pointing at. But this TG is created outside k8s...

With the help of someone on Slack I figured that if I only want ALBC to control targets on the TG I don't need `Ingress` resource at all. `Ingress` dictates...

In the nginx access logs they do become escaped: ``` "${${jnd${upper:\xC4\xB1}:ldap:localhost/log4shell_test}" ``` But does it mean they're neutralized?