-
Notifications
You must be signed in to change notification settings - Fork 1
Skip Validation of Resource References during --dry-run=server #50
Copy link
Copy link
Open
Labels
Q2/2026This topic is relevant for the hackathon in Q2/2026.This topic is relevant for the hackathon in Q2/2026.area/usabilityUsability relatedUsability relatedfast-trackTask that can take a couple of hours or a day to solve.Task that can take a couple of hours or a day to solve.kind/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
Q2/2026This topic is relevant for the hackathon in Q2/2026.This topic is relevant for the hackathon in Q2/2026.area/usabilityUsability relatedUsability relatedfast-trackTask that can take a couple of hours or a day to solve.Task that can take a couple of hours or a day to solve.kind/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 usability
/kind enhancement
/label teamsize/small
/label fast-track
What is the topic about?:
Originally proposed by @maboehm in https://hackmd.io/c-SxOnnDTE-XQbrXnrPprw?both#Skip-Validation-of-Resource-References-during---dry-runserver.
As already discussed in gardener/gardener#12582 (comment) and gardener/gardener#12950, the strict validation of referenced resources makes it impossible for tools like
fluxto create a Shoot and e.g. a referenced Audit ConfigMap, which is not yet present, at the same time, because flux always performs a server-side dry run first. I would propose to consistently make these validations optional on dry-runs and only emit a warnings if the resources do not exist.