search

k3s-io / k3s

Lightweight Kubernetes
https://k3s.io
Apache License 2.0
27.6k stars 2.31k forks source link

Formally add support for CentOS 7 #1371

Closed davidnuzik closed 4 years ago

davidnuzik commented 4 years ago

We need to expand our testing and identify any issues that prevent us from formally supporting CentOS. Keep in mind K3s is expected to work fine on CentOS 7. This issue is to track the testing effort required to formally support and certify the operating system (See https://rancher.com/docs/k3s/latest/en/installation/node-requirements/#operating-systems )

Currently there are existing issues with the os/centos label, but take care to note that these issues are not all necessarily caused just by utilizing CentOS. As such, it makes sense to review those GitHub issues, but we need to execute some testing and identify any other issues. As needed, we'll need to resolve these issues so we may fully support CentOS.

SELinux support is also needed, which is tracked separately here: https://github.com/rancher/k3s/issues/1372

gz#9311

gz#9743

WillPlatnick commented 4 years ago

Is there anything blocking calling CentOS officially supported now?

akhfa commented 4 years ago

Is there anything blocking calling CentOS officially supported now?

I'm also waiting for this. Can we add Centos to the operating system requirements in the docs?

bluebrown commented 3 years ago

I am getting this on centos8

image

I haven't found a way to use legacy IP tables on CentOS yet. I think it may not be possible. I could still run the dashboard though.

noelmcloughlin commented 3 years ago

On saltstack-formulas we run CI/CD that includes installing K3S on various OS (https://travis-ci.com/github/saltstack-formulas/kubernetes-formula) using binary (https://github.com/rancher/k3s/releases).

                 ID: kubernetes-k3s-binary-prerequisites
           Function: file.directory
               Name: /usr/local/k8s-k3s-1.18.4+k3s1/bin
             Result: True
            Comment: Directory /usr/local/k8s-k3s-1.18.4+k3s1/bin updated
            Started: 22:41:32.870731
           Duration: 3.539 ms
            Changes:   
              ----------
              /usr/local/k8s-k3s-1.18.4+k3s1/bin:
                  New Dir
       ----------
                 ID: kubernetes-k3s-binary-install
           Function: file.managed
               Name: /usr/local/k8s-k3s-1.18.4+k3s1/bin/k3s
             Result: True
            Comment: File /usr/local/k8s-k3s-1.18.4+k3s1/bin/k3s updated
            Started: 22:41:32.876005
           Duration: 1625.91 ms
            Changes:   
              ----------
              diff:
                  New file
              mode:
                  0755
       ----------
                 ID: kubernetes-k3s-binary-install-symlink
           Function: file.symlink
               Name: /usr/local/bin/k3s
             Result: True
            Comment: Created new symlink /usr/local/bin/k3s -> /usr/local/k8s-k3s-1.18.4+k3s1/bin/k3s
            Started: 22:41:34.504775
           Duration: 70.67 ms
            Changes:   
              ----------
              new:
                  /usr/local/bin/k3s

I would like to add job to run the K3S script (https://get.k3s.io) on CentOS7 and CentOS8 but the hash sum is missing.

K3S should provide a hash sum (i.e. https://get.k3sum.io) so downloaded script can be verified.

That would be a nice improvement.

brandond commented 3 years ago

@noelmcloughlin can you create a new feature request issue for that? I don't think it's related to this issue.

kylos101 commented 3 years ago

For posterity, with CentOS7.8, I found I had to make a slight change to update kernel (notice the second sudo for the --update-kernel argument:

sudo grubby --args="user_namespace.enable=1" --update-kernel="$(sudo grubby --default-kernel)"
PRNDA commented 3 years ago

For posterity, with CentOS7.8, I found I had to make a slight change to update kernel (notice the second sudo for the --update-kernel argument:

sudo grubby --args="user_namespace.enable=1" --update-kernel="$(sudo grubby --default-kernel)"

what's it for? and why this?

kylos101 commented 3 years ago

@PRNDA

To enable user namespaces in centos/7. The k3s check-config was failing with ootb with centos/7