Move non-cluster-host typha into the enterprise extension - #5189
Merged
caseydavenport merged 2 commits intoAug 18, 2026
Merged
Conversation
The manager cache already serves nodes and host endpoints, so the autoscaler needs neither its own informers nor a clientset. A replica counter function replaces the noncluster-host flag.
The typha deployment, service, policy, and autoscaler for non-cluster hosts now render from pkg/enterprise/installation.
caseydavenport
force-pushed
the
casey-devariant-noncluster-host
branch
from
August 18, 2026 16:42
0b10d75 to
0311bf6
Compare
Brian-McM
approved these changes
Aug 18, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Description
Non-cluster-host typha now renders from the enterprise installation extension instead of core. What leaves core:
The policy for the non-cluster-host typha still renders alongside the other component policies, same as before.
The typha autoscaler moved to its own package so the enterprise extension can reach it without an import cycle, and it takes a controller-runtime client now instead of a rest.Config plus a clientset.
One behavior change worth calling out: the serving keypair for the non-cluster-host typha is only created when a NonClusterHost resource exists. Before it was created on every reconcile, in both variants.