-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Cleanup of preinstall assertions #11901
Cleanup of preinstall assertions #11901
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: VannTen 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 |
/label tide/merge-method-merge |
# Minimal memory requirement in MB for safety checks | ||
minimal_node_memory_mb: 1024 | ||
minimal_master_memory_mb: 1500 | ||
|
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.
Hi @VannTen
Why is the minimal check of memory removed.
Is it because kubeadm already has a check?
Ref to https://github.com/kubernetes/kubernetes/blob/master/cmd/kubeadm/app/constants/constants.go#L396
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.
Yes, that's exactly the point, as well as the kernel version check. Since kubeadm is already doing validation, (which we're not ignoring anymore 😆 ), let's not maintain our own.
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.
Isn't better to fail early than mid-way through the kubeadm install ?
I would prefer to fail at this stage rather than to 10 min later
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.
Good point. I'd still like to defer to kubeadm, but I think we need a better story on download first, to have kubeadm available sufficiently early than we can use it for validation (assuming that we can run the preflight independantly, but I think that's possible).
I'll remove that commit for now.
@@ -160,13 +132,6 @@ | |||
- dashboard_enabled | |||
- not ignore_assert_errors | |||
|
|||
- name: Stop if kernel version is too low |
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?
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.
Same that the mem requirements, this is checked by kubeadm. I'll drop this as well per above.
@@ -193,13 +158,6 @@ | |||
- cloud-provider | |||
- facts | |||
|
|||
- name: "Check that kube_service_addresses is a network range" |
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 to remove this check ?
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.
That's a leftover from a removed commit, messed up my rebase. I'll clean this up.
7520fb4
to
cd60262
Compare
When the etcd group is not specified we assume it's kube_control_plane. In that case, etcd still can't be even, so instead of only checking the etcd group we need to default to kube_control_plane
Since 'none' can be, for instance, a manual calico deployment, don't check whether there is enough ip for pods on a node, because the plugin can use another mechanism than the podCIDR to allocate IPs.
This has been deprecated for a long time, time to pull the plug. We leave an assert for one release to have a straightforward failure if some users were still using the variable.
This assert is present since 2021, we can assume now users have removed it from their inventories.
This assertion is present since 2022, users inventories' should be clean from it now.
cd60262
to
67a7376
Compare
Thanks @VannTen |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
etcd_kubeadm_enabled
(which was deprecated) and assert it's not defined for one releaseWhich issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?: