Support for Fedora 39

[tu1h]

Fedora 39 released at November 7, that would be nice if we can install production-ready Kubernetes on it immediately.

[tu1h]

/kind feature

[tu1h]

https://github.com/ansible/ansible/blob/v2.14.11/lib/ansible/module_utils/urls.py#L604

Fedora 39 use Python 3.12.x, but the deprecated parametes like cert_files in http client library have been removed. So it is necessary to upgrade ansible core to 2.16.x

[trensetim]

Since I am currently doing exactly this, I found that the ansible upgrade might be already done by https://github.com/kubernetes-sigs/kubespray/commit/7ba85710ad8d1f23e28d56cc7a128c5de05224f3

However, I also found some other quirks which may or may not need addressing (maybe they are just related to me...)

• Fedora uses tmpfs for /tmp . Since roles/download uses /tmp by default as the target directory for downloads, it effectively pollutes the RAM. Possibly we should better use /var/tmp here, as this is persistent
• Fedora uses [email protected]. According to the fedora docs zram-generator-defaults should be uninstalled when deploying a kubernetes cluster. However in my test it was not uninstalled, which lead to systemd reporting

  [systemd]
  Failed Units: 1
    [email protected]
  

  upon ssh login to a target maschine

[VannTen]

/remove-kind support (since this is a feature)

[k8s-triage-robot]

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

[k8s-triage-robot]

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