diff options
| author | Jeff Peeler <jpeeler@redhat.com> | 2017-06-13 11:16:50 -0400 |
|---|---|---|
| committer | Jeff Peeler <jpeeler@redhat.com> | 2017-06-13 11:16:50 -0400 |
| commit | e53b17cdab273bda7758d19aec1392d310b77405 (patch) | |
| tree | cbdd25407de195992c0174601b3c9fc24784a3fe | |
| parent | c23128b206ce71d9b1967a12c7b0f206add301d6 (diff) | |
Update PodPreset modification annotation format
The new format simply adds a prefix of "podpreset-" to the current
annotation that records what presets have acted on a pod. The new naming
makes it such that there is no chance of collision with the newly
introduced opt-out annotation (or future ones yet to be added).
Opt-out annotation PR:
kubernetes/kubernetes#44965
| -rw-r--r-- | contributors/design-proposals/pod-preset.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/pod-preset.md b/contributors/design-proposals/pod-preset.md index 6247c3d1..094bc7bc 100644 --- a/contributors/design-proposals/pod-preset.md +++ b/contributors/design-proposals/pod-preset.md @@ -220,7 +220,7 @@ changes to `Volumes` apply to the pod spec for all pods matching `Selector`. The resultant modified pod spec will be annotated to show that it was modified by the `PodPreset`. This will be of the form -`podpreset.admission.kubernetes.io/<pip name>": "<resource version>"`. +`podpreset.admission.kubernetes.io/podpreset-<pip name>": "<resource version>"`. *Why modify all containers in a pod?* |