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

feat(argo-cd)!: refactor ingress to support any backend service #1826

Closed
wants to merge 1 commit into from
Closed

Conversation

jdomag
Copy link

@jdomag jdomag commented Feb 6, 2023

Resolves:

Signed-off-by: Jacek Domagalski domagalski.j@gmail.com

Note on DCO:

If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.

Checklist:

  • I have bumped the chart version according to versioning
  • I have updated the documentation according to documentation
  • I have updated the chart changelog with all the changes that come with this pull request according to changelog.
  • Any new values are backwards compatible and/or have sensible default.
  • I have signed off all my commits as required by DCO.
  • My build is green (troubleshooting builds).

Changes are automatically published when merged to main. They are not published on branches.

Signed-off-by: Jacek Domagalski <domagalski.j@gmail.com>
@jdomag
Copy link
Author

jdomag commented Feb 6, 2023

Let me know if you think this is the right direction. If so I would adjust not only argo-cd server but other components of argo-cd and their corresponding values

# -- Ingress path type. One of `Exact`, `Prefix` or `ImplementationSpecific`
pathType: Prefix
# -- Additional ingress paths
- path: /
Copy link
Member

@pdrastil pdrastil Feb 18, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the same as extraPaths just below that allow following configuration:

extraPaths:
  - path: /*
     pathType: Prefix
     backend:
       service:
         name: ssl-redirect
         port:
           name: https

@@ -29,36 +29,27 @@ spec:
rules:
{{- if .Values.server.ingress.hosts }}
{{- range $host := .Values.server.ingress.hosts }}
{{- if and $.Values.server.ingressGrpc.isAWSALB $.Values.server.ingressGrpc.enabled }}
{{ $serviceName = printf "%s-grpc" (include "argo-cd.server.fullname" $) }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will break AWS integration. AWS ALB requires 2 ingress routes (1st for http / https, 2nd for grpc traffic targeting grpc service with ALB annotations)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was not aware of this. @pdrastil thanks for review, I will cancel this PR

@jdomag jdomag closed this Feb 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[argo-cd] Add ability to specify backend service in ingress for argocd-server
2 participants