Skip to content

Use Envoy Gateway HTTPRoute in HelmRelease tutorial values example#3247

Open
pipo02mix wants to merge 5 commits into
mainfrom
fix-tutorial-envoy-gateway
Open

Use Envoy Gateway HTTPRoute in HelmRelease tutorial values example#3247
pipo02mix wants to merge 5 commits into
mainfrom
fix-tutorial-envoy-gateway

Conversation

@pipo02mix

Copy link
Copy Markdown
Contributor

The hello-world tutorial's values.yaml example was still built around a plain Ingress. Fixing it

The hello-world tutorial's values.yaml example was still built around a
plain Ingress. Ingress is deprecated on the Giant Swarm platform, and
the current hello-world chart (v3.0.2) exposes a `route:` block that
renders a Gateway API HTTPRoute attached to the shared
`giantswarm-default` Envoy Gateway. Bump the referenced chart version
from 2.9.1 to 3.0.2 (the `route:` block only exists from 3.0.2) and
swap the ingress example for the route example. Also explicitly disable
`ingress.enabled` since the chart defaults it to `true`, which otherwise
causes install failures on clusters without an nginx IngressClass.

Verified end-to-end on gazelle -> operations: HR reconciles, HTTPRoute
lands on operations with Accepted + ResolvedRefs against giantswarm-default.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@pipo02mix pipo02mix requested a review from a team as a code owner July 3, 2026 12:55
@pipo02mix pipo02mix self-assigned this Jul 3, 2026
@pipo02mix pipo02mix requested a review from a team July 3, 2026 12:55
@pipo02mix pipo02mix enabled auto-merge July 3, 2026 12:56
- Rewrite "we have to expose" as "we need to expose" (Microsoft.Contractions).
- Rewrite "tags are not necessarily identical" as "tags aren't necessarily identical" (Microsoft.Contractions).
- Add parentRefs to the docs Vale accept list (Vale.Spelling).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Opsgenie
OTLP
PagerDuty
parentRefs

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Shouldn't be necessary as long as the term is in a code block or in backticks

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

it was failing when I used it even with backsticks, so I did not find other way to please vale

We don't have to deal with most of the configuration options in this case. However, to get the application fully working and see a little demo website deployed to our server, we need to expose it through the cluster's [Envoy Gateway]({{< relref "/tutorials/connectivity/gateway-api" >}}) using a Gateway API `HTTPRoute`. The chart's `route` block renders that `HTTPRoute` for us. Based on our assumptions for this example case, we create a new `values.yaml` file like this:

```yaml
ingress:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Do you want to keep the ingress: line?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

it is a decision we can make and remove support, but I would do it afterwards

@marians

marians commented Jul 3, 2026

Copy link
Copy Markdown
Member

For a getting started, I think it would make sense to show the dedicated happy path and use kubectl gs deploy chart

@pipo02mix

Copy link
Copy Markdown
Contributor Author

For a getting started, I think it would make sense to show the dedicated happy path and use kubectl gs deploy chart

I am ok with that, but here I am just fixing some mistakes; I don't want to rewrite entirely. It can be in an additional step part of diaxtasis effort

Co-authored-by: Fernando Ripoll <fernando@giantswarm.io>
@pipo02mix pipo02mix requested a review from marians July 3, 2026 15:32
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.

2 participants