Skip to content

Conversation

pipo02mix
Copy link
Contributor

@pipo02mix pipo02mix commented Oct 15, 2025

Towards https://github.com/giantswarm/giantswarm/issues/34325

@giantswarm/team-cabbage can you help to verify I am not missing something?

@pipo02mix pipo02mix requested a review from a team as a code owner October 15, 2025 11:53
@pipo02mix pipo02mix self-assigned this Oct 15, 2025
@pipo02mix pipo02mix requested a review from a team October 15, 2025 11:53
Copy link
Contributor

@mcharriere mcharriere left a 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.

@pipo02mix pipo02mix requested a review from mcharriere October 16, 2025 07:48
pipo02mix and others added 6 commits October 16, 2025 11:08
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]>
@pipo02mix pipo02mix requested a review from mcharriere October 21, 2025 09:24
Copy link
Contributor

@mcharriere mcharriere left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good!

@pipo02mix pipo02mix enabled auto-merge October 21, 2025 10:01
@pipo02mix pipo02mix added this pull request to the merge queue Oct 21, 2025
Merged via the queue into main with commit 5e62342 Oct 21, 2025
7 checks passed
@pipo02mix pipo02mix deleted the add-gateway-api-docs branch October 21, 2025 14:30
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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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).
Copy link
Member

@ubergesundheit ubergesundheit Oct 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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:

@ubergesundheit
Copy link
Member

Oops seems I was too slow. I'll create another PR for my suggestions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants