From a0cc5d83409bf48008f1d67f5509d6a4b0fe9a50 Mon Sep 17 00:00:00 2001 From: Paolo Patierno Date: Wed, 9 Jun 2021 14:15:28 +0200 Subject: [PATCH] Fixed CSV deployments label field doc Signed-off-by: Paolo Patierno --- doc/design/building-your-csv.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/design/building-your-csv.md b/doc/design/building-your-csv.md index 7da59ee4f8..277bdf4664 100644 --- a/doc/design/building-your-csv.md +++ b/doc/design/building-your-csv.md @@ -314,7 +314,7 @@ Ensure that the `serviceAccountName` used in the `deployment` spec matches one o Multiple Roles should be described to reduce the scope of any actions needed containers that the Operator may run on the cluster. For example, if you have a component that generates a TLS Secret upon start up, a Role that allows `create` but not `list` on Secrets is more secure than using a single all-powerful Service Account. -It is also possible to set custom labels for Deployment in addition to the system labels set by the OLM. This labels should be present in the `labels` fields of the `deployments` section. +It is also possible to set custom labels for Deployment in addition to the system labels set by the OLM. This labels should be present in the `label` fields of the `deployments` section. Here’s a full example: @@ -323,7 +323,7 @@ Here’s a full example: spec: deployments: - name: example-operator - labels: + label: application: example-operator technology: general spec: