-
Notifications
You must be signed in to change notification settings - Fork 3.8k
K8s: Add way of reporting errors when importing policy #2095
Copy link
Copy link
Closed
Labels
area/k8sImpacts the kubernetes API, or kubernetes -> cilium internals translation layers.Impacts the kubernetes API, or kubernetes -> cilium internals translation layers.kind/enhancementThis would improve or streamline existing functionality.This would improve or streamline existing functionality.staleThe stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.
Description
Metadata
Metadata
Assignees
Labels
area/k8sImpacts the kubernetes API, or kubernetes -> cilium internals translation layers.Impacts the kubernetes API, or kubernetes -> cilium internals translation layers.kind/enhancementThis would improve or streamline existing functionality.This would improve or streamline existing functionality.staleThe stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.
Currently, we have no way of notifying users that import Kubernetes NetworkPolicy objects that the policies were unable to be imported by Cilium. For example, when a user imports a NetworkPolicy object with EgressRules that are label-based, which Cilium currently cannot do at this time, no error is returned to the user. Figure out a way of notifying the user about malformed / disallowed policies.