Skip to content

feat(envoy): add two new advanced settings to control migration #57

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
benjaminch wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat(envoy): add two new advanced settings to control migration #57

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 25 additions & 3 deletions docs/configuration/cluster-advanced-settings.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -665,18 +665,40 @@ If you don't specify custom image repository and tag, ensure your cluster includ
---
## Network - Gateway API

<a id="k8s.deploy_api_gateway"></a>

### k8s.deploy_api_gateway

**Cloud Provider:** <img src="/images/logos/cloud-providers/aws-icon.svg" alt="AWS" width="20" style={{display: "inline", verticalAlign: "middle", marginRight: "4px"}} />

**Type:** `boolean`

**Description:** Deploys Gateway API resources on the cluster if true.

<Warning>
- Gateway API will be deployed on the cluster alongside Ingress NGINX
controller, and both will be active. - It will allow you to access your
service using a dedicated service URL pointing to the Gateway API controller
instead of Ingress NGINX controller.
</Warning>

**Default Value:** `false`

<a id="k8s.use_api_gateway"></a>

### k8s.use_api_gateway

**Cloud Provider:** <img src="/images/logos/cloud-providers/aws-icon.svg" alt="AWS" width="20" style={{display: "inline", verticalAlign: "middle", marginRight: "4px"}} />
**Cloud Provider:** <img src="/images/logos/cloud-providers/aws-icon.svg" alt="AWS" width="20" style={{display: "inline", verticalAlign: "middle", marginRight: "4px"}} />

**Type:** `boolean`

**Description:** Flag to deploy Gateway API resources on the cluster.
**Description:** Makes Gateway API the default routing component.

<Warning>
- This is alpha feature, only available on AWS for now and not meant to be used for now but will be handly soon to test ingress to gateway API migration.
- When enabled, all new services will be exposed through Gateway API instead
of Ingress NGINX controller. - NGINX controller will still be deployed in the
cluster an will remain until we've fully migrated to Gateway API, but it will
not be used for routing.
</Warning>

**Default Value:** `false`
Expand Down