-
Notifications
You must be signed in to change notification settings - Fork 463
*: init apis and client #2
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
*: init apis and client #2
Conversation
ashcrow
left a comment
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.
There is too much to really review in depth, but I perused some of the non generated go code, configs, and shell scripts and they look good.
60fc8ac to
753556d
Compare
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.
if len(configs) == 0 {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.
done
753556d to
1617f80
Compare
There seems to have been some initial uncertainty about what this would be called, with MachinePool first landing in 30d522f (docs: add initial documentation of design, 2018-07-25) and MachineConfigPool first landing in cfc9660 (pkg/apis: add machineconfiguration.openshift.io apis, 2018-07-26, openshift#2). This commit consolidates us around MachineConfigPool, except for the machine-pools/ bootstrap path (since changing that would require consumer updates).
*: use kubecsr mount, add readiness probe to etcd pod
operator-sdk new output
Uh oh!
There was an error while loading. Please reload this page.