-
Notifications
You must be signed in to change notification settings - Fork 577
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
Add AWSCluster #942
Add AWSCluster #942
Conversation
Signed-off-by: Andy Goldstein <goldsteina@vmware.com>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ncdc 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 |
87d7eb7
to
bc2d7e2
Compare
awsCluster.Status.APIEndpoints = []infrastructurev1alpha2.APIEndpoint{ | ||
{ | ||
Host: awsCluster.Status.Network.APIServerELB.DNSName, | ||
// TODO(ncdc): should this come from awsCluster.Status.Network.APIServerELB.Listeners[0].Port? |
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 we can assume only a single listener, then I do not see why not.
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 our ELB creation code sets up a single listener. Is it possible for a user to BYO ELB?
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 don't think so
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 the code does get-or-create?
Signed-off-by: Andy Goldstein <goldsteina@vmware.com>
bc2d7e2
to
f7ca984
Compare
Signed-off-by: Andy Goldstein <goldsteina@vmware.com>
/test pull-cluster-api-provider-aws-bazel-integration |
Signed-off-by: Andy Goldstein <goldsteina@vmware.com>
Signed-off-by: Andy Goldstein <goldsteina@vmware.com>
Signed-off-by: Andy Goldstein <goldsteina@vmware.com>
adae994
to
fe5c581
Compare
@ncdc planning to update with the changes from kubernetes-sigs/cluster-api#1217? |
@detiber next on my list! |
Signed-off-by: Andy Goldstein <goldsteina@vmware.com>
Signed-off-by: Andy Goldstein <goldsteina@vmware.com>
fe5c581
to
242a3ea
Compare
Latest force-push has the same changes from CAPI 1217 |
/lgtm |
What this PR does / why we need it:
Replaces the old cluster actuator with a new AWSCluster CRD and controller.
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 #933
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: