What happened:
Worker nodes with data disks cannot join the cluster on GCP with Gardenlinux.
What you expected to happen:
The worker to join the cluster successfully.
How to reproduce it (as minimally and precisely as possible):
Create a GCP shoot with Gardenlinux 318.8 and the following disk configuration (shoot.yaml):
Anything else we need to know?:
The issue is caused by the fact that the GCP extensions creates a MachineClass which configures the data disk from the same image as the boot disk:
How to categorize this issue?
/area os /kind bug /priority 3 /platform gcp
What happened: Worker nodes with data disks cannot join the cluster on GCP with Gardenlinux.
What you expected to happen: The worker to join the cluster successfully.
How to reproduce it (as minimally and precisely as possible): Create a GCP shoot with Gardenlinux
318.8
and the following disk configuration (shoot.yaml):Anything else we need to know?: The issue is caused by the fact that the GCP extensions creates a
MachineClass
which configures the data disk from the same image as the boot disk:As a result, the system runs into two independent problems:
mkfs.ext4 -F
):LABEL
s only and creating another disk form the very same image causes theLABEL
s to be duplicated:As a consequence, the data device is sporadically used as a boot device.
Environment:
v1.30.1
v1.19.0-dev
318.8