kubernetes: XFS volumes are unsupported on GCE using the Container-Optimized OS

Is this a request for help? Partly

What keywords did you search in Kubernetes issues before filing this one? xfs gce gci cos mount


Is this a BUG REPORT or FEATURE REQUEST?: BUG REPORT

Kubernetes version: 1.6.4

Environment:

  • Cloud provider or hardware configuration: GCE
  • OS (e.g. from /etc/os-release): Container-Optimized OS v57 (Build ID: 9202.64.0)
  • Kernel (e.g. uname -a): Linux
  • Install tools:
  • Others:

What happened: The node failed to mount an XFS PV on GCE using the COS image. With the Container-vm image everything was fine after I installed xfsprogs.

What you expected to happen: The node should mount the xfs volume on COS too.

How to reproduce it: Try to create an XFS persistent volume in gcloud, then mount it into a pod.

Anything else we need to know: I’m not sure that this is the right place to post this issue. If not, please could you point me to the right direction? I know that this is an issue with the COS itself rather than k8s.

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Reactions: 3
  • Comments: 15 (4 by maintainers)

Most upvoted comments

@markpeterfejes @YouriT there are no plans in the near future to support xfs on COS. However, you can now specify ubuntu as a node image type in GKE (beta).

Yup doing the same, DaemonSet with startup script works like a charm. I really don’t like this inability of personalising the underlying node, containers ok but still if something is missing we need to be able to tweak the underlying.

I thought you were looking for confirmation, sorry. I have no clue where to ask that unfortunately. AFAIK their COS source is not open yet. There is still Chromium OS repo but I’m not sure it’s the best place to ask.

I’m running into the same issue. But I filed a ticket on the support when they gently asked us to move out of container-vm. Let’s see.