Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge dev to main #280

Merged
merged 11 commits into from
Mar 15, 2024
Merged

Merge dev to main #280

merged 11 commits into from
Mar 15, 2024

Conversation

gianlucam76
Copy link
Member

Post release v0.26.0

gianlucam76 and others added 11 commits March 5, 2024 14:32
A ClusterSet/Set allows to manage a group of clusters and dynamically
select a subset for deployments based on specific criteria.

It offers the following capabilities:

- Selection: Clusters are chosen using a defined clusterSelector;
- Capping: A field named maxReplicas specifies the maximum number of clusters to be
selected from the pool matching the clusterSelector.
- Failover: If a selected cluster becomes unavailable, another cluster from the
matching pool will be automatically chosen to maintain the desired number of active
clusters (up to the maxReplicas limit).

A ClusterProfile can reference a ClusterSet by specifying its name.
A Profile can reference a Set by specifying its name.

The add-ons defined in the ClusterProfile will be deployed only to the
currently selected clusters within the referenced ClusterSet/Set.
This enables dynamic deployment management based on the available and
healthy clusters in the set.

This feature is particularly useful for scenarios where you want to:

Implement active/passive failover:
Create a ClusterSet/Set with maxReplicas: 1 and have it match two clusters in the clusterSelector.
This ensures only one cluster is active at a time.
If the active cluster goes down, the backup cluster will be automatically selected for deployments.
Adjust field names for ClusterSet/Set Status fields
In certain case it might be convenient to simply list all clusters
that are part of a ClusterSet/Set without using a cluster selector.

This also makes cluster selection inline with ClusterProfile/Profile.

This PR also removes clusterproxy utility IsClusterReady as duplicate
of IsClusterReadyToBeConfigured.
This is a behavior change. Previoulsy, only deleted clusters were not
considered.
…ady-cluster

Matching clusters: only cluster ready to be programmed can be a match
@gianlucam76 gianlucam76 merged commit cf8cc0a into projectsveltos:main Mar 15, 2024
4 checks passed
gianlucam76 added a commit that referenced this pull request Apr 1, 2024
Merge pull request #280 from gianlucam76/main
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant