blogpost: Gateway API Quickstart with KinD - #53581
Conversation
k8s-ci-robot
added
the
cncf-cla: yes
k8s-ci-robot
added
area/blog
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
6cb88a3 to
1189ec5
Compare
| - A LoadBalancer controller that assigns addresses to LoadBalancer-type Services | ||
| - A Gateway API controller that implements the Gateway API specification | ||
|
|
||
| Cloud-provider-kind also automatically installs the Gateway API Custom Resource Definitions (CRDs) in your cluster. |
There was a problem hiding this comment.
| Cloud-provider-kind also automatically installs the Gateway API Custom Resource Definitions (CRDs) in your cluster. | |
| Cloud-provider-kind can run a Gateway API controller (alpha). Enable it by selecting a Gateway API channel, for example --gateway-channel standard. | |
| Cloud-provider-kind also automatically installs the Gateway API Custom Resource Definitions (CRDs) in your cluster. |
Considering cloud-provider-kind's support for gateway API is alpha, should we clarify it?
https://github.com/kubernetes-sigs/cloud-provider-kind/?tab=readme-ov-file#gateway-api-support-alpha
There was a problem hiding this comment.
cloud-provider-kind defaults to installing the CRDs and running the controller: https://github.com/kubernetes-sigs/cloud-provider-kind/blob/600a7713a50ef910b3910ee812e49e5ac1474837/cmd/app.go#L55
@aojea thoughts?
There was a problem hiding this comment.
@jayeshmahajan Antonio fixed it on cloud-provider-kind README
There was a problem hiding this comment.
yeah, sorry, forget to update the docs but we consider gateway api now officially supported in kind, thanks for catching this
| - `ResolvedRefs=False` with reason `BackendNotFound` - The backend Service doesn't exist or has the wrong name | ||
| - `Accepted=False` - The route couldn't attach to the Gateway (check namespace permissions or hostname matching) | ||
|
|
||
| Example error when a backend is not found: |
There was a problem hiding this comment.
I don't follow how is this related with a Gateway Class.
| --- | ||
| layout: blog | ||
| title: "Experimenting with Gateway API using KinD" | ||
| date: 2025-12-11 |
There was a problem hiding this comment.
The scheduling for feature blog should end on Jan 12, so we will schedule this post after this date.
It's ok to leave this date here since it will be merged as draft first.
| - `ResolvedRefs=False` with reason `BackendNotFound` - The backend Service doesn't exist or has the wrong name | ||
| - `Accepted=False` - The route couldn't attach to the Gateway (check namespace permissions or hostname matching) | ||
|
|
||
| Example error when a backend is not found: |
There was a problem hiding this comment.
I don't follow how is this related with a Gateway Class.
b1e11b0 to
b16671e
Compare
lmktfy
left a comment
lmktfy
left a comment
There was a problem hiding this comment.
Can you get a Gateway maintainer to provide a technical review for this @rikatz?
It's technical enough that I think it's worth getting one (I'm sure you've done a good job, but we ought to check on the content not on the provenance).
Here's some feedback. I think we can merge this even with zero changes, if necessary, but it would be nice to be aligned with the Kubernetes website style guide before we merge.
| This document will guide you through setting up a local experimental environment with [Gateway API](https://gateway-api.sigs.k8s.io/) on [kind](https://kind.sigs.k8s.io/). This setup is designed for learning and testing. It helps you understand Gateway API concepts without production complexity. | ||
|
|
||
| {{< caution >}} | ||
| This is an experimentation learning setup, and must not be used for production. |
There was a problem hiding this comment.
Maybe "should", or explain more about why it's a bad idea.
There was a problem hiding this comment.
added some more details that the components not being suited for production usage.
| Now that your cluster is set up, you can start experimenting with Gateway API resources. | ||
|
|
||
| cloud-provider-kind automatically provisions a GatewayClass called `cloud-provider-kind`. You'll use this class to create your Gateway. | ||
|
|
There was a problem hiding this comment.
nit: we could clarify that kind is not really a cloud provider; it's more that it pretends to be to help with testing / learning.
There was a problem hiding this comment.
added "It is worth noticing that while kind is not a cloud provider, the project is named as cloud-provider-kind as it provides features that simulate a cloud-enabled environment."
b16671e to
d635107
Compare
|
thanks @lmktfy I have pushed a new commit addressing your comments |
|
/lgtm |
k8s-ci-robot
added
the
lgtm
|
LGTM label has been added. DetailsGit tree hash: 77c23290f7f8c79bfa905d0bcbbc38255d02ce18 |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lmktfy The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
approved
6 participants
Description
This PR adds a blog post about experimenting Gateway API with KinD. The idea is to allow users to test, have the feeling of it on their own local machine without needing to deploy a cluster or without needing the burden (right now) to chose an implementation.
Issue
Closes: #