You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Network Policy resource editor does not need to implement every field present on the resource. The editor should allow updates to the metadata (name, namespace, labels, annotations), the policy type to be updated to deny all ingress and egress traffic, and use match labels on the pod selector to limit the group of pods to which the network policy will apply.
Context
Currently, the Config as Data UI has first-class resource editors for many resources, including for Deployments, Stateful Sets, Services, Service Accounts, Ingress, Roles, and Role Bindings, however, a first-class resource editor has yet to be created for Network Policies. First-class resource editors allow users to add and update Kubernetes resources with a UI versus using YAML.
The text was updated successfully, but these errors were encountered:
Feature Suggestion
Add a first-class Network Policy resource editor.
Possible Implementation
The Network Policy resource editor does not need to implement every field present on the resource. The editor should allow updates to the metadata (name, namespace, labels, annotations), the policy type to be updated to deny all ingress and egress traffic, and use match labels on the pod selector to limit the group of pods to which the network policy will apply.
Context
Currently, the Config as Data UI has first-class resource editors for many resources, including for Deployments, Stateful Sets, Services, Service Accounts, Ingress, Roles, and Role Bindings, however, a first-class resource editor has yet to be created for Network Policies. First-class resource editors allow users to add and update Kubernetes resources with a UI versus using YAML.
The text was updated successfully, but these errors were encountered: