feat(argo-cd ingress): support google managed certificates for gce ingress #1088
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
In our organisation, we would like to use Google ManagedCertificates with GCE Ingress for exposing the ArgoCD web interface for our Developers.
Since the BackendConfig is already supported, I thought the other GKE Custom Resources might be useful for others who want to use GCE ingress, too.
I also added the FrontendConfig resource for setting features like SSL Policies and HTTP to HTTPS redirects on the loadbalancer.
Best regards,
Robert
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:
Changes are automatically published when merged to
master
. They are not published on branches.