From e53b17cdab273bda7758d19aec1392d310b77405 Mon Sep 17 00:00:00 2001 From: Jeff Peeler Date: Tue, 13 Jun 2017 11:16:50 -0400 Subject: [PATCH] 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 --- contributors/design-proposals/pod-preset.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contributors/design-proposals/pod-preset.md b/contributors/design-proposals/pod-preset.md index 6247c3d1f..094bc7bc6 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/": ""`. +`podpreset.admission.kubernetes.io/podpreset-": ""`. *Why modify all containers in a pod?*