-
Notifications
You must be signed in to change notification settings - Fork 1
Extensions: Use controller-runtime abstraction for validating/mutating webhooks #20
Copy link
Copy link
Open
Labels
area/dev-productivityDeveloper productivity related (how to improve development)Developer productivity related (how to improve development)area/qualityOutput qualification (tests, checks, scans, automation in general, etc.) relatedOutput qualification (tests, checks, scans, automation in general, etc.) relatedkind/enhancementEnhancement, improvement, extensionEnhancement, improvement, extensionlifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.teamsize/smallA team of 1-2 people.A team of 1-2 people.
Description
Metadata
Metadata
Assignees
Labels
area/dev-productivityDeveloper productivity related (how to improve development)Developer productivity related (how to improve development)area/qualityOutput qualification (tests, checks, scans, automation in general, etc.) relatedOutput qualification (tests, checks, scans, automation in general, etc.) relatedkind/enhancementEnhancement, improvement, extensionEnhancement, improvement, extensionlifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.teamsize/smallA team of 1-2 people.A team of 1-2 people.
Type
Fields
Give feedbackNo fields configured for issues without a type.
How to categorize this topic?
/area dev-productivity
/area quality
/kind enhancement
/label teamsize/small
What is the topic about?:
Currently we use a custom abstraction for validating/mutating webhooks in the Extensions API, which we can probably replace with the upstream custom validators and mutators provided by controller-runtime. Full details in this issue: