Skip to content

Conversation

@willkutler
Copy link
Contributor

Placements can now be generated by nesting a full labelSelector or clusterSelector YAML under the placement key, in addition to the legacy method of listing key/value pairs under placement. This allows users to specify multiple clusters in the values array of a placement or placementRule, and to use matchLabels instead of matchExpressions (only supported by placement).

Signed-off-by: Will Kutler [email protected]

@willkutler
Copy link
Contributor Author

/hold refactoring to fix code smells

@willkutler willkutler force-pushed the multiple-clusters branch 3 times, most recently from 9f561ec to 152622e Compare January 26, 2023 16:52
@willkutler
Copy link
Contributor Author

/unhold

Copy link
Member

@dhaiducek dhaiducek left a comment

Choose a reason for hiding this comment

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

Thanks! Some initial comments for consideration. Please also update the reference YAML to document these changes.

@willkutler
Copy link
Contributor Author

@mprahl second round of review changes are in the latest commit

@willkutler
Copy link
Contributor Author

@mprahl new review is done

@mprahl
Copy link
Member

mprahl commented Feb 6, 2023

@willkutler this looks great. Just fix that one typo and squash your commits. I'll approve it afterwards.

Placements can now be generated by nesting a full labelSelector or clusterSelector YAML under the `placement` key, in addition to the legacy method of listing key/value pairs under `placement`. This allows users to specify multiple clusters in the values array of a placement or placementRule, and to use matchLabels instead of matchExpressions (only supported by placement).

Signed-off-by: Will Kutler <[email protected]>
@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 6, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

90.9% 90.9% Coverage
0.0% 0.0% Duplication

@willkutler
Copy link
Contributor Author

@mprahl @dhaiducek I think this should be good to go

@openshift-ci
Copy link

openshift-ci bot commented Feb 10, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mprahl, willkutler

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

The pull request process is described 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

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.

4 participants