Skip to content

Conversation

@vincepri
Copy link
Member

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:


@k8s-ci-robot k8s-ci-robot requested review from justinsb and ncdc August 12, 2019 22:03
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Aug 12, 2019
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vincepri

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

@k8s-ci-robot k8s-ci-robot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Aug 12, 2019
@vincepri vincepri force-pushed the kbv2 branch 8 times, most recently from 983daa8 to 21580cc Compare August 13, 2019 00:29
@vincepri
Copy link
Member Author

@detiber fixed all comments 🙂

@vincepri vincepri force-pushed the kbv2 branch 2 times, most recently from f828bf4 to 720aea4 Compare August 13, 2019 14:54
Signed-off-by: Vince Prignano <[email protected]>
Signed-off-by: Vince Prignano <[email protected]>
Signed-off-by: Vince Prignano <[email protected]>
Signed-off-by: Vince Prignano <[email protected]>
type: object
status:
description: MachineStatus defines the observed state of Machine
description: / [MachineStatus] MachineStatus defines the observed state
Copy link
Contributor

Choose a reason for hiding this comment

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

This generation looks a bit off.

Copy link
Member Author

Choose a reason for hiding this comment

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

This has been shown before as well, we were missing marks on the resources, I added them back given that we'll probably reference these from the gitbook

openAPIV3Schema:
description: / [MachineSet] MachineSet ensures that a specified number of machines
replicas are running at any given time.
description: / [MachineSet] MachineSet is the Schema for the machinesets API
Copy link
Contributor

Choose a reason for hiding this comment

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

Same here with the generation looking off

_ = context.Background()
_ = r.Log.WithValues("machinedeployment", req.NamespacedName)

// your logic here
Copy link
Contributor

Choose a reason for hiding this comment

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

Still a todo to migrate the controller logic here?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah, it's gonna be a different PR

@detiber
Copy link
Contributor

detiber commented Aug 13, 2019

lgtm, @chuckha mind giving this a second set of eyes?

Copy link
Contributor

@chuckha chuckha left a comment

Choose a reason for hiding this comment

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

Nice approach, next PR moves the logic from old controllers to new ones. I was trying to avoid the bazel modifications but I'm not sure I'll get away with that.

Just some comments on the copyright. If you're not using the k/k copyright validator then ignore 'em

Signed-off-by: Vince Prignano <[email protected]>
Signed-off-by: Vince Prignano <[email protected]>
@vincepri
Copy link
Member Author

@detiber @chuckha Is this good to go? I'll start the work to migrate the controllers after this merges

@chuckha
Copy link
Contributor

chuckha commented Aug 13, 2019

@vincepri squash your commits and lgtm

or if you don't want to squash i'll lgtm

@vincepri
Copy link
Member Author

vincepri commented Aug 13, 2019

@chuckha We're not squashing commits anymore, at least within this repository (#1191). Given the large footprint of the PR, I think the commits should be ok?

@chuckha
Copy link
Contributor

chuckha commented Aug 13, 2019

The idea behind that change was that people are responsible for squashing their own commits instead of the merge bot. It was not that we would keep all commits that the dev made while developing because they are usually not particularly meaningful. The general practice is 1 commit for changes 1 for generated file updates, however, if you're happy with these commits no way I'd block on it

@chuckha
Copy link
Contributor

chuckha commented Aug 13, 2019

/lgtm

Thanks!

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 13, 2019
@k8s-ci-robot k8s-ci-robot merged commit 4cb9377 into kubernetes-sigs:master Aug 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants