Skip to content
This repository was archived by the owner on Aug 12, 2025. It is now read-only.
This repository was archived by the owner on Aug 12, 2025. It is now read-only.

Figure out where we stand about operating systems #118

@gianarb

Description

@gianarb

Currently, the cluster-template.yaml is tight to Ubuntu (maybe Debian as well)
because we use the BootstrapTemplate to install packages like: kubeadm,
docker, kubectl and so on:

kind: KubeadmConfig
apiVersion: bootstrap.cluster.x-k8s.io/v1alpha3
metadata:
  name: "${CLUSTER_NAME}-control-plane1-config"
spec:
  preKubeadmCommands:
    - swapoff -a
    - apt-get -y update
    - DEBIAN_FRONTEND=noninteractive apt-get install -y apt-transport-https curl
    - curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key add -
    - echo "deb https://apt.kubernetes.io/ kubernetes-xenial main" > /etc/apt/sources.list.d/kubernetes.list
    - curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
    - apt-key fingerprint 0EBFCD88
    - add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
    - apt-get update -y
    - apt-get install -y ca-certificates socat jq ebtables apt-transport-https cloud-utils prips docker-ce docker-ce-cli containerd.io kubelet kubeadm kubectl
    - systemctl daemon-reload
    - systemctl enable docker
    - systemctl start docker

As you can see this does not work for every operating system.

I am not 100% sure about how the other cluster-api-providers manage this, I
remember AWS, DigitalOcean generating their own images.

I think we should not put the effort of supporting multiple operating systems,
but we have to be clear about it.

In general the template can be modified in a lot of ways from the end user to
make the installation process to work for CentOS or ArchLinux, it is just matter
of changing the packege manager.

In any case I like the idea to maintain a list of images that people can grab
from Packet and use with the ClusterAPI mainly because it will decrease the
amount of runtime actions that can fail along the way.

So, this issue is to understand what you think about it.

First step should be to at least write a documentation about where we are to
avoid the pain for a user to discover that CentOS does not work when trying the
cluster-api.

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions