-
Notifications
You must be signed in to change notification settings - Fork 8
Add Gateway API docs #2848
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
Add Gateway API docs #2848
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks Fer for the contribution. We started working the docs here giantswarm/roadmap#4112. The idea is to expand a bit in different sections, but I think this is a good start.
Co-authored-by: Marian Steinbach <[email protected]>
Co-authored-by: Marian Steinbach <[email protected]>
Co-authored-by: Marian Steinbach <[email protected]>
Co-authored-by: Matías Charrière <[email protected]>
Co-authored-by: Marian Steinbach <[email protected]>
Co-authored-by: Marian Steinbach <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good!
Co-authored-by: Matías Charrière <[email protected]>
version: 0.5.1 | ||
``` | ||
In the configuration, you enable the gateway to be the default ingress method for your cluster. Also, the inference CRDs are installed in the workload cluster. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the configuration, you enable the gateway to be the default ingress method for your cluster. Also, the inference CRDs are installed in the workload cluster. | |
In the configuration, you enable the gateway to be the default ingress method for your cluster. Also, the [Gateway API Inference Extension](https://gateway-api-inference-extension.sigs.k8s.io/) CRDs are installed in the workload cluster. |
In the configuration, you enable the gateway to be the default ingress method for your cluster. Also, the inference CRDs are installed in the workload cluster. | ||
Run `kubectl apply -f` command to install the bundle and way till the app is finally deployed and all the child applications are deployed too (CRDs, envoy gateway and gateway default config). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Run `kubectl apply -f` command to install the bundle and way till the app is finally deployed and all the child applications are deployed too (CRDs, envoy gateway and gateway default config). | |
Run `kubectl apply -f` command on your management cluster to install the bundle and wait untill the app is finally deployed and all the child applications are deployed too (CRDs, envoy gateway and gateway default config). |
|
||
### Using the default gateway | ||
|
||
When you install the Gateway API Bundle, it automatically creates a default Gateway Class called `giantswarm-default` that's pointing to the envoy controller. You can verify it exists: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When you install the Gateway API Bundle, it automatically creates a default Gateway Class called `giantswarm-default` that's pointing to the envoy controller. You can verify it exists: | |
When you install the Gateway API Bundle, it automatically creates a default Gateway Class called `giantswarm-default` that's pointing to the envoy controller. You can verify it exists on your workload cluster: |
Oops seems I was too slow. I'll create another PR for my suggestions |
Towards https://github.com/giantswarm/giantswarm/issues/34325
@giantswarm/team-cabbage can you help to verify I am not missing something?