kubespray
kubespray copied to clipboard
can support alibaba linux
Alibaba's operating system is still very common in China, whether it can support the opening of Alibaba's operating system, the Dragon Lizard Alibab operating system is derived from the Dragon Lizard
It can be support by
allow_unsupported_distribution_setup: true
redhat_os_family_extensions:
- "Anolis OS"
where set this ?which file thank you !
i find this,thank you~ i will try.
@long1318737396 Hello, do you have any update for this issue? Can we close this issue? or do you want to add the linux as supported one into Kubespray?
i have no any other question, thank you very much~
[root@node1 yum.repos.d]# cat /etc/os-release NAME="Anolis OS" VERSION="7.9" ID="anolis" ID_LIKE="rhel fedora centos" VERSION_ID="7.9" PRETTY_NAME="Anolis OS 7.9" ANSI_COLOR="0;31" HOME_URL="https://openanolis.cn/" BUG_REPORT_URL="https://bugs.openanolis.cn/"
CENTOS_MANTISBT_PROJECT="CentOS-7" CENTOS_MANTISBT_PROJECT_VERSION="7" REDHAT_SUPPORT_PRODUCT="centos" REDHAT_SUPPORT_PRODUCT_VERSION="7"
allow_unsupported_distribution_setup: true redhat_os_family_extensions: - "Anolis OS"
After adding redhat_os extension. It was mentioned during installation that some packages did not exist. Anolis OS 7.9 is a successor to Centos 7.9. There are some differences between it and Redhat.
The non-existent package is python3-libselinux
/remove-kind support /kind feature
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/stale
is applied - After 30d of inactivity since
lifecycle/stale
was applied,lifecycle/rotten
is applied - After 30d of inactivity since
lifecycle/rotten
was applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale
- Close this issue with
/close
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/stale
is applied - After 30d of inactivity since
lifecycle/stale
was applied,lifecycle/rotten
is applied - After 30d of inactivity since
lifecycle/rotten
was applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle rotten
- Close this issue with
/close
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten