param --enable-worker not working

[ondrej-m]

Before creating an issue, make sure you've checked the following:

• You are running the latest released version of k0s
• Make sure you've searched for existing issues, both open and closed
• Make sure you've searched for PRs too, a fix might've been merged already
• You're looking at docs for the released version, "main" branch docs are usually ahead of released versions.

Platform

Debian 12.5, docker image
Docker ce 26.0.0

Version

k0sproject/k0s:v1.29.3-k0s.0

Sysinfo

`k0s sysinfo`

Machine ID: "90abf23a7d335a1763ee8504fe9811be9517a882bd6eb8c38dad79fa3e2dceec" (from machine) (pass)
Total memory: 3.8 GiB (pass)
Disk space available for /var/lib/k0s: 1.2 GiB (warning: 1.8 GiB recommended)
Name resolution: localhost: [::1 127.0.0.1] (pass)
Operating system: Linux (pass)
  Linux kernel release: 6.1.0-18-amd64 (pass)
  Max. file descriptors per process: current: 524288 / max: 524288 (pass)
  AppArmor: unavailable (pass)
  Executable in PATH: modprobe: /sbin/modprobe (pass)
  Executable in PATH: mount: /bin/mount (pass)
  Executable in PATH: umount: /bin/umount (pass)
  /proc file system: mounted (0x9fa0) (pass)
  Control Groups: version 2 (pass)
    cgroup controller "cpu": available (is a listed root controller) (pass)
    cgroup controller "cpuacct": available (via cpu in version 2) (pass)
    cgroup controller "cpuset": available (is a listed root controller) (pass)
    cgroup controller "memory": available (is a listed root controller) (pass)
    cgroup controller "devices": available (device filters attachable) (pass)
    cgroup controller "freezer": available (cgroup.freeze exists) (pass)
    cgroup controller "pids": available (is a listed root controller) (pass)
    cgroup controller "hugetlb": available (is a listed root controller) (pass)
    cgroup controller "blkio": available (via io in version 2) (pass)
  CONFIG_CGROUPS: Control Group support: no kernel config found (warning)
  CONFIG_NAMESPACES: Namespaces support: no kernel config found (warning)
  CONFIG_NET: Networking support: no kernel config found (warning)
  CONFIG_EXT4_FS: The Extended 4 (ext4) filesystem: no kernel config found (warning)
  CONFIG_PROC_FS: /proc file system support: no kernel config found (warning)

What happened?

No response

Steps to reproduce

1. docker run -d --name k0s --hostname k0s --privileged -v /var/lib/k0s -p 6443:6443 --cgroupns=host docker.io/k0sproject/k0s:v1.29.3-k0s.0 -- k0s controller --enable-worker
2. docker exec -it k0s k0s status
   Version: v1.29.3+k0s.0
   Process ID: 8
   Role: controller
   Workloads: true
   SingleNode: false
   Kube-api probing successful: true
   Kube-api probing last error:
3. $ docker exec -it k0s k0s kubectl get nodes --show-labels
   NAME STATUS ROLES AGE VERSION LABELS
   k0s Ready control-plane 4m42s v1.29.3+k0s beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/arch=amd64,kubernetes.io/hostname=k0s,kubernetes.io/os=linux,node-role.kubernetes.io/control-plane=true,node.k0sproject.io/role=control-plane

Expected behavior

2. docker exec -it k0s k0s status
   Version: v1.29.3+k0s.0
   Process ID: 8
   Role: controller +worker
   Workloads: true
   SingleNode: false
   Kube-api probing successful: true
   Kube-api probing last error:

Actual behavior

No response

Screenshots and logs

No response

Additional context

No response

[twz123]

You mean Role: controller? That's expected, as this is a controller node. The difference that --enable-worker makes that it also starts the worker components (mainly kubelet and containerd). You can see that as Workloads: true.

If you want to run a worker-only node (that needs to join an existing cluster using a join token), have a look at the worker subcommand.

[hztsm]

I also encountered the same problem. I asked to install a host, which is both a management node and a worker node。
Execute the following installation command:

k0s install controller --single --enable-worker --enable worker

When I run the application, the pod is always pending.

[twz123]

@hztsm This seems like a separate problem. Would you mind to file another issue and provide logs?