Skip to content
New issue

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

ArgoCD Helm Chart Enforcing targetPort on all ports #2904

Open
azhangsg opened this issue Aug 30, 2024 · 1 comment
Open

ArgoCD Helm Chart Enforcing targetPort on all ports #2904

azhangsg opened this issue Aug 30, 2024 · 1 comment
Labels
argo-cd bug Something isn't working no-issue-activity

Comments

@azhangsg
Copy link

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

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

Related helm chart

argo-cd

Helm chart version

7.1.3

To Reproduce

  1. Open a servicePort to a different port on the argocd server
  2. Examine the new port's targetPort once helm chart is applied

Expected behavior

I expected the targetPort for the new port to be the same as the new port.

Screenshots

No response

Additional context

No response

@azhangsg azhangsg added the bug Something isn't working label Aug 30, 2024
Copy link

github-actions bot commented Nov 2, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
argo-cd bug Something isn't working no-issue-activity
Projects
None yet
Development

No branches or pull requests

2 participants