From 6eb55f8a78318b977420c4bddc1e5a2474ad50ac Mon Sep 17 00:00:00 2001 From: Guillaume Rose Date: Wed, 29 Jul 2020 15:48:42 +0200 Subject: [PATCH] Add details about the default cluster profile --- enhancements/update/cluster-profiles.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/enhancements/update/cluster-profiles.md b/enhancements/update/cluster-profiles.md index 55caeb3ec0..510fdd2071 100644 --- a/enhancements/update/cluster-profiles.md +++ b/enhancements/update/cluster-profiles.md @@ -82,8 +82,8 @@ out of the scope of this design. CLUSTER_PROFILE=[identifier] ``` This environment variable would have to be specified in the CVO deployment. When -no `CLUSTER_PROFILE=[identifier]` variable is specified, the `default` cluster profile -is in effect. +no `CLUSTER_PROFILE=[identifier]` variable is specified, the `self-managed-highly-available` +cluster profile is in effect. The following annotation may be used to include manifests for a given profile: @@ -96,6 +96,8 @@ has been specified. Manifests may support inclusion in multiple profiles by including as many of these annotations as needed. +Manifests must contain at least one inclusion annotation. + For items such as node selectors that need to vary based on a profile, different manifests will need to be created to support each variation in the node selector. This feature will not support including/excluding sections of a manifest. In order to avoid drift and