-
Notifications
You must be signed in to change notification settings - Fork 422
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
Create certificates, admin kubeconfig, bootstrap token and discoveryhashes using kubeadm #136
Conversation
Hi @awesomenix. Thanks for your PR. I'm waiting for a kubernetes-sigs or kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign @tariq1890 @justaugustus |
/hold I'm at a conference this week, so my availability is going to be limited. |
/ok-to-test |
…t now, this consolidates efforts into upstream, any bug fixes, updates are consumed
Signed-off-by: Stephen Augustus <saugustus@vmware.com>
Thanks @tariq1890 i have removed all the overrides, great suggestion (its much simpler now). Fixed all the lint and test issues, could you please take another look. |
revision = "05914d821849570fba9eacfb29466f2d8d3cd229" | ||
version = "kubernetes-1.13.1" | ||
revision = "74b699b93c15473932b89e3d1818ba8282f3b5ab" | ||
version = "kubernetes-1.13.3" |
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.
Kinda ambivalent towards locking into a Kubernetes dependency without pinning it. Will defer to @justaugustus on that.
If this is agreed upon, Can we change to kubernetes-1.13.4
?
/cc @detiber @chuckha @vincepri @randomvariable |
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.
/hold
(For my review)I'm at a conference this week, so my availability is going to be limited.
@justaugustus anything of particular concern in this PR that we can address?
pkg/apis/azureprovider/v1alpha1/azureclusterproviderconfig_types.go
Outdated
Show resolved
Hide resolved
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.
Overall I think this change looks good, I'd consider moving the two fields I mentioned to status rather than Spec.
pkg/apis/azureprovider/v1alpha1/azureclusterproviderconfig_types.go
Outdated
Show resolved
Hide resolved
pkg/apis/azureprovider/v1alpha1/azureclusterproviderconfig_types.go
Outdated
Show resolved
Hide resolved
@vincepri we should definitely sync on these changes with the AWS provider. |
@detiber @justaugustus @juan-lee @tariq1890 Thanks for helpful comments, I have updated the PR to incorporate all the comments, would appreciate another look at PR |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: awesomenix, justaugustus 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 |
/hold cancel |
…ashes using kubeadm (#136) * Generate certificates using kubeadm instead of manual operations right now, this consolidates efforts into upstream, any bug fixes, updates are consumed * Update cluster-api dependency (#133) Signed-off-by: Stephen Augustus <saugustus@vmware.com> * Bring vendor into sync * Bring vendor into sync * Fix lint issues * Address review comments * Move adminkubeconfig and discoverhashes to cluster status instead of clusterspec
What this PR does / why we need it:
Currently we manually generate certificates and supporting configuration, instead use kubeadm standard tooling for generating all the base configuration required to bootstrap kubernetes nodes
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: