-
Notifications
You must be signed in to change notification settings - Fork 21
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
Update Services Status for ManagedCluster & MultiClusterService #550
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wahabmk
force-pushed
the
services-status
branch
from
October 24, 2024 13:54
56298a6
to
1f2245c
Compare
This was
linked to
issues
Oct 24, 2024
wahabmk
force-pushed
the
services-status
branch
7 times, most recently
from
October 25, 2024 08:58
01227cd
to
dd44dfa
Compare
wahabmk
force-pushed
the
services-status
branch
2 times, most recently
from
October 25, 2024 10:33
566a97a
to
967c55e
Compare
zerospiel
reviewed
Oct 25, 2024
wahabmk
force-pushed
the
services-status
branch
6 times, most recently
from
October 29, 2024 22:04
01d0736
to
129bd22
Compare
zerospiel
reviewed
Oct 30, 2024
wahabmk
force-pushed
the
services-status
branch
from
October 30, 2024 23:45
129bd22
to
fda90c5
Compare
wahabmk
force-pushed
the
services-status
branch
5 times, most recently
from
October 31, 2024 07:36
14efa75
to
44be7fa
Compare
zerospiel
previously approved these changes
Oct 31, 2024
wahabmk
force-pushed
the
services-status
branch
2 times, most recently
from
October 31, 2024 14:45
55fcc8e
to
bc6ae09
Compare
zerospiel
previously approved these changes
Oct 31, 2024
wahabmk
force-pushed
the
services-status
branch
from
November 4, 2024 19:14
bc6ae09
to
70d429a
Compare
wahabmk
force-pushed
the
services-status
branch
2 times, most recently
from
November 6, 2024 08:42
749fcae
to
ecf91a9
Compare
zerospiel
approved these changes
Nov 6, 2024
eromanova
approved these changes
Nov 7, 2024
wahabmk
force-pushed
the
services-status
branch
from
November 7, 2024 15:23
ecf91a9
to
4e9f82b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds status for services deployment to
ManagedCluster
andMultiClusterService
objects.Examples
Deploy 1 ManagedCluster
The following table shows the status of a
ManagedCluster
object alongside with the status of its associated SveltosClusterSummary
object. TheClusterSummary
-> is owned byProfile
-> is owned byManagedCluster
.Deploy 2 ManagedCluster and 1 MultiClusterService
I have the following:
wali-aws-dev-1
deploying kyverno and ingress-nginx withservicesPriority=100
.wali-aws-dev-2
deploying ingress-nginx withservicesPrriority=500
.global-nginx
(matching both clusters) deploying ingress-nginx withservicesPriority=300
.So in the table below we should see the following in the status of these objects:
wali-aws-dev-1
should show conflict for ingress-nginx and a message indicating that it is being managed by another object. (I.e. ClusterSummary -> which has owner ClusterProfile -> which has the MultiClusterServiceglobal-nginx
as its owner).wali-aws-dev-2
should show no conflicts as it has the highest priority.global-nginx
should show no conflict withwali-aws-dev-1
(as it has higher priority than it) but should show a conflict withwali-aws-dev-2
(as it has lower priority than it)