feat(gatewayAPI): Stop installing the gateway API by default #14523
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Alex Leong <[email protected]>
alpeb
approved these changes
Sep 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We switch the default value of
installGatewayAPIfrom true to false.This has the effect that for Helm installs and upgrades, we will no longer install the gateway API CRDs by default and will instead depend on them already being installed on the cluster.
For Helm upgrades from 2.18, this is a graceful upgrade because 2.18 added the
helm.sh/resource-policy=keepannotation to these CRDs. This means that even though this default is changing, upgrading from 2.18 will not cause Helm to delete these CRDs.This change has no effect on the Linkerd CLI which was already not installing gateway API CRDs by default.