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

fix(argo-cd): Allow to use dedicated gRCP ingress with GKE implementation #2541

Merged
merged 1 commit into from Feb 23, 2024

Conversation

pdrastil
Copy link
Member

Resolves: #2540

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).

@pdrastil pdrastil changed the title fix(argo-cd): Allow to use dedicated grpc with GKE implementation fix(argo-cd): Allow to use dedicated grpc ingress with GKE implementation Feb 22, 2024
@pdrastil pdrastil changed the title fix(argo-cd): Allow to use dedicated grpc ingress with GKE implementation fix(argo-cd): Allow to use dedicated gRCP ingress with GKE implementation Feb 22, 2024
Signed-off-by: Petr Drastil <petr.drastil@gmail.com>
@mkilchhofer mkilchhofer merged commit 2f91378 into argoproj:main Feb 23, 2024
6 checks passed
@pdrastil pdrastil deleted the fix/grpc branch February 23, 2024 14:04
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] ingressGrpc shouldn't depend on ingress' controller field
4 participants