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

update placement doc #79

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

elgnay
Copy link
Contributor

@elgnay elgnay commented May 27, 2021

Signed-off-by: Yang Le yangle@redhat.com

@elgnay
Copy link
Contributor Author

elgnay commented May 27, 2021

/assign @qiujian16

Signed-off-by: Yang Le <yangle@redhat.com>
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 11, 2021

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: elgnay
To complete the pull request process, please ask for approval from qiujian16 after the PR has been reviewed.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

// A placement is not satisfied if
// 1) No ManagedClusterSetBinding is found in the placement namespace;
// 2) ClusterSets in spec is specified and none of them is bound to the placement namespace;
// 3) No memeber ManagedCluster is found for all eligible ManagedClusterSets; A ManagedClusterSet
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no ManagedCluster in the ManagedClusterSets specified in the spec. And I do not think you need a and b

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no ManagedCluster in the ManagedClusterSets specified in the spec. And I do not think you need a and b

The above description does not cover the case: placement without Clustersets specified in the spec.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would you like to update a bit on this description?

I think it will be

1) No ManagedClusterSetBinding in the Placement namespace;
2) ClusterSets in the Placement spec is specified and none of them is bound to the namespace of the Placement;
3) No ManagedCluster in the ClusterSets which are specified in the Placement spec or bound to this namespace if ClusterSets is not specified in the Placement spec.
4) No ManagedCluster matches any of the cluster predicates in the Placement spec;
5) NumberOfSelectedClusters in status is less than NumberOfClusters in the Placement spec if it is specified;

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 3, 2021

@elgnay: PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants