Skip to content

Add GatewayAPI support & docs#395

Merged
mjudeikis merged 2 commits into
kbind-dev:mainfrom
mjudeikis:mjudeikis/helm.prod.setup
Nov 27, 2025
Merged

Add GatewayAPI support & docs#395
mjudeikis merged 2 commits into
kbind-dev:mainfrom
mjudeikis:mjudeikis/helm.prod.setup

Conversation

@mjudeikis

Copy link
Copy Markdown
Contributor

Summary

Add docs how to deploy in "real world" and add GatewayAPI support vs old ingress.
Dropping TLS support as gateway api default pattern is to terminate.

What Type of PR Is This?

/kind cleanup
/kind feature

Related Issue(s)

Fixes #

Release Notes

Add GatewayAPI support

@mjudeikis mjudeikis requested a review from a team as a code owner November 21, 2025 09:50
coderabbitai[bot]
coderabbitai Bot previously approved these changes Nov 21, 2025
Comment thread docs/content/setup/helm.md Outdated

Note !!!
To install production configuration, you will need to have OIDC provider.
If you interested just to try - check quickstart [quickstart].

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

For more information, just check out the [quickstart guide].

Comment thread docs/content/setup/helm.md Outdated
--values ./deploy/charts/backend/examples/values-local-development.yaml \
kube-bind oci://ghcr.io/kube-bind/charts/backend --version 0.0.0-a50df39d7e4c71f7808f4209ec23f294c5ac8f86
```
helm upgrade --install \

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Let's put --install on its own line, like every other flag 😁

cnvergence
cnvergence previously approved these changes Nov 21, 2025
{{- if .Values.backend.cookieEncryptionKey }}
- --cookie-encryption-key={{ .Values.backend.cookieEncryptionKey }}
{{- end }}
{{- if .Values.backend.tls.enabled }}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

So TLS is simply not supported anymore when using Ingresses? Can you explain your thinking in removing the flags from the chart, but keeping all the TLS code in the backend?

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.

GatewayAPI has TLSRoute, where we would need to do Passthrouth, but its experimental channel (https://gateway-api.sigs.k8s.io/concepts/api-overview/) so it is not installed by default :/ feels like everybody is doing TLS termination these days.

We could do TLS too, but this needs dragging in an experimental feature from the gateway api. And for now, I wanted to keep it simple.

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.

For now - lets keep it in the backend, if somebody would want to use it with this. You can still use it with ServiceType: Loadbalancer

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

if somebody would want to use it with this. You can still use it with ServiceType: Loadbalancer

That was kind of why I asked. Can't we keep all the tls.enabled-guarded YAML intact, for those who want to use the LoadBalancer instead?

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.

make sense. will update

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.

reverted those changes

Comment thread docs/content/setup/helm.md
@mjudeikis mjudeikis enabled auto-merge (squash) November 26, 2025 11:40
@mjudeikis mjudeikis merged commit e1294ba into kbind-dev:main Nov 27, 2025
15 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants