clarify mutual exclusivity of service account annotation keys in godoc

Signed-off-by: Anish Ramasekar <anish.ramasekar@gmail.com>

Kubernetes-commit: f7e82d8059d29a279740a03ca2d9a76615632d5d
This commit is contained in:
Anish Ramasekar 2025-03-25 17:30:42 -07:00 committed by Kubernetes Publisher
parent 6fd894d356
commit 560bf1d9f1
1 changed files with 3 additions and 0 deletions

View File

@ -134,6 +134,8 @@ type ServiceAccountTokenAttributes struct {
// additional information required to fetch credentials or allow workloads to opt in to
// using service account tokens for image pull.
// If non-empty, requireServiceAccount must be set to true.
// Keys in this list must be unique.
// This list needs to be mutually exclusive with optionalServiceAccountAnnotationKeys.
// +optional
// +listType=set
RequiredServiceAccountAnnotationKeys []string `json:"requiredServiceAccountAnnotationKeys,omitempty"`
@ -145,6 +147,7 @@ type ServiceAccountTokenAttributes struct {
// the existence of annotations and their values.
// This field is optional and may be empty. Plugins may use this field to extract
// additional information required to fetch credentials.
// Keys in this list must be unique.
// +optional
// +listType=set
OptionalServiceAccountAnnotationKeys []string `json:"optionalServiceAccountAnnotationKeys,omitempty"`