-
Notifications
You must be signed in to change notification settings - Fork 578
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
feat: expose additional eks bootstrap options #2965
feat: expose additional eks bootstrap options #2965
Conversation
@richardcase: This issue is currently awaiting triage. If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the The 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. |
@richardcase do you want this in before v1.1.0 release or is it okay to merge this after we make the release? Feel free to add a milestone when you decide. |
/test ? |
@richardcase: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
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. |
/test pull-cluster-api-provider-aws-e2e-eks |
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.
Non-blocking comments. LGTM.
PauseContainerVersion *string | ||
UseMaxPods *bool | ||
IPFamily *string | ||
ServiceIPV6Cidr *string |
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'd be good to have a note here for both ServiceIPV6Cidr and IPFamily as this is not implemented yet and no-op.
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.
Added a comment
// TODO(richardcase): uncomment when we support ipv6 / dual stack | ||
/*if config.Spec.ServiceIPV6Cidr != nil && *config.Spec.ServiceIPV6Cidr != "" { | ||
nodeInput.ServiceIPV6Cidr = config.Spec.ServiceIPV6Cidr | ||
nodeInput.IPFamily = pointer.String("ipv6") |
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.
For future implementation:
If setting IPFamily
without setting ServiceIPV6Cidr
possible during EKS bootstrap, then I think having IPFamily
as a separate field is needed.
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 is possible to set IPFamily
without setting ServiceIPV6Cidr
but i think we should hide this detail based on whether the user has supplied ipv4 or 6
/test? |
@sedefsavas: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
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. |
/test pull-cluster-api-provider-aws-e2e-eks |
1 similar comment
/test pull-cluster-api-provider-aws-e2e-eks |
) | ||
|
||
// ConvertTo converts the v1alpha4 EKSConfig receiver to a v1beta1 EKSConfig. | ||
func (r *EKSConfig) ConvertTo(dstRaw conversion.Hub) error { | ||
dst := dstRaw.(*v1beta1.EKSConfig) | ||
|
||
return Convert_v1alpha4_EKSConfig_To_v1beta1_EKSConfig(r, dst, nil) | ||
if err := Convert_v1alpha4_EKSConfig_To_v1beta1_EKSConfig(r, dst, nil); err != nil { |
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.
Do we need to do the same for v1alpha3?
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.
We do, added.
Added additional options to `EKSConfig` so that additional configuration options have be set when bootstrapping a node when it joins an eks cluster. Note: the IPv6 services cidr is deliberately not exposed as this will be done when we come to do the IPv6 work. There are some comments left in on purpose for this. Signed-off-by: Richard Case <[email protected]>
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sedefsavas 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 |
…fig_options feat: expose additional eks bootstrap options
What type of PR is this?
/kind feature
/kind api-change
What this PR does / why we need it:
Added additional options to
EKSConfig
so that additional configurationoptions have be set when bootstrapping a node when it joins an eks
cluster.
Note: the IPv6 services cidr is deliberately not exposed as this will be
done when we come to do the IPv6 work. There are some comments left
in on purpose for this.
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 #2853
Special notes for your reviewer:
Checklist:
Release note: