Skip to content

Profile Tiers

This section explains ClusterProfiles and Profiles in Sveltos, focusing on how tiers enable prioritized deployments for resources targeted by multiple configurations.

Efficient Cluster Management with ClusterProfiles and Profiles

Sveltos streamlines application and add-on deployments across your Kubernetes clusters using ClusterProfiles and Profiles. These profiles target a set of managed clusters, simplifying configuration for large groups.

Addressing the Challenge of Subset Modifications

Imagine you need to adjust deployments for a specific subset of clusters within a previously defined group. Traditionally, creating a new profile targeting this subset and including resources already managed by another profile would lead to conflicts. Sveltos wouldn't allow deployment for those overlapping resources.

Introducing Tiers for Conflict Resolution and Priority

Sveltos tiers provide a solution for managing deployment priority when resources are targeted by multiple configurations.

  • Tier Property: Each ClusterProfile/Profile now has a new property called "tier."
  • Deployment Order Control: The tier value dictates the deployment order for resources targeting the same element within a cluster (e.g., a Helm chart or Kubernetes object).
  • Default Behavior: By default, the first configuration to reach the cluster successfully deploys the resource.
  • Tier Overrides: Tiers override this default behavior. In case of conflicts, the configuration with the lowest tier value takes precedence and deploys the resource. Lower tier values represent higher priority deployments. Default Tier Value: The default tier value is 100.

Example

Let's consider a scenario with managed clusters labeled by environment (env:prod) and regions (region:west and region:east).

An initial ClusterProfile named validation-and-monitoring deploys Kyverno (v3.1.1), Prometheus (23.4.0), and Grafana (6.58.9) across all clusters (env:prod).

apiVersion: config.projectsveltos.io/v1alpha1
kind: ClusterProfile
metadata:
  name: validation-and-monitoring
spec:
  clusterSelector: env=prod
  continueOnConflict: true
  helmCharts:
  - repositoryURL:    https://kyverno.github.io/kyverno/
    repositoryName:   kyverno
    chartName:        kyverno/kyverno
    chartVersion:     v3.1.1
    releaseName:      kyverno-latest
    releaseNamespace: kyverno
    helmChartAction:  Install
  - repositoryURL:    https://prometheus-community.github.io/helm-charts
    repositoryName:   prometheus-community
    chartName:        prometheus-community/prometheus
    chartVersion:     23.4.0
    releaseName:      prometheus
    releaseNamespace: prometheus
    helmChartAction:  Install
  - repositoryURL:    https://grafana.github.io/helm-charts
    repositoryName:   grafana
    chartName:        grafana/grafana
    chartVersion:     6.58.9
    releaseName:      grafana
    releaseNamespace: grafana
    helmChartAction:  Install

Now, imagine you want to upgrade Kyverno to version 3.1.4 only in clusters within the region:west area. Creating a new ClusterProfile targeting region:west for Kyverno (v3.1.4) would result in a conflict because both profiles manage Kyverno. By default, the first one wins (validation-and-monitoring), and the upgrade wouldn't occur.

apiVersion: config.projectsveltos.io/v1alpha1
kind: ClusterProfile
metadata:
 name: kyverno
spec:
 clusterSelector: region=west
 helmCharts:
 - repositoryURL:    https://kyverno.github.io/kyverno/
   repositoryName:   kyverno
   chartName:        kyverno/kyverno
   chartVersion:     v3.1.4
   releaseName:      kyverno-latest
   releaseNamespace: kyverno
   helmChartAction:  Install

Resolving the Conflict with Tiers

Sveltos tiers in action

We can leverage tiers to prioritize the upgrade for west regions. Here's a revised ClusterProfile targeting region:west for Kyverno with a tier value of 50 (lower than the default 100):

apiVersion: config.projectsveltos.io/v1alpha1
kind: ClusterProfile
metadata:
  name: kyverno
spec:
  tier: 50
  clusterSelector: region=west
  helmCharts:
  - repositoryURL:    https://kyverno.github.io/kyverno/
    repositoryName:   kyverno
    chartName:        kyverno/kyverno
    chartVersion:     v3.1.4
    releaseName:      kyverno-latest
    releaseNamespace: kyverno
    helmChartAction:  Install

With this configuration, the kyverno ClusterProfile (tier:50) overrides the default validation-and-monitoring profile (tier:100) for Kyverno deployment in west clusters. This ensures Kyverno gets upgraded to version 3.1.4 only in the desired region.

The table below shows a sample cluster state after applying both ClusterProfiles:

+-----------------------------+---------------+------------+----------------+---------+--------------------------------+------------------------------------------+
|           CLUSTER           | RESOURCE TYPE | NAMESPACE  |      NAME      | VERSION |              TIME              |                 PROFILES                 |
+-----------------------------+---------------+------------+----------------+---------+--------------------------------+------------------------------------------+
| default/clusterapi-workload | helm chart    | prometheus | prometheus     | 23.4.0  | 2024-05-14 12:48:20 +0200 CEST | ClusterProfile/validation-and-monitoring |
| default/clusterapi-workload | helm chart    | grafana    | grafana        | 6.58.9  | 2024-05-14 12:48:31 +0200 CEST | ClusterProfile/validation-and-monitoring |
| default/clusterapi-workload | helm chart    | kyverno    | kyverno-latest | 3.1.4   | 2024-05-14 13:01:55 +0200 CEST | ClusterProfile/kyverno                   |
+-----------------------------+---------------+------------+----------------+---------+--------------------------------+------------------------------------------+