We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When opening a servicePort on the argocd server, we encounter an issue where the containerPort is enforced as the targetPort for all ports opened.
Chart Config
containerPorts: server: 8080 service: servicePortHttpsName: mesh servicePortHttps: 20000
Resulting Kustomize
- name: http port: 80 protocol: TCP targetPort: 8080 - name: mesh port: 20000 protocol: TCP targetPort: 8080
argo-cd
7.1.3
servicePort
targetPort
I expected the targetPort for the new port to be the same as the new port.
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
When opening a servicePort on the argocd server, we encounter an issue where the containerPort is enforced as the targetPort for all ports opened.
Chart Config
Resulting Kustomize
Related helm chart
argo-cd
Helm chart version
7.1.3
To Reproduce
servicePort
to a different port on the argocd servertargetPort
once helm chart is appliedExpected behavior
I expected the
targetPort
for the new port to be the same as the new port.Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: