Installation of 1.30/stable on debian-12-genericcloud-amd64.qcow2 fails about microk8s HOT 12 OPEN

Hi @Aaron-Ritter see #4361 (comment).

We are in the process of promoting the fix. It should already be out in 1.29/stable, and 1.30/stable is expected to follow before the end of this week. Thank you for testing!

from microk8s.

Hi @Aaron-Ritter, could this be the same issue as #4361?

from microk8s.

@neoaggelos likely, cant deploy 1.29/stable either

from microk8s.

This does the trick for 1.30/stable too:

#4361 (comment)

echo '
--cgroups-per-qos=false
--enforce-node-allocatable=""
' | sudo tee -a /var/snap/microk8s/current/args/kubelet

sudo snap restart microk8s.daemon-kubelite

But 1. i don't think its something we should disable and 2. https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/ (DEPRECATED: This parameter should be set via the config file specified by the kubelet's --config flag. See kubelet-config-file for more information.)

from microk8s.

Can you try installing from 1.30/edge? We have a fix that should solve the related cgroups issues #4503 but it's not yet found its way to 1.30/stable.

Should be something like

sudo snap install microk8s --classic --channel 1.30/edge

from microk8s.

yep! this works, the node is online.

Whats the downside of this fix with delegate.conf?

And is it already clear by when it is expected to be in stable?

from microk8s.

Apparently, this is some sort of regression in Kubernetes, see kubernetes/kubernetes#122955. kubelet is responsible for ensuring cgroups have all required controllers, but apparently that does not work as expected.

from microk8s.

Hm ok, so does that mean that the workaround will potentially bite itself once the underlying kubelet issue is solved?

I will try the test cluster setup with 1.30/edge for now and deploy all other components i usually use and see if there are any other problems with it.

from microk8s.

@neoaggelos are you able to comment on the possible release ETA for the working edge version?

from microk8s.

@neoaggelos Is there a way to track the releases of patch versions? Meaning the details of the different patch versions like list of features / fixes / issues solved by the patched version?

from microk8s.

@Aaron-Ritter I am leaning towards checking the commit merge date into main, and comparing that to last channel update in snap info microk8s

snap-id:      EaXqgt1lyCaxKaQCU349mlodBkDCXRcg
tracking:     1.29/stable
refresh-date: 5 days ago, at 15:29 WIB
channels:
  1.29/stable:           v1.29.4  2024-05-07 (6809) 170MB classic
  1.29/candidate:        v1.29.4  2024-05-03 (6809) 170MB classic
  1.29/beta:             v1.29.4  2024-05-03 (6809) 170MB classic
  1.29/edge:             v1.29.5  2024-05-15 (6837) 170MB classic
  latest/stable:         v1.29.0  2024-01-25 (6364) 168MB classic
  latest/candidate:      v1.30.1  2024-05-17 (6844) 168MB classic
  latest/beta:           v1.30.1  2024-05-17 (6844) 168MB classic
  latest/edge:           v1.30.1  2024-05-15 (6844) 168MB classic
  1.30-strict/stable:    v1.30.0  2024-04-18 (6783) 168MB -
  1.30-strict/candidate: v1.30.0  2024-04-18 (6783) 168MB -
  1.30-strict/beta:      v1.30.0  2024-04-18 (6783) 168MB -
  1.30-strict/edge:      v1.30.1  2024-05-15 (6843) 168MB -
  1.30/stable:           v1.30.0  2024-04-18 (6782) 168MB classic
  1.30/candidate:        v1.30.0  2024-05-10 (6813) 168MB classic
  1.30/beta:             v1.30.0  2024-05-10 (6813) 168MB classic
  1.30/edge:             v1.30.1  2024-05-15 (6842) 168MB classic

The PR merged on 2024-04-19, so I suppose 1.29/stable has the update, because its updated on may, but 1.30/stable still doesn't have it because its last updated on 2024-04-18, the candidate/beta version has it tho

from microk8s.