Joe Julian

Ok, I'll go ahead and close this. If circumstances change, feel free to reopen it.

Another good reason, and a potential deadline, gcr.io container-registry is deprecated and is scheduled to be moved to Artifact Registry on May 15, 2024. https://cloud.google.com/container-registry/docs/deprecations/container-registry-deprecation

On the other hand, AWS VPC CNI does't support NetworkPolicy. There are a lot of kubernetes users that use EKS and have no choice but to use that CNI driver.

> Note that the argument against NetworkPolicy (CNI support) may no longer apply Is supporting NetworkPolicy a **_requirement_** for CNI, or is it just an option? If it's optional, should...

> @yxxhero Aslso on another note, i try to utilize the `settings.Debug` flag to adjust this behavior , but since it was declared in main and was not pass down...

> we are not sure whether the new behavior must be opt-in via a flag in accordance with Helm's backward compatibility guidelines My thought on this is that the act...

closing as duplicate of #11369

Since there's been nobody able to step forward and add this feature, I'm going to go ahead and close this with a suggestion. Don't do concurrent actions. Use a fresh...

Since this has sat idle for this long, I'm going to assume this answered your question and close this. I hope it helped.

This falls outside of the realm of what's feasible in helm. To restrict namespaces, use kustomize as a post-renderer, or dry-run and pipe to kubectl -n namespace. This won't really...