Skip to content

feat: aggregate SecurityPolicy status from edge - #311

Draft
ecv wants to merge 1 commit into
mainfrom
feat/97-securitypolicy-status-interpreter
Draft

feat: aggregate SecurityPolicy status from edge#311
ecv wants to merge 1 commit into
mainfrom
feat/97-securitypolicy-status-interpreter

Conversation

@ecv

@ecv ecv commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Adds a Karmada ResourceInterpreterCustomization that aggregates gateway.envoyproxy.io/v1alpha1 SecurityPolicy status from member clusters back to the hub, so SecurityPolicies in project control planes surface their edge status condition.

SecurityPolicy uses the Gateway API PolicyStatus shape (status.ancestors[].conditions), identical to BackendTrafficPolicy, so the new block is modeled verbatim on the existing BackendTrafficPolicy interpreter and copies status.ancestors.

Closes #97

SecurityPolicies in project control planes did not surface their edge
status because no Karmada ResourceInterpreterCustomization aggregated
SecurityPolicy status from member clusters back to the hub.

Add a statusAggregation customization for
gateway.envoyproxy.io/v1alpha1 SecurityPolicy, modeled on the existing
BackendTrafficPolicy block. SecurityPolicy uses the Gateway API
PolicyStatus shape, so aggregation copies status.ancestors from the
first member status item.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Propagate security policy status back from edge

1 participant