Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add the Network Policy resource editor #243

Open
ChristopherFry opened this issue Jan 31, 2023 · 0 comments
Open

Add the Network Policy resource editor #243

ChristopherFry opened this issue Jan 31, 2023 · 0 comments
Labels
area/ui enhancement New feature or request good first issue Good for newcomers

Comments

@ChristopherFry
Copy link
Collaborator

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.

@ChristopherFry ChristopherFry added enhancement New feature or request good first issue Good for newcomers area/ui labels Jan 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ui enhancement New feature or request good first issue Good for newcomers
Projects
Status: Ready
Development

No branches or pull requests

1 participant