Skip to content

KOF Gateway API#744

Open
gmlexx wants to merge 1 commit intok0rdent:mainfrom
gmlexx:kof-gateway-api
Open

KOF Gateway API#744
gmlexx wants to merge 1 commit intok0rdent:mainfrom
gmlexx:kof-gateway-api

Conversation

@gmlexx
Copy link
Contributor

@gmlexx gmlexx commented Mar 17, 2026

@gmlexx gmlexx marked this pull request as ready for review March 18, 2026 13:50
@gmlexx gmlexx requested a review from denis-ryzhkov March 18, 2026 13:50
7. Using Gateway API instead of deprecated Nginx Ingress

Both `ingress` and `gateway` are **disabled** by default in the `kof-mothership` chart.
For regional clusters, `ingress-nginx` is **enabled** by default in `kof-regional`.
Copy link
Contributor

Choose a reason for hiding this comment

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

The "option 1" was selected to "make full switch by default to gateway API".

However this docs PR follows the "option 2" which keeps ingress-nginx enabled by default.

I guess we should update both KOF code and docs to follow the option 1:

  • KOF should switch here.
  • No new steps should be added to kof-install as the greenfield deployments will get envoy gateway by default.
  • New step should be added to kof-upgrade fixing the consequences of this instant switch. Please try to suggest these docs, and I could create a script from them. Or I could start doing both in few days.

enabled: true
```
Nginx Ingress will be removed and Envory Gateway be created instead. That might cause a downtime while DNS is propagated from Nginx Ingress to Gateway IP address. If the downtime is not available, consider to deploy a new regional cluster with Gateway API and follow the [migration to a new cluster](kof-upgrade.md#data-migration-to-a-new-regional-cluster)
Copy link
Contributor

Choose a reason for hiding this comment

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

  • "downtime is not available" should be "downtime is not acceptable"
  • "consider deploying" is better:
Suggested change
Nginx Ingress will be removed and Envory Gateway be created instead. That might cause a downtime while DNS is propagated from Nginx Ingress to Gateway IP address. If the downtime is not available, consider to deploy a new regional cluster with Gateway API and follow the [migration to a new cluster](kof-upgrade.md#data-migration-to-a-new-regional-cluster)
Nginx Ingress will be removed and Envory Gateway be created instead. That might cause a downtime while DNS is propagated from Nginx Ingress to Gateway IP address. If the downtime is not acceptable, consider deploying a new regional cluster with Gateway API and following the [migration to a new cluster](kof-upgrade.md#data-migration-to-a-new-regional-cluster)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

Migration to Gateway API documenation

2 participants