-
Notifications
You must be signed in to change notification settings - Fork 2k
Closed
Labels
argo-cdenhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomershelp wantedCommunity help wanted!Community help wanted!
Description
Problem
Unable to specify port for argocd server nodeport Service.
The chart allows to set server.service.type to NodePort. However, we do not choose the port that will be used on each node to run this service.
If we want a reverse proxy or a loadbalancer to point to the argocd, we have to change the port every time we redeploy argocd.
Possible solution
Create a value, for example: server.service.nodeport.port
Other solutions
Maybe using argocd behind a reverse proxy or a loadbalancer is not a good pattern. If so, I am interested in knowing why so ?
Metadata
Metadata
Assignees
Labels
argo-cdenhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomershelp wantedCommunity help wanted!Community help wanted!