gatewayapi docs - #317
Conversation
✅ Deploy Preview for metal-stack-io ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
l0wl3vel
added
area: network
e408dff to
d688f42
Compare
Signed-off-by: Benjamin Ritter <benjamin.ritter@x-cellent.com>
d688f42 to
3bf85bc
Compare
Gerrit91
left a comment
Gerrit91
left a comment
There was a problem hiding this comment.
Thanks for writing this up! Left some comments, which I hope are helpful.
|
|
||
| ### Continued need for an Ingress Controller | ||
|
|
||
| For some vendor dependencies you will still require an ingress controller. Examples of services still relying on Ingress are Gardener and Thanos. As ingress-nginx is EoL we recommend switching to a different Ingress Controller implementation. |
There was a problem hiding this comment.
Gardener does not rely on an ingress controller from third-party.
There was a problem hiding this comment.
Now opened some PRs to get rid off the rest of the ingresses:
|
|
||
| ### Migrating Components | ||
|
|
||
| ::: warning |
There was a problem hiding this comment.
This block is not properly rendered in docusaurus.
| The old Ingress Controller and new Gateway are going to have different IP addresses. | ||
| ::: | ||
|
|
||
| Deploy the `HTTPRoutes` and `TCPRoutes` for each component using metal-role. *routes and Ingress resources can be deployed at the same time. To switch over a service to the Gateway, change the DNS record of that service from pointing to the Ingress Controller to the Gateway. |
There was a problem hiding this comment.
| Deploy the `HTTPRoutes` and `TCPRoutes` for each component using metal-role. *routes and Ingress resources can be deployed at the same time. To switch over a service to the Gateway, change the DNS record of that service from pointing to the Ingress Controller to the Gateway. | |
| Deploy the `HTTPRoute` and `TCPRoute` resources for each component using metal-role. Note that routes and Ingress resources can be deployed at the same time. To switch over a service to the Gateway, change the DNS record of that service from pointing to the Ingress Controller to the Gateway. |
There was a problem hiding this comment.
Hint to unusual parallel deployment parametrization:
metal_deploy_ingress: true
metal_api_httproute_enabled: true
metal_deploy_ingress_api_v1_rules: true
metal_deploy_ingress_api_v2_rules: falseAfter migration toggle metal_deploy_ingress to false.
| - name: metal-control-plane | ||
| sectionName: https | ||
| ``` | ||
|
|
There was a problem hiding this comment.
I was using a gateway resolver for cert-manager to issue certificates and for this scenario I manually copied the existing cert secrets over to the gateway namespace in order to make both services successfully reachable in parallel for a transition time window. Not sure if there is a better solution than that. Otherwise we could just recommend that there will be a short switchover phase where the services are not available until cert-manager was able to solve the DNS challenge for the IP address.
Co-authored-by: Gerrit <Gerrit91@users.noreply.github.com>
Co-authored-by: Gerrit <Gerrit91@users.noreply.github.com>
3 participants
Description
TODO
Used AI-Tools ✨