no tcp: {} option - instead spec.listeners{} in the last helm chart values #11270
Labels
needs-kind
Indicates a PR lacks a `kind/foo` label and requires one.
needs-priority
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
Hi, I'm trying to expose custom TCP/UDP port using helm chart option
I pulled and installed this offical helm chart
helm pull oci://ghcr.io/nginxinc/charts/nginx-ingress --untar --version 1.2.0
cd nginx-ingress
nano values.yaml
I want add below redis to values.yaml but there is no tcp: {} option in default values.yaml (as it was in old values.yaml file)
I noticed there is new option appeared: Is that alternative of tcp: {} option???
I tried to add using my custom-values.yaml but still no port exposed
Is there any major update or am I doing fundamentally wrong??
Tasks
The text was updated successfully, but these errors were encountered: