content large_stringlengths 3 20.5k | url large_stringlengths 53 192 ⌀ | branch large_stringclasses 4
values | source large_stringclasses 53
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
This guide explains how to migrate from the legacy queue control flags to the modern `--filter` flag. The queue control flags are currently aliased to their equivalent `--filter` expressions, but will be deprecated in a future version of Terragrunt. We recommend migrating to `--filter` to take advantage of its more fle... | https://github.com/gruntwork-io/terragrunt/blob/main/docs/src/content/docs/08-migrate/07-queue-to-filter.md | main | terragrunt | [
-0.06220575049519539,
0.0281197689473629,
-0.008312196470797062,
0.008331062272191048,
0.004949832800775766,
-0.040857505053281784,
0.029236607253551483,
-0.1008848175406456,
-0.005154418759047985,
0.05179748684167862,
0.03500092774629593,
-0.09616077691316605,
-0.002747192746028304,
-0.01... | -0.031373 |
Terragrunt can be configured to emit telemetry in [OpenTelemetry](https://opentelemetry.io/) format in the form of traces and metrics. OpenTelemetry tracing is typically used in Terragrunt to analyze performance. For more details on analyzing and optimizing performance, read the dedicated [Performance documentation](/t... | https://github.com/gruntwork-io/terragrunt/blob/main/docs/src/content/docs/06-troubleshooting/02-open-telemetry.md | main | terragrunt | [
-0.005932691507041454,
-0.005308074876666069,
-0.010893577709794044,
0.0035278857685625553,
-0.014193343929946423,
-0.0937785804271698,
-0.009589523077011108,
-0.023948609828948975,
0.017326276749372482,
0.031920190900564194,
-0.004641267005354166,
-0.08327392488718033,
-0.022097434848546982... | 0.110834 |
```yaml version: '3' services: otel-collector: image: otel/opentelemetry-collector:0.94.0 volumes: - ./otel-collector-config.yaml:/etc/otelcol/config.yaml ports: - "4317:4317" # OTLP gRPC receiver - "4318:4318" # OTLP HTTP receiver - "8889:8889" # Prometheus exporter prometheus: image: prom/prometheus:v2.45.3 volumes: ... | https://github.com/gruntwork-io/terragrunt/blob/main/docs/src/content/docs/06-troubleshooting/02-open-telemetry.md | main | terragrunt | [
-0.03319283947348595,
0.0007471158751286566,
-0.012687805108726025,
-0.026645639911293983,
-0.024300120770931244,
-0.1501333862543106,
-0.030926991254091263,
-0.04925931245088577,
0.019669897854328156,
-0.01589653640985489,
0.07268811017274857,
-0.05307779461145401,
-0.04121401160955429,
-... | 0.175814 |
Within the Kubernetes community, the concept of a contributor ladder has been developed to define how individuals can earn formal roles within the project. The Gateway API contributor ladder largely follows the [roles defined by the broader Kubernetes community](https://github.com/kubernetes/community/blob/master/commu... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/contributing/contributor-ladder.md | main | gateway-api | [
-0.06840825825929642,
-0.011977272108197212,
0.059700556099414825,
-0.020556997507810593,
-0.031889140605926514,
0.009447515942156315,
-0.02178456448018551,
-0.02595403976738453,
0.034660205245018005,
0.043259892612695694,
-0.03665969893336296,
-0.062311869114637375,
0.006614352576434612,
... | 0.146072 |
ensure that different companies are represented in these roles. ### Maintainers Gateway API Maintainers are known as [Subproject Owners](https://github.com/kubernetes/community/blob/master/community-membership.md#subproject-owner) within the Kubernetes community. To become a Gateway API Maintainer, the most important t... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/contributing/contributor-ladder.md | main | gateway-api | [
-0.04468660056591034,
-0.0364549495279789,
0.07185066491365433,
-0.022936753928661346,
-0.02949107438325882,
-0.012967872433364391,
-0.055532306432724,
-0.04428891837596893,
0.09535173326730728,
0.05398893356323242,
-0.04447856545448303,
-0.053960420191287994,
-0.010002155788242817,
0.0258... | 0.152428 |
Inspired by [Kubernetes enhancements][enhance], Gateway API provides a process for introducing new functionality or considerable changes to the project. The enhancement process will evolve over time as the project matures. [enhance]: https://github.com/kubernetes/enhancements Enhancements provides the basis of a commun... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/contributing/enhancement-requests.md | main | gateway-api | [
-0.029968826100230217,
0.02727302350103855,
0.077080138027668,
-0.011260136030614376,
-0.008600777015089989,
-0.035861458629369736,
-0.05930917710065842,
-0.010859998874366283,
0.018225019797682762,
0.006794457323849201,
-0.024921884760260582,
0.03487253561615944,
-0.029909485951066017,
-0... | 0.206461 |
This page contains links to all of the meeting notes, design docs and related discussions around the APIs. If you're interested in working towards a formal role in the project, refer to the [Contributor Ladder](/contributing/contributor-ladder/). ## Feedback and Questions For general feedback, questions or to share ide... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/contributing/get-involved.md | main | gateway-api | [
-0.05990970879793167,
0.01597289741039276,
0.02321869134902954,
-0.004023946821689606,
-0.04536524415016174,
-0.022909201681613922,
-0.05085337907075882,
0.013541512191295624,
-0.03269233554601669,
0.023030132055282593,
-0.05878998339176178,
-0.04259181395173073,
-0.025356387719511986,
-0.... | 0.131264 |
With the Gateway API | [video][2022-kubecon-video-3]| | Oct, 2022 | Kubecon 2022 Detroit: Flagger, Linkerd, And Gateway API: Oh My! | [video][2022-kubecon-video-2]| | May, 2022 | Kubecon 2022 Valencia: Gateway API: Beta to GA | [video][2022-kubecon-video-1]| | May, 2021 | Kubecon 2021 Virtual: Google Cloud - Multi-clus... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/contributing/get-involved.md | main | gateway-api | [
-0.018315117806196213,
-0.13293354213237762,
0.05020832642912865,
-0.04344582557678223,
0.009394439868628979,
0.031325776129961014,
-0.050319019705057144,
-0.0760258138179779,
0.016583386808633804,
0.02615700475871563,
-0.03933219239115715,
-0.06269048899412155,
-0.03106101043522358,
-0.06... | 0.134084 |
In Gateway API 1.2+, we will be following a more structured and predictable release cycle that is inspired by the [upstream Kubernetes release cycle](https://kubernetes.io/releases/release/). ## Goals \* Ensure a predictable release schedule that enables 2-3 releases a year \* Minimize the amount of time required from ... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/contributing/release-cycle.md | main | gateway-api | [
-0.013860850594937801,
0.051848139613866806,
0.11748486757278442,
0.007743602152913809,
0.04426490142941475,
-0.02647808939218521,
-0.050573207437992096,
-0.03805680200457573,
0.10835854709148407,
-0.009566930122673512,
-0.03905273228883743,
0.02869194932281971,
-0.04863782599568367,
-0.05... | 0.063104 |
bugs, and gather early feedback on the viability of the release. ## What happens when GEPs are unable to meet a timeline? There will be situations where the above phases and timelines can't be met by a GEP for one reason or another. In special circumstances (particularly, when it is is anticipated that only a little bi... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/contributing/release-cycle.md | main | gateway-api | [
-0.08201522380113602,
0.029460517689585686,
0.07501973956823349,
-0.024020979180932045,
0.07486370205879211,
0.017725065350532532,
-0.08074779063463211,
-0.002189967082813382,
0.027854179963469505,
-0.0084177041426301,
0.051597949117422104,
0.08287639915943146,
-0.04040958732366562,
-0.016... | 0.030776 |
## Project Management We are using the GitHub issues and project dashboard to manage the list of TODOs for this project: \* [Open issues][gh-issues] \* [Project dashboard][gh-dashboard] Issues labeled `good first issue` and `help wanted` are especially good for a first contribution. We use [milestones][gh-milestones] t... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/contributing/devguide.md | main | gateway-api | [
-0.01492389477789402,
-0.01081505324691534,
-0.003877846756950021,
-0.001177050988189876,
0.02461342327296734,
0.014384406618773937,
-0.05711369961500168,
0.028075553476810455,
0.02287198416888714,
0.02838064730167389,
0.007259890902787447,
-0.013052836991846561,
-0.01977861486375332,
0.00... | 0.105157 |
``` [prow-setup]: https://github.com/kubernetes/test-infra/tree/master/config/jobs/kubernetes-sigs/gateway-api ## Post-Development: Pull Request, Documentation, and more Tests ### Submit a Pull Request Gateway API follows a similar pull request process as [Kubernetes](https://github.com/kubernetes/community/blob/master... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/contributing/devguide.md | main | gateway-api | [
-0.08796471357345581,
-0.02614659070968628,
0.02878746949136257,
-0.03044915199279785,
-0.018056225031614304,
-0.042440544813871384,
-0.037437278777360916,
0.036552298814058304,
0.05255848169326782,
0.040658362209796906,
-0.0014145703753456473,
-0.023852555081248283,
-0.03817325085401535,
... | 0.084116 |
shown as a Condition". (we don't need to cover all the conditions). In one or two phrases, API documentation should help a user who is reading the documentation understand what happens when the field is configured, what values can be specified, and what any additional important implications of setting the field may be.... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/contributing/devguide.md | main | gateway-api | [
-0.008100150153040886,
0.08218894153833389,
0.017376061528921127,
-0.06062856689095497,
-0.0034066897351294756,
-0.010844409465789795,
0.005311076063662767,
0.03511158004403114,
0.02190309762954712,
-0.0269002765417099,
-0.02278304472565651,
-0.021114520728588104,
-0.006584255024790764,
0.... | 0.184613 |
// field. // - Passthrough: The TLS session is NOT terminated by the Gateway. This // implies that the Gateway can't decipher the TLS stream except for // the ClientHello message of the TLS protocol. The certificateRefs field // is ignored in this mode. // // Support: Core // // // Notes for implementers: // // Setting... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/contributing/devguide.md | main | gateway-api | [
-0.07942285388708115,
0.10549181699752808,
0.008228622376918793,
0.003670515725389123,
0.000916689052246511,
-0.05037102475762367,
-0.012382096610963345,
0.025547528639435768,
0.05700403079390526,
-0.03915257006883621,
-0.040856242179870605,
-0.018050668761134148,
0.017172448337078094,
0.0... | 0.013662 |
Gateway API aims to adhere to the upstream [Kubernetes Documentation Style Guide](https://kubernetes.io/docs/contribute/style/style-guide/) wherever possible. This guide should be considered an extension of that guide. Whenever there is conflicting guidance, the information contained in this guide has precedence for Ga... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/contributing/style-guide.md | main | gateway-api | [
-0.012025131843984127,
0.04245658591389656,
0.040426500141620636,
-0.003947154618799686,
0.0064339833334088326,
0.024626435711979866,
-0.07238828390836716,
-0.03316378965973854,
0.07962095737457275,
-0.016614297404885292,
-0.05392823740839958,
0.05700981616973877,
-0.043834563344717026,
-0... | 0.09281 |
Gateway Enhancement Proposals (GEPs) serve a similar purpose to the [KEP][kep] process for the main Kubernetes project: 1. Ensure that changes to the API follow a known process and discussion in the OSS community. 1. Make changes and proposals discoverable (current and future). 1. Document design ideas, tradeoffs, deci... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/geps/overview.md | main | gateway-api | [
-0.034985464066267014,
0.0674087330698967,
0.0644744262099266,
-0.08478011935949326,
0.015266098082065582,
-0.02508525550365448,
-0.06627511233091354,
0.025784213095903397,
0.05988698825240135,
0.029012266546487808,
-0.017012571915984154,
-0.015488225035369396,
-0.03697111830115318,
-0.027... | 0.151514 |
in the YAML metadata files accompanying each GEP. ### GEP metadata file Each GEP has a YAML file containing metadata alongside it, please keep it up to date as changes to the GEP occur. In particular, note the `authors`, and `changelog` fields, please keep those up to date. ## Process ### 1. Discuss with the community ... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/geps/overview.md | main | gateway-api | [
0.01822926476597786,
-0.002463742159307003,
0.0585537888109684,
-0.04822905734181404,
0.005426332820206881,
-0.031421076506376266,
-0.02344433031976223,
-0.00939290039241314,
0.06579428911209106,
0.039271317422389984,
-0.016170376911759377,
-0.0014338141772896051,
-0.0467502661049366,
0.02... | 0.096938 |
GEP process will be the most helpful. The shepherd for that GEP will be responsible for initial review, as well as to be available to answer questions for the GEP owner about the process. Being a GEP Shepherd is a reasonably significant time commitment, with the time required scaling up sharply as a GEP becomes more co... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/geps/overview.md | main | gateway-api | [
-0.06279855221509933,
0.08266478031873703,
0.07160375267267227,
-0.03266341984272003,
0.03042936511337757,
-0.06359638273715973,
-0.08204466849565506,
0.07174183428287506,
-0.08052267134189606,
0.019883550703525543,
0.02829541265964508,
-0.026500888168811798,
-0.023251114413142204,
0.02055... | 0.119109 |
shelf" must be reviewed and accepted by the maintainers. > \*\*Warning\*\*: It is \*\*extremely important\*\* that projects which implement > `Experimental` features clearly document that these features may be removed in > future releases. ### 6. `Standard` - Graduate the GEP Once this feature has met the [graduation c... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/geps/overview.md | main | gateway-api | [
-0.03727603331208229,
0.06521692872047424,
0.0550348125398159,
-0.07908487319946289,
0.07833391427993774,
-0.042432062327861786,
-0.09969209879636765,
0.021972736343741417,
-0.03663085401058197,
0.008833779022097588,
0.08941836655139923,
0.008545724675059319,
0.014273895882070065,
-0.00149... | 0.032029 |
feature past `Experimental` is not a forgone conclusion. Before implementing an experimental feature, you should: \* Clearly document that support for the feature is experimental and may disappear in the future. \* Have a plan in place for how you would handle the removal of this feature from the API. [kep]: https://gi... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/geps/overview.md | main | gateway-api | [
-0.027788454666733742,
0.07082591205835342,
0.13622550666332245,
0.040357206016778946,
0.042329754680395126,
-0.023141389712691307,
-0.04509557783603668,
-0.06590258330106735,
-0.009469245560467243,
0.026383548974990845,
0.003535268595442176,
-0.0395003966987133,
-0.015482047572731972,
-0.... | 0.14208 |
Gateway API was originally designed to manage traffic from clients outside the cluster to services inside the cluster -- the \_ingress\_ or [\_north/south\_][north/south traffic] case. Over time, though, interest from [service mesh] users prompted the creation of the GAMMA (\*\*G\*\*ateway \*\*A\*\*PI for \*\*M\*\*esh ... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/mesh/gamma.md | main | gateway-api | [
-0.06706763803958893,
-0.04055682197213173,
0.00046731563634239137,
-0.0427117720246315,
-0.03171491622924805,
-0.016648946329951286,
0.024155491963028908,
-0.0005251612747088075,
0.02409331128001213,
-0.005332801956683397,
-0.06042096018791199,
0.019815722480416298,
0.08713798224925995,
0... | 0.192927 |
{{< details title="Standard Channel since v1.1.0" color="success" >}} The [GAMMA initiative](/docs/mesh/gamma/) work for supporting service mesh use cases has been part of the Standard Channel since v1.1.0 and is considered GA. For more information refer to our [versioning guide](/docs/concepts/versioning/). {{< /detai... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/mesh/mesh-overview.md | main | gateway-api | [
-0.0641542375087738,
0.0009754666243679821,
-0.009531529620289803,
-0.0018319955561310053,
0.006050282157957554,
-0.01764586754143238,
0.03324541822075844,
-0.019008614122867584,
-0.001906289136968553,
-0.0003923317708540708,
-0.026966672390699387,
0.0873761922121048,
0.03508847951889038,
... | 0.158151 |
the same Namespace as the Route. For example, this HTTPRoute would cause all clients of the `smiley` workload in the `fast-clients` Namespace to have a 100ms timeout: ```yaml kind: HTTPRoute metadata: name: smiley-route namespace: fast-clients spec: parentRefs: - name: smiley namespace: faces kind: Service group: core ... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/mesh/mesh-overview.md | main | gateway-api | [
-0.05954000726342201,
-0.0894031748175621,
-0.016584353521466255,
0.010006153024733067,
-0.06403748691082001,
-0.01819789595901966,
-0.009556473232805729,
-0.06361600011587143,
0.058294426649808884,
-0.05265132710337639,
0.04106639698147774,
-0.030395757406949997,
0.04388786852359772,
0.02... | -0.012099 |
The Kubernetes [Service] resource is considerably more complex than people often realize. When you create a Service, typically the cluster machinery will: - Allocate a cluster-wide IP address for the Service itself (its \_cluster IP\_); - Allocate a DNS name for the Service, resolving to the cluster IP (its \_DNS name\... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/mesh/service-facets.md | main | gateway-api | [
-0.022727729752659798,
-0.031220491975545883,
0.020292241126298904,
-0.038231875747442245,
-0.08974532783031464,
0.016801508143544197,
0.019479993730783463,
-0.03226631507277489,
0.11146251112222672,
0.039218705147504807,
-0.08358626067638397,
-0.012251390144228935,
0.010530779138207436,
-... | 0.192613 |
#### How can I get involved with Gateway API? The [community](/contributing/) page keeps track of how to get involved with the project. #### Will Gateway API replace the Ingress API? No. The Ingress API is GA since Kubernetes 1.19. There are no plans to deprecate this API and we expect most Ingress controllers to suppo... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/faq/_index.md | main | gateway-api | [
-0.07093751430511475,
-0.03613981977105141,
-0.000990186003036797,
0.014949753880500793,
-0.0435238778591156,
-0.00047275100951083004,
-0.005644211079925299,
0.017411967739462852,
0.026046080514788628,
0.06582466512918472,
-0.05287061259150505,
-0.01847609505057335,
0.016868548467755318,
-... | 0.23611 |
provide. An API Gateway can be an essential part of an API Management solution. Gateway API can be seen as a way to standardize provisioning of API Gateways. | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/faq/_index.md | main | gateway-api | [
-0.057836029678583145,
0.007263823412358761,
0.03131438046693802,
0.013649189844727516,
0.007603965234011412,
0.02090335823595524,
-0.07651560753583908,
0.008736240677535534,
0.016580702736973763,
-0.008589835837483406,
-0.05039133131504059,
0.007977900095283985,
0.05122803896665573,
-0.00... | 0.169572 |
Gateway API is an official Kubernetes project focused on L4 and L7 routing in Kubernetes. This project represents the next generation of Kubernetes Ingress, Load Balancing, and Service Mesh APIs. From the outset, it has been designed to be generic, expressive, and role-oriented. The overall resource model focuses on 3 ... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/introduction/_index.md | main | gateway-api | [
-0.0306782815605402,
-0.0027713829185813665,
0.013784333132207394,
-0.026837676763534546,
-0.019975997507572174,
0.009794339537620544,
-0.002336249453946948,
-0.003279372351244092,
0.05888209491968155,
0.031238839030265808,
-0.07330778986215591,
0.006646640598773956,
-0.007017485797405243,
... | 0.234097 |
service networking. - \*\*Portable\*\* - This isn't an improvement but rather something that should stay the same. Just as Ingress is a universal specification with [numerous implementations](https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/), Gateway API is designed to be a portable specific... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/introduction/_index.md | main | gateway-api | [
-0.048557572066783905,
0.02122718282043934,
0.039017949253320694,
0.0018373540369793773,
-0.025017766281962395,
0.02689807489514351,
0.036618225276470184,
0.002519903238862753,
0.07311107218265533,
0.04823552444577217,
-0.07718774676322937,
-0.01981862634420395,
0.02598518691956997,
-0.005... | 0.26654 |
to keep things running smoothly. This is the core challenge of Gateway API in a nutshell. ### Use Cases The [example use cases][use-cases] show this role-oriented model at work. Its flexibility allows the API to adapt to vastly different organizational models and implementations while remaining a portable and standard ... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/introduction/_index.md | main | gateway-api | [
-0.035511314868927,
-0.02052111178636551,
0.002053180942311883,
-0.02454495057463646,
0.009763242676854134,
-0.03564975783228874,
-0.00034426600905135274,
0.01172454934567213,
0.10319186747074127,
-0.013138080947101116,
-0.06951604038476944,
0.03751608356833458,
0.04953429475426674,
-0.007... | 0.276733 |
## Overview Each new release of Gateway API is defined with a "bundle version" that represents the Git tag of a release, such as v1.0.0. This contains the following: \* API Types (Go bindings for the resources) \* CRDs (Kubernetes definitions of the resources) ### Release Channels Release channels are used to indicate ... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/versioning.md | main | gateway-api | [
0.017252635210752487,
0.009641585871577263,
0.06933245807886124,
-0.046244774013757706,
0.061691977083683014,
0.005814563017338514,
-0.04182666540145874,
-0.013107928447425365,
0.051418136805295944,
-0.021040447056293488,
0.0239581186324358,
0.057029180228710175,
-0.047835469245910645,
-0.... | 0.160204 |
that graduate to Standard Channel will include a v1 API version as part of that process. The resources that already have a beta API version (v1beta1) are: \* HTTPRoute \* Gateway \* GatewayClass \* ReferenceGrant In the v1.0 release, HTTPRoute, Gateway, and GatewayClass all graduated to include a GA API Version (v1). R... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/versioning.md | main | gateway-api | [
-0.012499473057687283,
-0.057732969522476196,
0.07376149296760559,
0.0019015526631847024,
0.029582059010863304,
-0.012649173848330975,
-0.04750587046146393,
-0.05477902293205261,
0.060182783752679825,
0.0019778546411544085,
-0.04622342437505722,
0.05637231841683388,
-0.04896007478237152,
-... | 0.082869 |
new API version which may include renamed fields or anything else that is valid in a [new Kubernetes API version](https://kubernetes.io/docs/reference/using-api/#api-versioning) ### Major Version (e.g. v0.x to v1.0) \* There are no API compatibility guarantees when the major version changes. ## Graduation Criteria For ... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/versioning.md | main | gateway-api | [
-0.017091261222958565,
0.01991112157702446,
0.10872898995876312,
-0.06926196068525314,
0.011494540609419346,
-0.03842984139919281,
-0.10001517832279205,
-0.03601326420903206,
0.024042902514338493,
0.03808090090751648,
-0.030602797865867615,
-0.04789537563920021,
-0.04277250915765762,
-0.02... | 0.138339 |
This API covers a broad set of features and use cases and has been implemented widely. This combination of both a large feature set and variety of implementations requires clear conformance definitions and tests to ensure the API provides a consistent experience wherever it is used. When considering Gateway API conform... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/conformance.md | main | gateway-api | [
-0.06988950818777084,
-0.021572396159172058,
0.039460163563489914,
0.010362260974943638,
0.021105993539094925,
-0.037318598479032516,
-0.06676991283893585,
-0.0396898053586483,
-0.04055498540401459,
-0.03758380189538002,
-0.04563833028078079,
0.032792795449495316,
0.007301829755306244,
-0.... | 0.151109 |
matches the API specification. Each release contains a set of conformance tests, these will continue to expand as the API evolves. Currently conformance tests cover the majority of Core capabilities in the standard channel, in addition to some Extended capabilities. ### Running Tests There are two main contrasting sets... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/conformance.md | main | gateway-api | [
-0.028210900723934174,
-0.07109206169843674,
-0.017646392807364464,
0.019694870337843895,
0.00518362270668149,
-0.055051349103450775,
-0.12191908061504364,
-0.008009396493434906,
-0.042395662516355515,
-0.0072689056396484375,
-0.00801109243184328,
-0.01566358283162117,
-0.00679511483758688,
... | 0.104338 |
can be done by setting the `--run-test` flag. #### Network Policies In clusters that use [Container Network Interface (CNI) plugins][network\_plugins] which enforce network policies some conformance tests might require custom [`NetworkPolicy`][netpol] resources to be added to the cluster in order to allow the traffic t... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/conformance.md | main | gateway-api | [
0.01770075038075447,
0.01432852353900671,
0.016089316457509995,
0.009679729118943214,
-0.028873033821582794,
-0.023709706962108612,
-0.015787331387400627,
-0.03976970538496971,
-0.018650813028216362,
0.03350336477160454,
-0.07568109780550003,
-0.10491207987070084,
0.012875465676188469,
0.0... | 0.115915 |
## Background In the original design of Kubernetes, Ingress and Service resources were based on a usage model in which the developers who create Services and Ingresses controlled all aspects of defining and exposing their applications to their users. In practice, though, clusters and their infrastructure tend to be sha... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/roles-and-personas.md | main | gateway-api | [
-0.00004163213088759221,
0.0038982960395514965,
0.056856535375118256,
-0.039810750633478165,
-0.031935252249240875,
-0.022053692489862442,
0.0567086860537529,
-0.020457997918128967,
0.09590285271406174,
0.015948861837387085,
-0.06489892303943634,
-0.08760187029838562,
0.028138985857367516,
... | 0.201091 |
to a `Role` in the Kubernetes Role-Based Authentication (RBAC) system and will define resource model responsibility and separation. RBAC is discussed further in the [Security Model] description. [Security Model]: /docs/concepts/security/#rbac | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/roles-and-personas.md | main | gateway-api | [
-0.030279414728283882,
0.009316821582615376,
-0.04330478236079216,
-0.013028334826231003,
-0.029259640723466873,
0.03328416123986244,
0.09199387580156326,
-0.02727818489074707,
0.06266766786575317,
0.0171090979129076,
-0.013371109962463379,
0.008757617324590683,
0.09269927442073822,
0.0527... | 0.211628 |
Gateway API has tooling to facilitate interacting with the resources. ## `ingress2gateway` Interested in seeing what your ingress resources will look like in Gateway API? `ingress2gateway` provides an easy manner to translate provider-specific resources to Gateway API resources. Managed by the Gateway API SIG-Network s... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/tooling.md | main | gateway-api | [
-0.014259925112128258,
-0.002111596055328846,
0.020062794908881187,
0.0362224355340004,
-0.050471335649490356,
-0.03538673743605614,
0.03723783791065216,
0.018530022352933884,
0.019795028492808342,
0.029492352157831192,
-0.07228928804397583,
-0.02382095716893673,
0.005593536421656609,
-0.0... | 0.136845 |
Gateway API is a complex API, solving a complex problem. The designers of Gateway API have done our best to try to meet the dual demands of configuration flexibility and high usability. In order to do that, we've needed to create a number of new ideas and concepts, while still echoing ideas from the rest of Kubernetes.... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/api-overview.md | main | gateway-api | [
-0.0029146592132747173,
0.009652253240346909,
0.019520336762070656,
-0.0005124611780047417,
-0.05203321576118469,
0.016494372859597206,
0.037066083401441574,
-0.04246096312999725,
0.05621529743075371,
0.0005710851401090622,
-0.03569895774126053,
-0.046294406056404114,
0.020743245258927345,
... | 0.205302 |
may omit fields such as addresses, TLS settings. This allows the controller managing the GatewayClass to provide these settings for the user, resulting in a more portable spec. This behaviour will be made clear using the GatewayClass Status object. Gateway objects bind one or more \*\*Addresses\*\* to one or more \*\*L... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/api-overview.md | main | gateway-api | [
-0.03773229941725731,
-0.018803825601935387,
0.0011655236594378948,
-0.03213171288371086,
-0.0729665756225586,
-0.02108355425298214,
0.07661755383014679,
-0.12134817242622375,
0.11568113416433334,
-0.01664017140865326,
-0.0561780110001564,
-0.022791963070631027,
0.04898775368928909,
-0.055... | 0.04146 |
are distinct. \* `HTTPS` Listeners are distinct via the combination of the fields `protocol`, `port`, `hostname`, but there is an additional requirement. If the protocol is `HTTPS`, then you must have a Secret reference that points to a Kubernetes Secret of type `kubernetes.io/tls`. Listeners with different `hostnames`... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/api-overview.md | main | gateway-api | [
0.029454635456204414,
0.01994064450263977,
0.03174392133951187,
-0.021375464275479317,
-0.026044640690088272,
-0.06567371636629105,
0.025169162079691887,
-0.09243573993444443,
0.14005954563617706,
-0.04281130060553551,
-0.06152991205453873,
-0.04277244210243225,
0.018022658303380013,
0.022... | 0.049545 |
her peers to be able to multiplex Routes onto the same Listener. Each Route type has different information that can be used to accomplish this, and these sets of information are called \*\*Routing Discriminators\*\*. More precisely, \*\*Routing discriminators\*\* are the information that can be used to allow multiple R... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/api-overview.md | main | gateway-api | [
-0.020229943096637726,
-0.0629742294549942,
-0.006552630569785833,
-0.011416355147957802,
-0.04372259974479675,
-0.016132213175296783,
0.035674042999744415,
-0.04256332665681839,
0.008451172150671482,
-0.026855776086449623,
-0.019761035218834877,
0.01930021122097969,
0.039308689534664154,
... | 0.055401 |
can limit what \_shapes\_ Routes that can attach to their Gateway can take (via their Kind or their namespace),but they can't force Ana to expose her application. The final decision, and control of the Route object, is always Ana's. The Listener side is intended to ensure that Ana's Route produces a valid configuration... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/api-overview.md | main | gateway-api | [
0.0016713200602680445,
-0.07153697311878204,
-0.02266664430499077,
-0.026906803250312805,
-0.04354175552725792,
-0.0063393330201506615,
0.03793337941169739,
-0.020647775381803513,
-0.016810186207294464,
0.03242854028940201,
-0.03321417421102524,
-0.02479088120162487,
0.026442572474479675,
... | 0.237947 |
Routes in the same namespace as this Gateway may be attached. \* `All` will allow Routes from all Namespaces to be attached. \* `Selector` means that Routes from a subset of Namespaces selected by a Namespace label selector may be attached to this Gateway. When `Selector` is used, the `namespaces.selector` field must b... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/api-overview.md | main | gateway-api | [
-0.016531584784388542,
-0.09867603331804276,
-0.04684288799762726,
0.015218092128634453,
-0.0030964764300733805,
-0.03645065054297447,
0.06133094057440758,
-0.06825996935367584,
0.016366444528102875,
-0.018386757001280785,
-0.007491641212254763,
-0.03443019092082977,
0.00002131927067239303,
... | 0.098645 |
extensions points suffice for a use case, Implementers can choose to create custom Route resources for protocols that are not currently supported in the API. Custom Route types need to share the same fields that core Route types do. These are contained within CommonRouteSpec and RouteStatus. Whenever you are using an e... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/api-overview.md | main | gateway-api | [
-0.0521063432097435,
-0.03448203206062317,
-0.021325616165995598,
0.022727491334080696,
0.061499882489442825,
0.03836052864789963,
-0.05138319358229637,
0.06713040918111801,
-0.043674614280462265,
-0.03306987136602402,
-0.03411272540688515,
0.004644408822059631,
-0.008275520987808704,
0.08... | 0.149845 |
## Listener selection When Routes attach, the process can be thought of as a negotiation between the Listeners designated by the Route in its `parentRef`, and the settings on those Listeners that restrict what Routes can attach. When considering the `parentRef` of a Route, the set of Listeners that the Route \_may\_ at... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/traffic-matching.md | main | gateway-api | [
0.006558201741427183,
-0.13094022870063782,
0.07085074484348297,
0.015126657672226429,
0.052786651998758316,
-0.02761710435152054,
0.09977269917726517,
-0.07840146869421005,
0.03525383025407791,
-0.004517217166721821,
0.006059540901333094,
0.01483019720762968,
0.020104004070162773,
0.00983... | 0.096503 |
specific port: 8080 --- apiVersion: gateway.networking.k8s.io/v1 kind: HTTPRoute metadata: name: wildcard namespace: default spec: parentRefs: - name: example-com rules: - matches: - path: type: prefix value: / backendRefs: - name: prefix port: 8080 ``` Then the `specific` Route will \_only\_ match traffic bound to the... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/traffic-matching.md | main | gateway-api | [
-0.030840102583169937,
-0.006191356107592583,
0.0832732543349266,
-0.05528206378221512,
-0.006345753092318773,
-0.061272624880075455,
0.018583383411169052,
-0.020988184958696365,
0.02408975549042225,
0.009398143738508224,
-0.06230969354510307,
-0.006325291935354471,
0.016289664432406425,
0... | -0.015176 |
One of the biggest problems when using any Kubernetes object is how to know if the state requested by that object (generally encoded in its `spec` stanza) has been accepted, and when the state has been achieved. The current status of most Kubernetes objects is stored in the `status` subresource and stanza, but in Gatew... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/troubleshooting.md | main | gateway-api | [
-0.010756350122392178,
-0.00036436726804822683,
0.001839917153120041,
-0.006634570192545652,
-0.018495552241802216,
-0.013140627183020115,
0.017642362043261528,
-0.07260679453611374,
0.0969037190079689,
0.033023033291101456,
-0.10767651349306107,
-0.03543024882674217,
-0.019986633211374283,
... | 0.200091 |
arrays - on the Gateway object, there is also a Condition per `listener` field, as that status is also complex enough to need further clarification. Conditions are complex enough to be difficult to summarize in a single line, so most `kubectl get` commands cannot summarize them correctly. To check the status, you have ... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/troubleshooting.md | main | gateway-api | [
-0.023085294291377068,
0.07051707804203033,
0.0035526573192328215,
0.0038835813757032156,
-0.04330252856016159,
-0.04875873774290085,
0.017850985750555992,
-0.05250609666109085,
0.0754031389951706,
0.005672328639775515,
-0.06969012320041656,
-0.051169365644454956,
-0.029630478471517563,
-0... | 0.1236 |
## Introduction/Purpose of this document This document is intended to help both users of Gateway API and integrators who build systems that programmatically interact with Gateway API objects to better understand how Gateway API uses hostnames, and what are the most important things to know about these usages. ## Where ... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/hostnames.md | main | gateway-api | [
-0.026775680482387543,
-0.01675427332520485,
-0.001985579263418913,
-0.02370331808924675,
-0.05484776571393013,
-0.10269995778799057,
0.03862506151199341,
-0.041361644864082336,
0.02082758955657482,
-0.02637924812734127,
-0.06703397631645203,
-0.03491738438606262,
0.050892263650894165,
-0.... | 0.162778 |
a Gateway. In order to do this, it includes a Listener stanza like the Gateway object. #### Routes (HTTPRoute, GRPCRoute, and TLSRoute) Some Routes have a `hostnames` field. This field is treated as an `OR` for both hostname intersection and routing discrimination. `hostnames` may include wildcard hostnames. For HTTPRo... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/hostnames.md | main | gateway-api | [
-0.040049877017736435,
-0.04036625474691391,
-0.0006804520962759852,
-0.019586000591516495,
-0.024316489696502686,
-0.08382940292358398,
0.07980633527040482,
-0.049540627747774124,
0.10644200444221497,
-0.018420511856675148,
-0.028715189546346664,
0.019955892115831375,
0.005539332516491413,
... | 0.150297 |
| `\*.example.com` | Less specific wildcard hostname intersects with more specific wildcard hostname | | `\*` | `www.example.com` | `www.example.com` | Match anything intersects with precise hostname | | `\*` | `\*` | `\*` | Match anything intersects with other match anything | ### Traffic and Routing discriminators Ho... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/hostnames.md | main | gateway-api | [
0.03695553541183472,
-0.032194945961236954,
0.05725825950503349,
-0.03915756568312645,
0.027736108750104904,
-0.08456382155418396,
0.12398307025432587,
-0.08789486438035965,
0.007094294298440218,
0.014462277293205261,
-0.06689847260713577,
-0.025999275967478752,
0.05401276797056198,
-0.001... | 0.12311 |
possible - for example, `f\*.com` is not a valid `hostname`, so cannot match `foo.com` as in RFC-2818. Also note that RFC-2818 has the wildcard character `\*` only match a \_single\_ DNS label, rather than multiple. So the SNI behavior \_may be\_ subtly different to the hostname intersection and Listener selection beha... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/hostnames.md | main | gateway-api | [
-0.05538000538945198,
0.008720427751541138,
0.036678992211818695,
-0.0714406669139862,
-0.022033432498574257,
-0.0650273934006691,
0.020542031154036522,
-0.08235007524490356,
0.08565905690193176,
0.013403931632637978,
-0.11955080181360245,
-0.018453026190400124,
0.03795253485441208,
0.0589... | 0.042316 |
SNI matching will fail, because `\*.example.com` on a certificate does \_not\_ match `foo.bar.example.com` as an SNI. | | `\*.example.com` | Terminated | HTTPRoute | `\*.example.com` | ✅ | `\*.example.com` |`foo.bar.example.com` | ❌ | || `\*.example.com` on a certificate does \_not\_ match `foo.bar.example.com` as an S... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/hostnames.md | main | gateway-api | [
-0.032967060804367065,
0.013895760290324688,
0.04002062976360321,
-0.06666386127471924,
-0.0012122776824980974,
-0.0598972886800766,
-0.007368462160229683,
-0.0895635262131691,
0.017185021191835403,
-0.05091993883252144,
-0.018538054078817368,
-0.06846325844526291,
0.10461452603340149,
0.0... | -0.080572 |
calculations that involve a Gateway - Route relationship, a controller MUST always only interact with the full tree of resources. This means that controllers must: \* Be configured with one or more GatewayClasses to watch. ("All GatewayClasses" is fine too, but different GatewayClasses are \_not\_ required to have dist... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/hostnames.md | main | gateway-api | [
0.005188646726310253,
-0.0642189234495163,
-0.050146181136369705,
0.025227319449186325,
-0.03565578535199165,
-0.022252630442380905,
0.08750186860561371,
-0.06864771246910095,
-0.01465081050992012,
0.06605922430753708,
-0.017926039174199104,
-0.05559944361448288,
0.04003949463367462,
-0.04... | 0.022932 |
couple of things: \* `quux.example.com` is \_not\_ included, and, similarly to the wildcard case, will be rejected by the underlying Gateway API implementation even if it \_does\_ resolve to the underlying addresses. Gateway API says that implementations SHOULD NOT create intermediate records like this if it can be avo... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/hostnames.md | main | gateway-api | [
-0.04425882175564766,
-0.013717090710997581,
0.03314242139458656,
-0.004576582461595535,
-0.051984697580337524,
-0.037919431924819946,
-0.01106632687151432,
-0.0440063402056694,
0.05351279675960541,
-0.0009760039974935353,
-0.02595687471330166,
-0.007992951199412346,
0.06718314439058304,
-... | -0.005651 |
Gateway API covers a \_very\_ wide range of use cases (which is both a strength and a weakness!). This page is emphatically \_not\_ meant to be an exhaustive list of these use cases: rather, it is meant to provide some examples that can be helpful to demonstrate how the API can be used. In all cases, it's very importan... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/use-cases.md | main | gateway-api | [
-0.051222868263721466,
-0.016589179635047913,
-0.01206517405807972,
-0.044971536844968796,
-0.023919450119137764,
-0.019459465518593788,
0.010001136921346188,
-0.010992041788995266,
0.048072345554828644,
-0.06784079223871231,
-0.003580132033675909,
-0.03324003890156746,
0.03350325673818588,
... | 0.170343 |
(e.g. [traffic splitting rollouts](/guides/user-guides/traffic-splitting/)). [north/south]: /docs/glossary/#northsouth-traffic ## Multiple applications behind a single Gateway {{< details title="Standard Channel since v0.8.0" >}} The [north/south] use case is fully supported by the Standard Channel since `v0.8.0`. For ... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/use-cases.md | main | gateway-api | [
0.014703655615448952,
-0.05755510553717613,
0.006616153754293919,
-0.1245705783367157,
-0.012302502989768982,
-0.03167824447154999,
-0.06623683124780655,
-0.008914753794670105,
-0.032751474529504776,
-0.009665509685873985,
-0.015200403518974781,
0.08206471800804138,
-0.020192950963974,
-0.... | 0.109314 |
of [routing logic](/guides/user-guides/http-routing/), [traffic splitting rollout](/guides/user-guides/traffic-splitting/), etc., both for [north/south] and for [east/west] routing. [gateway controller]: /docs/glossary/#gateway-controller [Service routing]: /docs/glossary/#service-routing [endpoint routing]: /docs/glos... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/use-cases.md | main | gateway-api | [
0.030956115573644638,
-0.0730905681848526,
-0.04437154531478882,
-0.06807924062013626,
-0.0451798290014267,
0.019801242277026176,
-0.028658606112003326,
0.028030117973685265,
-0.022718574851751328,
0.025146208703517914,
-0.0076842582784593105,
0.09024608880281448,
-0.03562169522047043,
-0.... | 0.088474 |
## Introduction Gateway API has been designed to enable granular authorization for each role in a typical organization. ## Resources Gateway API has 3 primary API resources: \* \*\*GatewayClass\*\* defines a set of gateways with a common configuration and behavior. \* \*\*Gateway\*\* requests a point where traffic can ... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/security.md | main | gateway-api | [
-0.014085475355386734,
-0.017666339874267578,
-0.03298917040228844,
-0.0485699363052845,
-0.0670594796538353,
0.03212544322013855,
0.08785338699817657,
-0.03430938720703125,
0.05491705238819122,
0.014561006799340248,
-0.062086671590805054,
-0.03222448751330376,
0.0213827732950449,
0.039227... | 0.253794 |
allows references from HTTPRoutes in the "prod" namespace to Services that are deployed in the same namespace as the ReferenceGrant. {{< readfile file="/examples/standard/reference-grant.yaml" code="true" lang="yaml" >}} For more information on ReferenceGrant, refer to our [detailed documentation for this resource](/re... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/security.md | main | gateway-api | [
-0.05595867708325386,
-0.0796862542629242,
-0.042469773441553116,
-0.0011464782292023301,
0.012266721576452255,
-0.006265001837164164,
0.0002982443547807634,
-0.04901286959648132,
0.07580478489398956,
0.005019911099225283,
-0.0064861667342484,
0.04670378193259239,
0.034530941396951675,
-0.... | 0.099779 |
'' - name: allowed\_hostnames\_list expression: | variables.allowed\_hostnames\_str.split(','). map(h, h.trim()).filter(h, size(h) > 0) validations: - expression: | !has(object.spec.hostnames) || size(object.spec.hostnames) == 0 || object.spec.hostnames.all(hostname, hostname in variables.allowed\_hostnames\_list) mess... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/concepts/security.md | main | gateway-api | [
0.024829261004924774,
0.018384840339422226,
-0.0425729863345623,
0.007811246905475855,
0.005812551360577345,
-0.03700728714466095,
-0.00953750591725111,
-0.03238234296441078,
-0.0563293918967247,
0.07434733211994171,
-0.016091568395495415,
-0.08629059791564941,
0.04936269670724869,
0.02236... | 0.086199 |
### Consumer Route A Route bound to a workload's Service by a consumer of a given workload, refining the specific consumer's use of the workload. ### Gateway Controller A \_gateway controller\_ is software that manages the infrastructure associated with routing traffic across contexts using Gateway API, analogous to th... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/glossary/_index.md | main | gateway-api | [
-0.02947983145713806,
-0.056848034262657166,
-0.02498202584683895,
0.009355152025818825,
-0.014241292141377926,
-0.025181597098708153,
0.04324141517281532,
0.010627709329128265,
0.02828633040189743,
0.06739729642868042,
-0.059221044182777405,
0.031090915203094482,
0.00418965145945549,
-0.0... | 0.215432 |
This document tracks downstream implementations and integrations of Gateway API and provides status and resource references for them. Implementors and integrators of Gateway API are encouraged to update this document with status information about their implementations, the versions they cover, and documentation to help... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/implementations/list.md | main | gateway-api | [
-0.06286519765853882,
-0.009087773971259594,
0.019508155062794685,
-0.021729493513703346,
0.026304060593247414,
-0.045610636472702026,
-0.06043320521712303,
0.024149270728230476,
-0.06213068217039108,
-0.003374788910150528,
-0.049434661865234375,
-0.005857556592673063,
-0.022222299128770828,... | 0.121764 |
implementations have uploaded their conformance reports under the [conformance reports](https://github.com/kubernetes-sigs/gateway-api/tree/main/conformance/reports). {{% /alert %}} ## Gateway Controller Implementation Status ### Conformant - [Agentgateway][40] - [Airlock Microgateway][34] - [Calico][46] - [Cilium][16]... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/implementations/list.md | main | gateway-api | [
-0.08297953754663467,
0.015376020222902298,
-0.006021696608513594,
-0.025605618953704834,
-0.017395660281181335,
-0.06996160745620728,
-0.00587433623149991,
-0.04184596985578537,
0.05183110013604164,
0.024021364748477936,
-0.019578374922275543,
-0.021778004243969917,
-0.006709374021738768,
... | 0.170999 |
or nodes. EKS's implementation of the Gateway API is through [AWS Gateway API Controller][eks-gateway] which provisions [Amazon VPC Lattice][vpc-lattice] Resources for gateway(s), HTTPRoute(s) in EKS clusters. [eks]:https://docs.aws.amazon.com/eks/latest/userguide/what-is-eks.html [eks-gateway]:https://github.com/aws/a... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/implementations/list.md | main | gateway-api | [
-0.08471052348613739,
0.03303387388586998,
-0.07673662155866623,
0.049792300909757614,
0.006022195797413588,
0.020610477775335312,
-0.02085566334426403,
-0.017578642815351486,
0.07425236701965332,
0.03122251108288765,
-0.061160020530223846,
-0.009532098658382893,
0.05681817606091499,
-0.05... | 0.160657 |
is a feature-rich, Kubernetes-native ingress controller and next-generation API gateway. Gloo Gateway brings the full power and community support of Gateway API to its existing control-plane implementation. The Gloo Gateway ingress controller passes all the core Gateway API conformance tests in the v1.1.0 release for t... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/implementations/list.md | main | gateway-api | [
-0.05807267501950264,
-0.004753687884658575,
0.01562376506626606,
-0.014490070752799511,
-0.016968753188848495,
-0.05304231122136116,
0.007655385881662369,
-0.012966539710760117,
0.02023678831756115,
0.049761854112148285,
-0.0014818961499258876,
-0.015345321968197823,
-0.0016626896103844047,... | 0.163469 |
is an open source API Gateway built for hybrid and multi-cloud environments. The [Kong Gateway operator (KGO)][kgo] can be used to configure managed Gateways and orchestrate instances of [Kong Kubernetes Ingress Controllers](#kong-kubernetes-ingress-controller). For help and support with Kong Gateway operator please fe... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/implementations/list.md | main | gateway-api | [
-0.0725572481751442,
-0.02705131284892559,
-0.054492153227329254,
0.012520190328359604,
-0.08601955324411392,
-0.013332268223166466,
-0.02406618930399418,
-0.00578905176371336,
-0.02890709787607193,
0.05091468617320061,
-0.01262857485562563,
-0.06509621441364288,
0.02552013099193573,
-0.06... | 0.206633 |
Gateway API. It supports both the `v1alpha2` and `v1beta1` spec of Gateway API. You can refer to [this tutorial][flagger-tutorial] to use Flagger with any implementation of Gateway API. [flagger]: https://flagger.app [flagger-tutorial]: https://docs.flagger.app/tutorials/gatewayapi-progressive-delivery ### cert-manager... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/implementations/list.md | main | gateway-api | [
-0.010883328504860401,
0.012245896272361279,
-0.06977090239524841,
0.013790884055197239,
-0.01626938208937645,
-0.05288920924067497,
-0.01042178738862276,
-0.02815781719982624,
0.025760674849152565,
-0.03903571516275406,
-0.04889800027012825,
-0.06932734698057175,
0.0381360799074173,
0.015... | 0.055942 |
of implementations that are no longer at least partially conformant should contact the Gateway API maintainers to discuss the implementation's status. This period is called the "\*\*right-of-reply\*\*" period, is at least two weeks long, and functions as a lazy consensus period. \* Any implementations that do not respo... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/docs/implementations/list.md | main | gateway-api | [
-0.10588297992944717,
-0.02803267538547516,
0.03135550767183304,
0.008379173465073109,
0.014344418421387672,
-0.06551682949066162,
-0.10001534223556519,
-0.07511135190725327,
0.006118175107985735,
0.017583778128027916,
-0.018661443144083023,
0.0849941149353981,
-0.0525636225938797,
-0.0260... | 0.06576 |
Gateway API is built with CRDs. That comes with a number of significant benefits, notably that each release of Gateway API supports the 5 more recent minor versions of Kubernetes. That means you likely won't need to upgrade your Kubernetes cluster to get the latest version of this API. Unfortunately, this extra flexibi... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/crd-management/_index.md | main | gateway-api | [
-0.020725497975945473,
-0.032589513808488846,
0.04799402877688408,
-0.01571427844464779,
-0.011896412819623947,
0.035304758697748184,
-0.049907997250556946,
-0.016712820157408714,
0.09083518385887146,
0.06235085055232048,
-0.05604521185159683,
-0.02465629205107689,
-0.01067736092954874,
-0... | 0.078657 |
storage version. When a CRD storage version is updated, that only takes effect when the individual resources using that CRD are saved again. For example, if you created a "foo" GatewayClass using Gateway API v0.5.0 CRDs, the storage version of that GatewayClass would be v1alpha2. If that "foo" GatewayClass had never be... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/crd-management/_index.md | main | gateway-api | [
-0.01813358999788761,
-0.008926799520850182,
0.031653303653001785,
-0.03784998878836632,
-0.008092990145087242,
-0.01705675572156906,
-0.07848115265369415,
-0.04320857673883438,
0.010775498114526272,
0.035726215690374374,
-0.00879636686295271,
-0.03826937451958656,
0.017771707847714424,
-0... | -0.048796 |
Everything you wanted to know about building a Gateway API implementation but were too afraid to ask. This document is a place to collect tips and tricks for \_writing a Gateway API implementation\_ that have no straightforward place within the godoc fields of the underlying types. It's also intended to be a place to w... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/implementers-guide/_index.md | main | gateway-api | [
-0.08092115074396133,
0.01163662038743496,
0.007761453744024038,
0.010076525621116161,
-0.023777546361088753,
-0.006754795555025339,
-0.01915431022644043,
-0.014147083275020123,
0.04233517870306969,
0.05131905898451805,
-0.052063651382923126,
-0.02942797914147377,
-0.008744772523641586,
-0... | 0.195813 |
Rules and Guidelines ### CRD Management For information on how to manage Gateway API CRDs, including when it is acceptable to bundle CRD installation with your implementation, refer to our [CRD Management Guide](/guides/crd-management/). ### Conformance and Version Compatibility A conformant Gateway API implementation ... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/implementers-guide/_index.md | main | gateway-api | [
-0.0561479851603508,
-0.030587831512093544,
0.02543697878718376,
-0.018688995391130447,
0.02960902824997902,
0.00957917608320713,
-0.11511249095201492,
-0.020376434549689293,
-0.09396852552890778,
-0.034022752195596695,
0.0493878573179245,
0.02352062612771988,
-0.02035420760512352,
0.02908... | 0.000207 |
the conformance suite makes it impossible to claim support for a union feature combination without actually passing the tests that validate it. #### Union features and conformance profiles Union features MUST be included in the `ExtendedFeatures` set of every conformance profile where the combination is applicable. Thi... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/implementers-guide/_index.md | main | gateway-api | [
-0.0716942846775055,
-0.029711026698350906,
0.02755584567785263,
0.0178652536123991,
0.014071056619286537,
-0.0228774081915617,
-0.02033282443881035,
-0.0211458932608366,
-0.07047789543867111,
-0.05917273834347725,
-0.055663324892520905,
-0.0851818323135376,
0.057464707642793655,
0.0322318... | -0.039871 |
to see the exact details of these Conditions on each resource or part thereof. Additionally, the upstream `Conditions` struct contains an optional `observedGeneration` field - implementations MUST use this field and set it to the `metadata.generation` field of the object when the status is generated. This allows users ... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/implementers-guide/_index.md | main | gateway-api | [
-0.10789388418197632,
0.06393461674451828,
0.03533363342285156,
0.005200400482863188,
0.014591848477721214,
-0.061738573014736176,
0.01900438219308853,
-0.06434851139783859,
0.06621182709932327,
-0.0349513441324234,
-0.06872928887605667,
-0.0070813680067658424,
0.04783996194601059,
0.02293... | 0.069365 |
specified by other personas In some organizations, Application Developers are responsible for managing TLS Certificates (see [Roles and Personas](/docs/concepts/roles-and-personas/) for more on this and other roles). To enable this use case, a new controller and CRD would be created. This CRD would link hostnames to us... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/implementers-guide/_index.md | main | gateway-api | [
-0.05670749768614769,
0.03293190151453018,
-0.021165352314710617,
-0.023401964455842972,
-0.0393579937517643,
-0.02328292652964592,
0.012000617571175098,
0.022062689065933228,
0.07923208177089691,
-0.06683765351772308,
0.00034194145700894296,
-0.0951174944639206,
0.07530244439840317,
0.059... | -0.073267 |
### Routes All Route objects share some properties: - They MUST be attached to an in-scope parent for the implementation to consider them reconcilable. - The implementation MUST update the status for each in-scope Route with the relevant Conditions, using the namespaced `parents` field. See the specific Route types for... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/implementers-guide/_index.md | main | gateway-api | [
-0.08006662875413895,
0.02767552062869072,
0.005662496201694012,
0.031945422291755676,
0.039961427450180054,
-0.06373297423124313,
-0.026403438299894333,
-0.06653185933828354,
-0.02290157414972782,
0.07009042799472809,
0.02449883334338665,
0.030361676588654518,
0.0019616445060819387,
-0.02... | 0.050258 |
There are some general design guidelines used throughout this API. {{% alert color="primary" %}} Throughout the Gateway API documentation and specification, keywords such as "MUST", "MAY", and "SHOULD" are used broadly. These should be interpreted as described in RFC 2119. {{% /alert %}} ## Single resource consistency ... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/api-design/_index.md | main | gateway-api | [
0.007179646287113428,
0.020736193284392357,
0.017256993800401688,
0.008691181428730488,
0.020777195692062378,
-0.01580827124416828,
0.011737095192074776,
-0.05418717861175537,
0.12601099908351898,
-0.007648691534996033,
-0.06815733760595322,
-0.029608728364109993,
0.046063534915447235,
-0.... | 0.143884 |
validation is intended to provide immediate feedback to users when they provide an invalid configuration. Write code defensively with the assumption that at least some invalid input (Gateway API resources) will reach your controller. Both Webhook and CRD validation is not fully reliable because it: \* May not be deploy... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/api-design/_index.md | main | gateway-api | [
-0.08424020558595657,
0.059522490948438644,
-0.006899863947182894,
-0.027814440429210663,
-0.041919294744729996,
-0.0200619176030159,
-0.0468795970082283,
-0.017069295048713684,
0.056212663650512695,
-0.003979233559221029,
-0.043696947395801544,
-0.05710203945636749,
0.06325964629650116,
-... | 0.055416 |
{{< details title="Extended Support Feature: ListenerSet" open="true" >}} This feature is part of extended support. For more information on support levels, refer to our [conformance guide](/docs/concepts/conformance/). {{< /details >}} ListenerSets allow teams to define ports, hostnames, and TLS certificates in separat... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/user-guides/listener-set.md | main | gateway-api | [
0.012962955981492996,
-0.03358854353427887,
-0.02749554254114628,
-0.037413474172353745,
-0.010861964896321297,
-0.037088099867105484,
-0.001383199356496334,
-0.024724051356315613,
0.034409720450639725,
-0.02355034276843071,
-0.062032971531152725,
0.003034269204363227,
0.04491272196173668,
... | 0.092255 |
the Listener that takes effect. The rules go like this, continuing on ties. \* Listeners on the parent Gateway take priority over all others. \* The ListenerSet with the earliest creation time takes priority. \* The first ListenerSet alphabetically takes priority. The winning ListenerSet is marked as `Accepted: true`, ... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/user-guides/listener-set.md | main | gateway-api | [
-0.048121098428964615,
-0.048768237233161926,
0.04359281808137894,
-0.02964814566075802,
-0.008203024044632912,
-0.04814166948199272,
0.04497119039297104,
-0.09471197426319122,
0.06411947309970856,
-0.007864461280405521,
-0.03606228530406952,
0.06766380369663239,
0.03254352882504463,
-0.00... | 0.005691 |
{{< details title="Extended Support Feature: HTTPRouteRequestMirror" open="true" >}} This feature is part of extended support. For more information on support levels, refer to our [conformance guide](/docs/concepts/conformance/). {{< /details >}} The [HTTPRoute resource](/reference/api-types/httproute/) can be used to ... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/user-guides/http-request-mirroring.md | main | gateway-api | [
-0.07479966431856155,
-0.005620146170258522,
0.00978598278015852,
-0.015720941126346588,
-0.041343096643686295,
-0.09070063382387161,
-0.062424905598163605,
-0.015997378155589104,
-0.01328458171337843,
0.005998070817440748,
-0.03961179032921791,
0.05078106373548508,
0.002775241155177355,
-... | -0.021197 |
{{< details title="Extended Support Feature: HTTPRouteRequestTimeout" open="true" >}} This feature is part of extended support. For more information on support levels, refer to our [conformance guide](/docs/concepts/conformance/). {{< /details >}} The [HTTPRoute resource](/reference/api-types/httproute/) can be used to... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/user-guides/http-timeouts.md | main | gateway-api | [
-0.041220102459192276,
0.06936051696538925,
-0.028600022196769714,
0.062035463750362396,
-0.025754394009709358,
-0.02547278068959713,
-0.12295509874820709,
0.0029788496904075146,
0.022247271612286568,
0.008526747114956379,
-0.05102666839957237,
0.047170549631118774,
-0.04911204054951668,
-... | 0.091215 |
{{% alert color="info" title="Experimental Channel" %}} The `TCPRoute` resource described below is currently only included in the "Experimental" channel of Gateway API. For more information on release channels, refer to our [versioning guide](/docs/concepts/versioning/). {{% /alert %}} Gateway API is designed to work w... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/user-guides/tcp.md | main | gateway-api | [
0.0037253929767757654,
0.04715312644839287,
0.023257389664649963,
-0.010592559352517128,
-0.003767710644751787,
-0.004420062061399221,
0.11155173927545547,
0.0035308743827044964,
0.08421149104833603,
0.0000060930847212148365,
-0.0844903513789177,
-0.020641857758164406,
0.05870436504483223,
... | 0.090892 |
Gateway API allows for a variety of ways to configure TLS. This document lays out various TLS settings and gives general guidelines on how to use them effectively. Although this doc covers the most common forms of TLS configuration with Gateway API, some implementations may also offer implementation-specific extensions... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/user-guides/tls.md | main | gateway-api | [
-0.056788403540849686,
0.012206011451780796,
-0.028142089024186134,
-0.0041671390645205975,
-0.1047944575548172,
-0.05703975260257721,
0.004807109944522381,
-0.0019436536822468042,
0.11351729929447174,
-0.05283820629119873,
-0.10532331466674805,
0.044633835554122925,
0.007600196171551943,
... | 0.049976 |
>}} #### Cross namespace certificate references In this example, the Gateway is configured to reference a certificate in a different namespace. This is allowed by the ReferenceGrant created in the target namespace. Without that ReferenceGrant, the cross-namespace reference would be invalid. {{< readfile file="/examples... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/user-guides/tls.md | main | gateway-api | [
-0.07476441562175751,
-0.07114186137914658,
0.008687801659107208,
0.0013905246742069721,
0.04622947424650192,
-0.04395879805088043,
-0.017703356221318245,
-0.034841183573007584,
0.040549784898757935,
-0.03188446909189224,
-0.025904443114995956,
-0.01419847272336483,
0.0551782064139843,
0.0... | -0.048166 |
Gateway to use a set of trusted CA Certificates. There may be some variation in which system certificates are used by each implementation. Refer to documentation from your implementation of choice for more information. {{% alert color="info" title="Restrictions" %}} - Cross-namespace certificate references are not allo... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/user-guides/tls.md | main | gateway-api | [
-0.018659444525837898,
0.0069811721332371235,
0.014035169035196304,
0.0120715806260705,
-0.0010111654410138726,
-0.11454875767230988,
0.0042057642713189125,
-0.005164462141692638,
0.057620976120233536,
-0.015234400518238544,
-0.04399512708187103,
-0.04450879991054535,
0.09939730912446976,
... | 0.000576 |
{{< details title="Extended Support Feature: HTTPRouteMethodMatching" open="true" >}} This feature is part of extended support. For more information on support levels, refer to our [conformance guide](/docs/concepts/conformance/). {{< /details >}} The [HTTPRoute resource](/reference/api-types/httproute/) can be used to... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/user-guides/http-method-matching.md | main | gateway-api | [
-0.08815104514360428,
0.024437246844172478,
0.027098989114165306,
-0.016831684857606888,
-0.002196755725890398,
-0.0725058987736702,
-0.047978322952985764,
-0.01925482787191868,
0.010262805968523026,
0.014957165345549583,
-0.050110019743442535,
0.0068700239062309265,
-0.03160301223397255,
... | 0.041493 |
{{< details title="Extended Support Feature: HTTPRouteQueryParamMatching" open="true" >}} This feature is part of extended support. For more information on support levels, refer to our [conformance guide](/docs/concepts/conformance/). {{< /details >}} The [HTTPRoute resource](/reference/api-types/httproute/) can be use... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/user-guides/http-query-param-matching.md | main | gateway-api | [
-0.0775623545050621,
0.032979074865579605,
0.030361836776137352,
0.02865043841302395,
-0.01784246787428856,
-0.038889870047569275,
-0.013192219659686089,
-0.0030994373373687267,
-0.01137783844023943,
0.0031606864649802446,
-0.04433760046958923,
-0.05809421464800835,
0.008145283907651901,
0... | 0.042074 |
[HTTPRoute resources](/reference/api-types/httproute/) can issue redirects to clients or rewrite paths sent upstream using [filters](/reference/api-types/httproute/#filters-optional). This guide shows how to use these features. Note that redirect and rewrite filters are mutually incompatible. Rules cannot use both filt... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/user-guides/http-redirect-rewrite.md | main | gateway-api | [
-0.06597933173179626,
0.007338931784033775,
0.027494871988892555,
0.025320615619421005,
-0.01484801433980465,
-0.04306129366159439,
-0.05321916192770004,
-0.027204034850001335,
-0.004915418103337288,
-0.00393613800406456,
-0.10048767179250717,
0.0060506253503263,
-0.008229191415011883,
0.0... | 0.082563 |
to HTTPS. Here we set `sectionName` to be `http` so it only selects the listener named `http`. {{< readfile file="/examples/standard/http-redirect-rewrite/httproute-redirect-http.yaml" code="true" lang="yaml" >}} You also need an HTTPRoute that attaches to the HTTPS listener that forwards HTTPS traffic to application b... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/user-guides/http-redirect-rewrite.md | main | gateway-api | [
0.02870255336165428,
-0.04425276443362236,
0.012863412499427795,
-0.01081901229918003,
-0.009658558294177055,
-0.05555369332432747,
-0.06579138338565826,
0.001273267436772585,
-0.004636826924979687,
0.01680217683315277,
-0.017675263807177544,
0.02836480922996998,
-0.028024598956108093,
0.0... | -0.009263 |
The [TLSRoute resource](/reference/api-types/tlsroute/) allows you to match on TLS metadata and direct it to Kubernetes backends. This guide shows how the TLSRoute matches traffic on hostname and forwards it to different Kubernetes Services, using either `Passthrough` or `Terminate` TLS modes on the Gateway. In order t... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/user-guides/tls-routing.md | main | gateway-api | [
-0.010897090658545494,
0.022810757160186768,
0.02213308773934841,
-0.013164825737476349,
-0.07014401257038116,
-0.023732827976346016,
0.03760108724236488,
-0.05165674537420273,
0.1616920530796051,
0.017237776890397072,
-0.1192149668931961,
-0.044059496372938156,
0.019035400822758675,
0.010... | 0.048736 |
{{< details title="Extended Support Feature: HTTPRouteCORS" open="true" >}} This feature is part of extended support, and requires your implementation to support the feature `HTTPRouteCORS`. For more information on support levels, refer to our [conformance guide](/docs/concepts/conformance/). {{< /details >}} {{< detai... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/user-guides/http-cors.md | main | gateway-api | [
-0.00901991967111826,
-0.004058392718434334,
-0.02383224293589592,
-0.03687379136681557,
0.06712248176336288,
-0.05636472627520561,
-0.07835451513528824,
-0.03646227344870567,
-0.062152739614248276,
-0.032840561121702194,
-0.01790487952530384,
0.037950050085783005,
-0.06613950431346893,
0.... | 0.015039 |
The [GRPCRoute resource](/reference/api-types/grpcroute/) allows you to match on gRPC traffic and direct it to Kubernetes backends. This guide shows how the GRPCRoute matches traffic on host, header, and service, and method fields and forwards it to different Kubernetes Services. The following diagram describes a requi... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/user-guides/grpc-routing.md | main | gateway-api | [
-0.0014950954355299473,
-0.0869789719581604,
-0.018682396039366722,
-0.082978256046772,
-0.04321012273430824,
-0.027253683656454086,
0.04952438175678253,
-0.020652946084737778,
0.10835709422826767,
0.019138416275382042,
-0.09471464902162552,
0.005978782195597887,
-0.05311444029211998,
0.03... | 0.116495 |
Gateway API has core support for cross Namespace routing. This is useful when more than one user or team is sharing the underlying networking infrastructure, yet control and configuration must be segmented to minimize access and fault domains. Gateways and Routes can be deployed into different Namespaces and Routes can... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/user-guides/multiple-ns.md | main | gateway-api | [
-0.02131684496998787,
-0.08290298283100128,
-0.022119110450148582,
-0.011423085816204548,
-0.037514250725507736,
-0.041267961263656616,
-0.0009502071188762784,
-0.03146733343601227,
0.06383377313613892,
-0.005690983030945063,
-0.041163913905620575,
-0.02983771450817585,
0.02664773538708687,
... | 0.178938 |
`shared-gateway` Gateway into the `infra-ns` Namespace: {{< readfile file="/examples/standard/cross-namespace-routing/gateway.yaml" code="true" lang="yaml" >}} The `https` listener in the above Gateway matches traffic for the `foo.example.com` domain. This allows the infrastructure team to manage all aspects of the dom... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/user-guides/multiple-ns.md | main | gateway-api | [
-0.03351685404777527,
-0.045352280139923096,
-0.004920924548059702,
-0.028514591977000237,
-0.0226358063519001,
-0.10963625460863113,
0.002065132139250636,
-0.04800068959593773,
0.07104994356632233,
0.012092451564967632,
-0.03950563445687294,
0.00013589599984697998,
-0.006632319185882807,
... | 0.12892 |
[HTTPRoute resources](/reference/api-types/httproute/) can modify the headers of HTTP requests and the HTTP responses from clients. There are two types of [filters](/reference/api-types/httproute/#filters-optional) available to meet these requirements: `RequestHeaderModifier` and `ResponseHeaderModifier`. This guide sh... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/user-guides/http-header-modifier.md | main | gateway-api | [
-0.08792179822921753,
0.0715157687664032,
0.005503447726368904,
-0.007857942022383213,
0.021417131647467613,
-0.020916417241096497,
-0.03324229270219803,
0.026808856055140495,
-0.033968329429626465,
-0.006939615122973919,
-0.07375486940145493,
-0.015001615509390831,
0.00218539172783494,
-0... | 0.039689 |
{{< details title="Extended Support Features: HTTPRouteBackendProtocolH2C, HTTPRouteBackendProtocolWebSocket" open="true" >}} These features are part of extended support. For more information on support levels, refer to our [conformance guide](/docs/concepts/conformance/). {{< /details >}} {{< details title="Standard C... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/user-guides/backend-protocol.md | main | gateway-api | [
-0.005693549755960703,
-0.01566247083246708,
-0.025894008576869965,
-0.01939334161579609,
-0.01833316497504711,
0.014325903728604317,
-0.07017319649457932,
-0.002421091077849269,
0.03472215309739113,
0.012971220538020134,
-0.0466495119035244,
0.06130729615688324,
-0.050351787358522415,
-0.... | 0.057293 |
The [HTTPRoute resource](/reference/api-types/httproute/) allows you to match on HTTP traffic and direct it to Kubernetes backends. This guide shows how the HTTPRoute matches traffic on host, header, and path fields and forwards it to different Kubernetes Services. The following diagram describes a required traffic flo... | https://github.com/kubernetes-sigs/gateway-api/blob/main/site/content/en/guides/user-guides/http-routing.md | main | gateway-api | [
-0.002285097260028124,
-0.06632949411869049,
-0.009435388259589672,
-0.04652433097362518,
-0.06689881533384323,
-0.01831645332276821,
-0.0006949507514946163,
-0.016341552138328552,
0.11948022991418839,
0.017297493293881416,
-0.08628620207309723,
-0.000961833808105439,
-0.046465255320072174,
... | 0.095697 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.