pkg/webhook
Matt Moore c267dfecb7 This exempts defaulting from the rules governing field immutability. (#191)
Immutable fields with default values may now be changed iff they change is to populate their default value.  This is to support defaulting in the scenario where an object was created long ago and a new field (with a default!) is added.  When controllers attempt to mutate the object status today, this would create a webhook rejection!  With this change, we compare against a freshly defaulted "old" object to exclude newly defaulted fields from the immutability check.

We saw this in knative/serving for the newly added TimeoutSeconds field in Revision (otherwise immutable), which I believe it leading to upgrade testing flakes since post-upgrade Revision status updates will fail.
2018-12-05 13:40:26 -08:00
..
OWNERS Pull the webhook from `knative/serving` into `knative/pkg`. (#23) 2018-07-27 19:03:36 -07:00
certs.go Add webhook svc name to DNSNames of cert (#140) 2018-10-29 11:16:33 -07:00
certs_test.go Add webhook svc name to DNSNames of cert (#140) 2018-10-29 11:16:33 -07:00
helper_test.go Use zaptest logger for our TestLogger (#89) 2018-09-25 21:40:20 -07:00
webhook.go This exempts defaulting from the rules governing field immutability. (#191) 2018-12-05 13:40:26 -08:00
webhook_integration_test.go Make clientAuth of webhook server into a configuration option (#125) 2018-10-24 08:42:31 -07:00
webhook_test.go This exempts defaulting from the rules governing field immutability. (#191) 2018-12-05 13:40:26 -08:00