[feat: gw api]Adding docs for L4 routing for gateway api #4232
Conversation
k8s-ci-robot
added
the
cncf-cla: yes
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: shraddhabang The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
approved
shraddhabang
force-pushed
the
l4DocsUpdate
branch
from
827f061 to
7401fa1
Compare
|
/retest pull-aws-load-balancer-controller-unit-test |
|
@shraddhabang: The Use In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/test pull-aws-load-balancer-controller-unit-test |
| !!! warning | ||
| - Only very basic (and not conforming) support of the Gateway API spec currently exists. The team is actively trying to close conformance and support gaps. | ||
| - Using the LBC and Gateway API together is not suggested for production workloads (yet!) | ||
| !!! warning |
There was a problem hiding this comment.
is there anyway to make those warning more obvious, like in a red box?
There was a problem hiding this comment.
This will look this. Its a standard format of displaying the warnings.
| * The Kubernetes Gateway API definition is then translated into an equivalent desired state within AWS (e.g., specific NLB, Listeners, Target Groups etc). | ||
| * This desired state is meticulously compared against the actual state of AWS resources. | ||
| * Necessary AWS API calls are executed to reconcile any identified discrepancies, ensuring the cloud infrastructure matches the Kubernetes declaration. | ||
| 4. **Status Updates:** Following reconciliation, the LBC updates the `status` field of the Gateway API resources in Kubernetes. This provides real-time feedback on the provisioned AWS resources, such as the NLB's DNS name and ARN or if the gateways are accepted or not. |
There was a problem hiding this comment.
we support status update for gateway, gatewayClass and routes.
There was a problem hiding this comment.
Yeah I have mentioned Gateway API resources in Kubernetes which entails these. The DNS name and ARN is just an example. Do not want to go in too much details for each of them right now. What do you think?
|
have a general question, is there anyway we can preview new pages before they are out? to make sure the layout is good or it will work as expected |
Yes. You pull my changes and run |
shraddhabang
force-pushed
the
l4DocsUpdate
branch
from
e751be4 to
2bb1b13
Compare
Description
Checklist
README.md, or thedocsdirectory)BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯