Skip to content

Move Enterprise istio rendering behind the extensions boundary - #5232

Open
caseydavenport wants to merge 1 commit into
tigera:masterfrom
caseydavenport:casey-istio-render
Open

Move Enterprise istio rendering behind the extensions boundary#5232
caseydavenport wants to merge 1 commit into
tigera:masterfrom
caseydavenport:casey-istio-render

Conversation

@caseydavenport

@caseydavenport caseydavenport commented Aug 20, 2026

Copy link
Copy Markdown
Member

Description

Another variant-gating split. The istio render no longer branches on variant, and the Enterprise extension layers on what only Enterprise installs get:

  • the tigera istio pilot, install-cni, ztunnel and proxyv2 images
  • the waypoint L7 logging resources: the defaults ConfigMap, the two EnvoyFilters, and the EnvoyFilter-writer Role and binding

When waypoint logging is turned off, those five objects are queued for deletion in the order that keeps the RBAC grant alive until the EnvoyFilters are gone. That was already the behavior; it moves into the extension with the rest.

The EnvoyFilter shim types stay in the render package, since the operator registers them in the scheme for the controller-runtime cache.

No behavior change for either variant. Test coverage for the Enterprise pieces moved into the new package alongside the code.

Related: CORE-13396

Release Note

None

The base istio render produces the same objects for both variants. The Enterprise
extension supplies the tigera istio images and the waypoint L7 logging resources,
which move into pkg/enterprise/istio alongside it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants