Add configs for gatewayAPI cluster deployment#164
Open
Conversation
ACLay
requested changes
Apr 23, 2026
Contributor
ACLay
left a comment
ACLay
left a comment
There was a problem hiding this comment.
Can we add a kustomization.yaml file that references all of the other yaml's so that these configs can be deployed automatically by argocd?
Incase it's useful for the prod migration, I used the following commands to get names of gateway httproutes and ingresses for comparison to figure out what hadn't had gateway config deployed:
kubectl get ingress -n apps | grep -Po "^[^ ]+"
kubectl get httproute -n apps | grep -Po "^[^ ]+"
| Envoy Gateway was installed via Helm: | ||
|
|
||
| ```bash | ||
| helm install eg oci://docker.io/envoyproxy/gateway-helm --version v1.7.1 -n envoy-gateway-system --create-namespace |
Contributor
There was a problem hiding this comment.
Can we also add files so that argocd automatically installs the chart? U&A have a couple examples in their message broker component directories.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Closes https://github.com/isisbusapps/docker-orchestration/issues/1024
Uses Helm to deploy Envoy gateway proxy, which also installs the CRDs.
Creates the Gateway class and gateway, which automatically provisions a load balancer using the existing OCCM integration to direct pod traffic.
Created an HTTP route for the messages service to test on the CAPI cluster and Visits frontend HTTP route on the backup cluster.
Runs in parallel with the existing ingress controller for a gradual migration.
We need to add an HTTPRoute file for all the apps and deploy it.