-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Fix certificate bootstrap for non-kops-controller-bootstrap cloud providers #12019
Fix certificate bootstrap for non-kops-controller-bootstrap cloud providers #12019
Conversation
/test pull-kops-e2e-kubernetes-do-kubetest2 |
c41aca3
to
302a5c4
Compare
/test pull-kops-e2e-kubernetes-do-kubetest2 |
302a5c4
to
ce15a66
Compare
/test pull-kops-e2e-kubernetes-do-kubetest2 |
ce15a66
to
eabdca0
Compare
eabdca0
to
1f70561
Compare
/test pull-kops-e2e-kubernetes-do-kubetest2 |
/area provider/digitalocean |
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.
This code is getting a bit convoluted ... and the cyclomatic complexity makes it a bit hard to reason about.
In particular, I think we need to have a think about apply_cluster.go
soon.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: olemarkus 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 |
/retest |
There are the various model builders which have to decide whether or not to create tasks. There is Then there is Finally, there are the nodeup tasks which consume the data from the I've tried to push NodeupConfig data that doesn't come from dependent tasks down into But yes, I think you've correctly identified |
No description provided.