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

Support dry-run in the admission webhook #1513

Closed
afrittoli opened this issue Nov 2, 2019 · 11 comments
Closed

Support dry-run in the admission webhook #1513

afrittoli opened this issue Nov 2, 2019 · 11 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@afrittoli
Copy link
Member

afrittoli commented Nov 2, 2019

Expected Behavior

I can kubectl diff tekton pipeline resources

Actual Behavior

On the plumbing repo:

$ kubectl diff -f tekton/resources/prerelease_checks.yaml
Error from server (InternalError): Internal error occurred: admission webhook "webhook.tekton.dev" does not support dry run
@vdemeester
Copy link
Member

/kind feature

@tekton-robot tekton-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 9, 2019
@imjasonh
Copy link
Member

Good news! This will be very easy to support once we (bad news!) upgrade to the latest knative/pkg and adopt their new style for expressing webhooks.

Basically it boils down to specifying in the ValidatingAdmissionController YAML that validations don't have side effects.

@vincent-pli
Copy link
Member

@imjasonh
I think knative/pkg still not support this in it's latest webhook implements.

@imjasonh
Copy link
Member

The way knative/serving uses knative/pkg, the config is in YAML instead of Go, so it's easier to configure it to support dry-run: https://github.com/knative/serving/blob/master/config/500-webhook-configuration.yaml

@vincent-pli
Copy link
Member

@imjasonh
I see, you are right, they made a controller for admissionregistration, thanks.

@vincent-pli
Copy link
Member

Could be close, fix by #1894

@afrittoli
Copy link
Member Author

Could be close, fix by #1894

Nice! This ended up in 0.11.0-rc1 - so as soon and I get that deployed, I'll test this one and close if it works.

@tekton-robot
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.

/lifecycle stale

Send feedback to tektoncd/plumbing.

@tekton-robot
Copy link
Collaborator

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

@tekton-robot
Copy link
Collaborator

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Aug 13, 2020
@tekton-robot
Copy link
Collaborator

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

5 participants