-
Notifications
You must be signed in to change notification settings - Fork 4.7k
WIP: Support cluster-api for non-master instancegroups, on GCE #8151
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
Conversation
1641714
to
4538868
Compare
Will be building this up here and then splitting out smaller pieces (e.g. #8180). This PR will show the "big picture" and hopefully there will be manageable pieces that make sense individually! |
c8379eb
to
97659b2
Compare
Makefile
Outdated
@@ -168,6 +168,7 @@ kops: ${KOPS} | |||
${KOPS}: ${BINDATA_TARGETS} | |||
go build ${GCFLAGS} ${EXTRA_BUILDFLAGS} ${LDFLAGS}"-X k8s.io/kops.Version=${VERSION} -X k8s.io/kops.GitVersion=${GITSHA} ${EXTRA_LDFLAGS}" -o $@ k8s.io/kops/cmd/kops/ | |||
|
|||
.PHONY: ${GOBINDATA} |
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.
Why? This task actually creates/updates the file that ${GOBINDATA}
expands to, so it's not phony.
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.
You're right - fixed!
It's currently not possible to turn off MachineDeployment's rolling updates. I filed kubernetes-sigs/cluster-api#1754 but that appears to have been kicked into the long grass. Kops rolling updates are soon to be much more sophisticated than MachineDeployment's. You might want to use MachineSets instead of MachineDeployments. |
"bootstrap": map[string]interface{}{ | ||
"dataSecretName": dataSecretName, | ||
}, | ||
"infrastructureRef": map[string]interface{}{ |
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.
I assume you're using these maps to avoid the dependency of Cluster API repo, right?
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.
Right - it's actually not so much a circular dependency as it is that cluster-api has its own dependencies on controller-runtime & client-go etc and I was hitting conflicts.
97659b2
to
9e82b69
Compare
We want to start re-using it for cluster-api support.
This is the first step to supporting cluster-api; starting with GCE for now. Slight problem at the moment: kubernetes/kubernetes#86509
9e82b69
to
7713746
Compare
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@justinsb: PR needs rebase. 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. |
|
||
var resource string | ||
|
||
switch gvk.Group + ":" + gvk.Kind { |
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.
Is there any way we can put this logic into something generic? To me it seems that this switch will expand pretty fast once we have more providers implementing this logic. And then we have two places worrying about which cloud uses which resources, which is quite unfortunate.
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.
It looks like this is essentially a map lookup.
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closed this PR. In response to this:
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. |
Going to reopen, but leave as WIP, as I track merging this functionality. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@justinsb: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
/milestone v1.22 |
Rotten issues close after 30d of inactivity. Send feedback to sig-contributor-experience at kubernetes/community. |
@fejta-bot: Closed this PR. In response to this:
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. |
No description provided.