-
Notifications
You must be signed in to change notification settings - Fork 34
Add support for generating placement with raw data #93
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
Add support for generating placement with raw data #93
Conversation
|
/hold refactoring to fix code smells |
9f561ec to
152622e
Compare
|
/unhold |
There was a problem hiding this 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.
|
@mprahl second round of review changes are in the latest commit |
|
@mprahl new review is done |
|
@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]>
77e3c2f to
9c30c36
Compare
|
Kudos, SonarCloud Quality Gate passed! |
|
@mprahl @dhaiducek I think this should be good to go |
|
[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 |








Placements can now be generated by nesting a full labelSelector or clusterSelector YAML under the
placementkey, in addition to the legacy method of listing key/value pairs underplacement. 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]