Skip to content

Conversation

mcoletti
Copy link
Contributor

This PR will enable using the CRD to pass in the schedulerName to be used. We use Portworx which leverages the stork scheduler.

@Jan-M
Copy link
Member

Jan-M commented May 27, 2020

(*in)[i].DeepCopyInto(&(*out)[i])
}
}
if in.SchedulerName != nil {
Copy link

@jbagot jbagot Jul 22, 2020

Choose a reason for hiding this comment

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

Hi, I compiled your PR because I'm interested in using it because I have to use stork as well. When I did make docker I'm receiving these errors:
pkg/apis/acid.zalan.do/v1/zz_generated.deepcopy.go:649:22: invalid operation: in.SchedulerName != nil (mismatched types string and nil)
pkg/apis/acid.zalan.do/v1/zz_generated.deepcopy.go:651:8: cannot use new(string) (type *string) as type string in assignment
pkg/apis/acid.zalan.do/v1/zz_generated.deepcopy.go:652:3: invalid indirect of *out (type string)
pkg/apis/acid.zalan.do/v1/zz_generated.deepcopy.go:652:11: invalid indirect of *in (type string)

well, that's the reason Travis failed aswell

Copy link
Member

Choose a reason for hiding this comment

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

run ./hack/update-codegen.sh and maybe make deps in case you get compiler errors

@bbsbb
Copy link
Contributor

bbsbb commented Nov 5, 2020

What is the status on this? Is there intent to get it merged or is there a block I can help with solving around it?

Jan-M pushed a commit that referenced this pull request Nov 25, 2020
* Add ability to specify alternative schedulers via schedulerName.

Co-authored-by: micah.coletti@gmail.com <micah.coletti@gmail.com>
@FxKu FxKu added this to the 1.7 milestone Dec 16, 2020
@FxKu
Copy link
Member

FxKu commented Dec 16, 2020

Just noticed that we merged it with #1226 which looks nearly identical to this one. Thanks again @bbsbb

@FxKu FxKu closed this Dec 16, 2020
@FxKu FxKu modified the milestones: 1.7, 1.6 Dec 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants