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 #304

Merged
merged 11 commits into from
May 17, 2024
Merged

Merge dev to main #304

merged 11 commits into from
May 17, 2024

Conversation

gianlucam76
Copy link
Member

Post release v0.30.0

gianlucam76 and others added 11 commits May 10, 2024 14:05
When reporting conflict, add list of conflicting Clusterprofile/Profiles
A Kubernetes resource can be deployed in a managed cluster only by
a ClusterProfile/Profile instance

Before this PR, if two ClusterProfile/Profile instances:
1. matched the same cluster
2. referenced the same ConfigMap

the resources contained in the ConfigMap were successfully deployed
and neither of the ClusterProfile/Profile instance reported an error.

After this PR, the resources contained in the ConfigMap will still be
successfully deployed. But while the first ClusterProfile/Profile will
succeed, the second one will report a conflict with the first one.

This behavior change is implemented as part of introducing the concept
of tier in ClusterProfile/Profile.
Allowing only one ClusterProfile/Profile instance to deploy a given
Kubernetes resources, allows to handle the scenario where different
ClusterProfile/Profile instances with different tiers want to deploy
the same resource (and let the profile with lower tier win the conflict).
Instead of returning a boolen indicating whether resource exists or not,
return the resource version (only existing objects have that field set).
ValidateObjectForUpdate: Return resource version
@gianlucam76 gianlucam76 merged commit fd98796 into projectsveltos:main May 17, 2024
4 checks passed
gianlucam76 added a commit that referenced this pull request May 28, 2024
Merge pull request #304 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