mirror of
https://pagure.io/fedora-docs/quick-docs.git
synced 2024-10-18 09:21:50 +00:00
Compare commits
14 commits
aa8f2ccb04
...
1111bc3f02
| Author | SHA1 | Date | |
|---|---|---|---|
|
1111bc3f02 | ||
|
33be22abff | ||
|
ee8c798dc3 | ||
|
|
228c63b9c6 | ||
|
|
c5d6c00a41 | ||
|
|
0e2518f5ef | ||
| c74c063315 | |||
| 3ca5cb2ce3 | |||
| 66b7663e94 | |||
|
3bd1a11630 | ||
|
0b81f99792 | ||
|
|
26d2c3748f | ||
|
b61cac8ece | ||
|
|
8780d722a3 |
14 changed files with 975 additions and 516 deletions
|
|
@ -2,11 +2,12 @@
|
|||
|
||||
This is the content repository for the Fedora Quick Docs.
|
||||
|
||||
Quick docs is a collection of short HOW-TO, tutorials and FAQ-style documentation for Fedora users on the official Fedora documentation site that cover commonly used workflows/tools.
|
||||
|
||||
Please report Issues and submit Pull Requests for **Content Fixes** here.
|
||||
Never done a pull request (or "PR")? Here's the [Pagure documentation for
|
||||
Pull Requests](https://docs.pagure.org/pagure/usage/pull_requests.html).
|
||||
|
||||
|
||||
General appearance issues and publishing issues should be reported against
|
||||
the [Fedora Docs Website](https://gitlab.com/fedora/docs/docs-website/docs-fp-o).
|
||||
|
||||
|
|
|
|||
|
|
@ -78,6 +78,12 @@
|
|||
** xref:understanding-and-administering-systemd.adoc[Understanding and administering systemd]
|
||||
** xref:gnome-shell-extensions.adoc[Using GNOME Shell extensions]
|
||||
** xref:using-kubernetes.adoc[Using Kubernetes on Fedora]
|
||||
*** xref:using-kubernetes-basics.adoc[Kubernetes Basics]
|
||||
*** xref:using-kubernetes-non-versioned.adoc[Nonversioned Kubernetes rpms (F39, F40)]
|
||||
*** xref:using-kubernetes-versioned.adoc[Versioned Kubernetes rpms (F41 and newer)]
|
||||
*** xref:using-kubernetes-kubelet.adoc[Configuring kubelet]
|
||||
*** xref:using-kubernetes-kubeadm.adoc[Creating a Kubernetes cluster]
|
||||
*** xref:using-kubernetes-cri-o.adoc[CRI-O and CRI-Tools]
|
||||
** xref:using-shared-system-certificates.adoc[Using shared system certificates]
|
||||
** xref:using-yubikeys.adoc[Using Yubikeys with Fedora]
|
||||
** xref:viewing-logs.adoc[Viewing logs in Fedora]
|
||||
|
|
@ -125,10 +131,11 @@
|
|||
** xref:cups-filing-a-bug-report.adoc[Filing a CUPS Bug Report]
|
||||
|
||||
* Troubleshooting
|
||||
** xref:troubleshooting-bluetooth-problems.adoc[Troubleshooting Bluetooth problems]
|
||||
** xref:troubleshooting-java-programs.adoc[Troubleshooting Java Programs]
|
||||
** xref:troubleshooting-mozilla-products.adoc[Troubleshooting Mozilla Products]
|
||||
** xref:troubleshooting-wayland-problems.adoc[Troubleshooting Wayland Problems]
|
||||
** xref:troubleshooting-bluetooth-problems.adoc[Troubleshooting Bluetooth problems]
|
||||
** xref:troubleshooting-java-programs.adoc[Troubleshooting Java Programs]
|
||||
** xref:troubleshooting-mozilla-products.adoc[Troubleshooting Mozilla Products]
|
||||
** xref:troubleshooting-wayland-problems.adoc[Troubleshooting Wayland Problems]
|
||||
** xref:how-to-troubleshoot-sound-problems.adoc[Troubleshooting Sound Problems]
|
||||
|
||||
* FAQ
|
||||
** xref:fedora-and-red-hat-enterprise-linux.adoc[Fedora and Red Hat Enterprise Linux]
|
||||
|
|
|
|||
142
modules/ROOT/pages/how-to-troubleshoot-sound-problems.adoc
Normal file
142
modules/ROOT/pages/how-to-troubleshoot-sound-problems.adoc
Normal file
|
|
@ -0,0 +1,142 @@
|
|||
= How to troubleshoot sound problems
|
||||
Hank Lee ; The Music and Audio SIG
|
||||
:revnumber: F40
|
||||
:revdate: 2024-07-29
|
||||
:category: Administration
|
||||
:tags: Troubleshooting, Sound, Multimedia
|
||||
|
||||
[abstract]
|
||||
This page covers some basic troubleshooting techniques to help narrow down the root cause of an issue. It also explains information that should be included when filing bugs related to sound. General sound problems - where the problem is observed across multiple applications - should usually be filed against the kernel, or PipeWire (see below for instructions on determining whether the problem is PipeWire-related). If the problem is observed only in a specific application, or only in applications which use a single multimedia library (such as SDL or OpenAL), the bug should be filed against that component.
|
||||
|
||||
== Check which Kernel driver is in use by PCI devices
|
||||
|
||||
To display kernel drivers handling each device, use the lspci (List PCI) command with the option -k. Searching for known issues specific to driver’s name and your hardware model before reporting issues to Ask Fedora.
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
$ sudo lspci -k
|
||||
----
|
||||
|
||||
New hardware drivers are updated continuously. If you see a device listed as unknown, query your PCI device ID database.
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
$ sudo lspci -Q
|
||||
----
|
||||
|
||||
And update your local PCI ID database by running the command update-pciids.
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
$ sudo update-pciids
|
||||
----
|
||||
|
||||
== ALSA Firmware
|
||||
|
||||
The ALSA Firmware package contains firmware for various third-party sound cards.
|
||||
|
||||
See which firmware is in use by running the following command.
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
$ sudo dnf list alsa-firmware
|
||||
----
|
||||
|
||||
The regular ALSA Firmware will appear <alsa-firmware.noarch>.
|
||||
|
||||
If the regular firmware is not on the output, install the alsa-firmware.
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
$ sudo dnf install alsa-firmware
|
||||
----
|
||||
|
||||
If any other firmware is installed, put them on blocklist on configuration directory for modprobe.
|
||||
|
||||
----
|
||||
/etc/modprobe.d/*.conf
|
||||
----
|
||||
|
||||
Add the line on configuration file.
|
||||
|
||||
----
|
||||
blacklist <the module to blocklist>
|
||||
----
|
||||
|
||||
The dracut tool creates an initial image used by the kernel for preloading the block device modules. The option -f overwrite existing initramfs file.
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
$ sudo dracut -f
|
||||
----
|
||||
|
||||
Reboot your computer for the change to take effect.
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
$ sudo reboot
|
||||
----
|
||||
|
||||
== Hardware information
|
||||
|
||||
It is always useful to include detailed information on your sound hardware when filing a sound-related bug. To produce this information, run this command:
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
$ alsa-info.sh --no-upload
|
||||
----
|
||||
|
||||
It will generate a file containing detailed information about your sound hardware with the name /tmp/alsa-info.txt. Attach this file to your bug report.
|
||||
|
||||
== Is it PipeWire?
|
||||
|
||||
PipeWire is a media sharing server, low-level multimedia framework that aims to;
|
||||
|
||||
* improve handling of audio and video under Linux
|
||||
|
||||
* work for all users at all levels
|
||||
|
||||
* offer support for PulseAudio, JACK (JACK Audio Connection Kit), ALSA and GStreamer-based applications
|
||||
|
||||
=== Visual checks on ports
|
||||
|
||||
Qpwgraph is a graph manager dedicated to PipeWire.
|
||||
|
||||
Visual checks on ports using Qpwgraph will help discover all the routing between applications and devices and change the routing as you need. For example, if multiple applications and devices are connected and disconnected like below,
|
||||
|
||||
* Firefox: video conference application using WebRTC protocol
|
||||
|
||||
* VLC: media playback
|
||||
|
||||
* OBS Studio: live stream and recording
|
||||
|
||||
* USB soundcards or mixers: devices
|
||||
|
||||
it will be useful to learn how ports are connected to applications and devices graphically.
|
||||
|
||||
Ports are directional, they can be either:
|
||||
|
||||
* Source ports (output). Located at the right-most edge of a node, they generate an audio/video/midi stream.
|
||||
|
||||
* Sink ports (input). Located at the left-most edge of a node, they consume an audio/video/midi stream.
|
||||
|
||||
Ports also have different types:
|
||||
|
||||
* Audio (default color: green)
|
||||
|
||||
* Video (default color: blue)
|
||||
|
||||
* PipeWire/JACK MIDI (default color: red)
|
||||
|
||||
* ALSA MIDI (default color: purple)
|
||||
|
||||
Ports of the same type and opposite directions can be connected.
|
||||
|
||||
Check the upstream documentation for user guide link:https://gitlab.freedesktop.org/rncbc/qpwgraph/-/blob/main/docs/qpwgraph-user_manual.md[Qpwgraph User Guide].
|
||||
|
||||
=== PipeWire debugging options
|
||||
|
||||
Debugging usually starts after the bug has been identified, and works best when users are very familiar with the circumstances surrounding the bug.
|
||||
|
||||
PipeWire has its own debugging options. Please see the upstream documentation link:https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Troubleshooting#pipewire-debugging-options[PipeWire debugging].
|
||||
|
||||
|
|
@ -51,7 +51,7 @@ via their communication channels: https://www.mysql.com/about/faq/
|
|||
sudo dnf install mysql-community-server
|
||||
----
|
||||
|
||||
=== Start MySQL Service and Enable at Loggin:
|
||||
=== Start MySQL Service and Enable at login:
|
||||
|
||||
----
|
||||
sudo systemctl start mysqld
|
||||
|
|
@ -107,41 +107,6 @@ sudo systemctl enable {mysqld|mariadb}
|
|||
sudo systemctl start {mysqld|mariadb}
|
||||
----
|
||||
|
||||
=== Installing MariaDB server from the Fedora Modular repository
|
||||
|
||||
To list the available versions (_streams_ in modularity terminology) of MariaDB:
|
||||
|
||||
----
|
||||
dnf module list mariadb
|
||||
----
|
||||
|
||||
To enable the version of MariaDB you want to use and make the stream RPMs available in the package set:
|
||||
|
||||
----
|
||||
sudo dnf module enable mariadb:10.4
|
||||
----
|
||||
|
||||
At this point you can verify that the available RPM provides the 10.4 verison of MariaDB server:
|
||||
|
||||
----
|
||||
dnf list mariadb-server
|
||||
----
|
||||
|
||||
To install MariaDB server:
|
||||
|
||||
----
|
||||
sudo dnf module install mariadb/server
|
||||
----
|
||||
|
||||
With modules, you could also install a specific profile: like client, devel or galera (the multi-master replica).
|
||||
For instance, if you don't want to install the server stuff, but only the client packages:
|
||||
|
||||
----
|
||||
sudo dnf module install mariadb:10.4/client
|
||||
----
|
||||
|
||||
* MariaDB default root password is empty.
|
||||
|
||||
=== Configuring SQL before the first use
|
||||
|
||||
----
|
||||
|
|
|
|||
|
|
@ -59,7 +59,7 @@ or you can run the following command:
|
|||
== Applying The Patch
|
||||
|
||||
To apply the patch, take the .patch file you've been requested to apply,
|
||||
and save it in the "kerenl" directory the previous step created as:
|
||||
and save it in the "kernel" directory the previous step created as:
|
||||
|
||||
linux-kernel-test.patch
|
||||
|
||||
|
|
|
|||
|
|
@ -13,19 +13,18 @@ include::{partialsdir}/3rdparty-message.adoc[]
|
|||
|
||||
|
||||
== Introduction
|
||||
The objective is to enable NVIDIA GPU of an Optimus-based laptop *all the time* and use it for every single activity.
|
||||
Please do not use this guide if you want to render your desktop using the integrated GPU and specifically select applications to be rendered using the NVIDIA GPU.
|
||||
The goal is to have an active NVIDIA GPU on an Optimus-based laptop and use it for all activities on Desktops Environments with Xorg-X11.
|
||||
Avoid using this guide if you prefer to render your desktop with the integrated GPU and selectively choose applications to utilize the NVIDIA GPU.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
The steps listed here have been verified to be working on Fedora 32 Workstation. Please update your installation to include your experiences and any other tweaks that may be needed if you are using any other desktop environments.
|
||||
The instructions in this document have been verified to work on releases of Fedora 32 Workstation and later versions that use Xorg-X11.
|
||||
|
||||
Some guides on the internet recommend a different approach to installing Nvidia drivers on Fedora, such as directly using the binaries provided by Nvidia. However, the Fedora Project cannot guarantee that these will always function with every Fedora release. Therefore, we recommend following the steps outlined in this document instead.
|
||||
|
||||
As of Fedora 34, Wayland has become the default display server on Fedora Workstation for GNOME desktop environments. To follow the steps provided in this guide, you must be logged in to a session that runs on Xorg-X11.
|
||||
|
||||
Some guides on the internet advise a different approach to installing nVidia drivers on Fedora, such as directly using the binaries provided by nVidia. The Fedora Project cannot ensure these will always work on every Fedora release, and we therefore recommend following the steps in this document instead.
|
||||
====
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
As Prime works less satisfactorily with Wayland server, following the steps provided in this guide would default the server to Xorg.
|
||||
====
|
||||
|
||||
[WARNING]
|
||||
|
|
@ -33,24 +32,26 @@ As Prime works less satisfactorily with Wayland server, following the steps prov
|
|||
This guide requires the secure boot to be **turned off** to load up the unsigned NVIDIA kernel modules.
|
||||
====
|
||||
|
||||
In order to make all the rendering default to the NVIDIA GPU, you need the follow the steps very carefully.
|
||||
To make all rendering default to the NVIDIA GPU, you need to follow these steps very carefully.
|
||||
|
||||
First, you need to see if you really want to achieve this.
|
||||
First, consider the following points:
|
||||
|
||||
=== Why would you want to do that?
|
||||
* The use of NVIDIA GPU all the time would allow for smoother transitions and richer animation effects. Premium desktop environments like GNOME would benefit a lot from this.
|
||||
* Enabling the NVIDIA GPU all the time would lead to lower CPU load and memory consumption which otherwise would have been high due to added in-memory video buffer.
|
||||
* Why would you want to do this?
|
||||
|
||||
=== Why would you not want to do that?
|
||||
* With the NVIDIA GPU used all the time, there would be a slight increase in battery consumption which should not be a concern if your device is used while being plugged in.
|
||||
* Increased generation of heat from the all-the-time enabled NVIDIA GPU can be worrisome. You would not want to play AAA-titles on Proton while placing your laptop on your lap.
|
||||
Using the NVIDIA GPU all the time allows for smoother transitions and richer animation effects. Premium desktop environments like GNOME benefit greatly from this.
|
||||
Enabling the NVIDIA GPU all the time leads to lower CPU load and memory consumption, which would otherwise be high due to the added in-memory video buffer.
|
||||
|
||||
* Why might this not be ideal?
|
||||
|
||||
Using the NVIDIA GPU all the time can cause a slight increase in battery consumption. This shouldn't be a concern if your device is plugged in while in use.
|
||||
The increased heat generation from the constantly enabled NVIDIA GPU might be a concern. You wouldn't want to play demanding games (AAA titles) on Proton while using your laptop on your lap.
|
||||
|
||||
== Step #1: Update from the existing repositories
|
||||
Execute
|
||||
----
|
||||
sudo dnf upgrade
|
||||
----
|
||||
once to update all your packages first.
|
||||
Once to update all your packages first.
|
||||
|
||||
image:how-to-set-nvidia-as-primary-gpu-on-optimus-based-laptops-0.png[]
|
||||
|
||||
|
|
@ -93,7 +94,9 @@ This would force the configuration to be read from the updated kernel modules wh
|
|||
== Step #7: Reboot your system
|
||||
Wait for 3-5 minutes for the changes to take effect and then reboot your system.
|
||||
|
||||
Once your system has started, go to the *About* page in the *Settings* application. You are likely to see the following output.
|
||||
Log in to a session with Xorg-X11.
|
||||
|
||||
From the desktop, go to the *About* page in the *Settings* application. You are likely to see the following output.
|
||||
|
||||
image:how-to-set-nvidia-as-primary-gpu-on-optimus-based-laptops-4.png[]
|
||||
|
||||
|
|
|
|||
|
|
@ -255,6 +255,17 @@ echo "Removed old kernels"
|
|||
exit 0
|
||||
----
|
||||
|
||||
[[sect-clean-up-old-keys]]
|
||||
=== Clean-up old keys trusted for RPM package signing
|
||||
|
||||
Keys from older Fedora releases and third-party repositories will accumulate in the RPM database over time. You can remove keys no-longer referenced from `/etc/yum.repos.d/` with:
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
sudo dnf install clean-rpm-gpg-pubkey
|
||||
sudo clean-rpm-gpg-pubkey
|
||||
----
|
||||
|
||||
[[sect-clean-up-old-symlinks]]
|
||||
=== Clean-up old symlinks
|
||||
|
||||
|
|
|
|||
60
modules/ROOT/pages/using-kubernetes-basics.adoc
Normal file
60
modules/ROOT/pages/using-kubernetes-basics.adoc
Normal file
|
|
@ -0,0 +1,60 @@
|
|||
= Kubernetes Basics
|
||||
Bradley G Smith,
|
||||
:revnumber: F37,F38,F39,F40,rawhide
|
||||
:revdate: 2023-12-23
|
||||
:category: Installation
|
||||
:tags: How-to, kubernetes, dnf, rpm, containers
|
||||
:page-aliases: kubernetes/basics
|
||||
|
||||
// Optional free form useful additional information as comment
|
||||
|
||||
//include::{partialsdir}/3rdparty-message.adoc[]
|
||||
include::partial$3rdparty-message.adoc[]
|
||||
|
||||
[[sect-kubernetes-defined]]
|
||||
== Kubernetes Defined
|
||||
|
||||
link:https:/kubernetes.io[Kubernetes] is an "open-source system for automating deployment, scaling, and management of containerized applications" on one or more machines.
|
||||
Kubernetes automates many of the tasks necessary to deploy, manage, and scale applications that are running as a container.
|
||||
This automation is vital when managing applications in data center or cloud environment where there are 100's or 1000's of machines and a corresponding complexity in numbers of applications.Fedora provides several technologies, in addition to Kubernetes, that run containers such as link:https://docker.com[Docker] or link:https://podman.io[Podman].
|
||||
|
||||
Kubernetes had its genesis in the concepts and principles used at Google to run container-base workloads at scale and with resilience.
|
||||
Kubernetes is now at the center of a vast ecosystem of products and services (link:https://cncf.io/[Cloud Native Computing Foundation]) that help organizations create, install, run, manage and secure container-based applications and services at any possible scale.
|
||||
|
||||
There are numerous ways to install and configure Kubernetes depending on purpose and target environment.
|
||||
Is this for a home lab on a single machine, a small cluster for home or business automation, edge-based services and applications in remote offices or enterprise scale production workloads in the cloud?
|
||||
|
||||
There is an enormous amount of Kubernetes information available online and in books. A good place to start is the link:https://kubernetes.io/docs/home/[Kubernetes Documentation] web site. Become familiar with what is available here, then use your favorite search engine to find additional material tailored to your requirements.
|
||||
|
||||
[[sect-versions]]
|
||||
== Versions
|
||||
|
||||
The Kubernetes team uses link:https://semver.org[semantic versioning] for Kubernetes where a given version has 3 primary components separated by periods: _major.minor.patch_. An example is 1.30.1 where the major version is _1_, the minor version is _30_, and the patch level is _1_. *A Kubernetes release is a new minor version such as 1.30 or 1.31.* The versioned rpms in Fedora are, therefore, at the minor version level.
|
||||
|
||||
Using ```dnf update``` on an existing versioned kubernetes rpm will update patch releases only. See the xref:using-kubernetes-versioned.adoc#sect-fedora-40-version-update[update process recommendations] for versioned rpms.
|
||||
|
||||
[[sect-terminology]]
|
||||
== Terminology
|
||||
|
||||
Kubernetes is complex and like many complex systems has its own terminology.
|
||||
The terminology used in this guide are defined here.
|
||||
The Kubernetes teams maintains a comprehensive link:https://kubernetes.io/docs/reference/glossary/[glossary] which is used in the subset below.
|
||||
|
||||
[horizontal]
|
||||
cluster:: a set of one or more nodes managed as an entity.
|
||||
A cluster has at least one node and one control plane (these can be on the same or separate machines).
|
||||
control plane:: the node or nodes in the cluster hosting the management services for the cluster.
|
||||
At least one node in a cluster has a control plane.
|
||||
A control plane machine can also function as a worker node.
|
||||
node:: a worker machine (either a virtual machine or physical machine) in a Kubernetes cluster that has the services required to run pods.
|
||||
These services include the `kubelet` container runtime and `kube-proxy`.
|
||||
pods:: containerized applications are deployed and managed in Kubernetes as pods.
|
||||
A pod is the base object managed by Kubernetes in a cluster.
|
||||
A pod typically has a single primary container but may include more capabilities including multiple containers.
|
||||
|
||||
|
||||
[[sect-additional-information]]
|
||||
== Additional Information
|
||||
|
||||
Kubernetes and the ecosystem of related components found under the link:https://www.cncf.io[Cloud Native Computing Foundation] umbrella is vast as is the plethora of internet accessible information about Kubernetes. Kubernetes and this ecosystem is also evolving rapidly such that online information may be out-dated or incomplete (_likely including information in this Quick Doc -ed_).
|
||||
|
||||
36
modules/ROOT/pages/using-kubernetes-cri-o.adoc
Normal file
36
modules/ROOT/pages/using-kubernetes-cri-o.adoc
Normal file
|
|
@ -0,0 +1,36 @@
|
|||
= Versioned CRI-O and CRI-Tools RPMs
|
||||
Bradley G Smith,
|
||||
:revnumber: F41
|
||||
:revdate: 2024-07-30
|
||||
:category: Installation
|
||||
:tags: How-to, kubernetes, dnf, rpm, containers, cri-o, cri-tools
|
||||
|
||||
// Optional free form useful additional information as comment
|
||||
|
||||
//include::{partialsdir}/3rdparty-message.adoc[]
|
||||
include::partial$3rdparty-message.adoc[]
|
||||
|
||||
[[sect-overview]]
|
||||
== Overview
|
||||
|
||||
link:https://cri-o.io[CRI-O] and link:https://github.com/kubernetes-sigs/cri-tools[CRI-Tools] are independent software packages available in Fedora repositories that are version matched to Kubernetes. If Kubernetes 1.30 is installed, then, when installed, CRI-O and CRI-Tools should also have the same minor version, _i.e_ 1.30.
|
||||
|
||||
[[sect-cri-o]]
|
||||
== CRI-O
|
||||
|
||||
The **C**ontainer **R**untime **I**nterface(link:https://kubernetes.io/docs/concepts/architecture/cri/[CRI]) is the plugin interface used by the ```kubelet``` to communicate with the container runtime on each node that launches pods and their containers. There are several implementations of CRI including link:https://cri-o.io[CRI-O] and link://https://containerd.io/[containerd].
|
||||
|
||||
CRI-O is available in Fedora repositories as versioned rpms in parallel with Kubernetes. If kubernetes1.30 is installed and CRI-O is the designated CRI implementation, then cri-o1.30 needs to be installed.
|
||||
|
||||
=== Configuration
|
||||
|
||||
CRI-O configuration options are set in `/etc/crio/crio.conf`. This file is managed by rpm and therefore replaced when a versioned CRI-O package is replaced by another package (not counting patch level updates) such as when the cri-o1.30 rpm is replaced by the cri-o1.31 rpm. One method to create and manage custom CRI-O conifiguration settings that persist across updates is to take advantage of CRI-O support for a drop-in configuration. The default drop-in subdirectory is `/etc/crio/crio.conf.d/`. Settings in configuration files placed in the drop-in directory take precedence over the same setting in the default configuration file `/etc/crio/crio.conf`. If multiple drop-in configuration files have the same setting, the file that is sorted last in lexical order will have precedence. See link:https://github.com/cri-o/cri-o/blob/main/docs/crio.conf.d.5.md[crio.conf.d] man file for additional information.
|
||||
|
||||
See xref:using-kubernetes-kubelet.adoc[Resilient kubelet configuration] for related `kublet` configuration options.
|
||||
|
||||
[[sect-cri-tools]]
|
||||
== CRI-Tools
|
||||
|
||||
link:https://github.com/kubernetes-sigs/cri-tools/[CRI-Tools] is a command line interface to any implementation of the CLI. CRI-Tools is available from the Kubernetes team. It is required when using ```kubeadm``` to initialize a cluster.
|
||||
|
||||
CRI-Tools is available in Fedora repositories as versioned rpms in parallel with Kubernetes. If kubernetes1.30 and kubernetes1.30-kubeadm are installed then cri-tools1.30 needs to be installed.
|
||||
277
modules/ROOT/pages/using-kubernetes-kubeadm.adoc
Normal file
277
modules/ROOT/pages/using-kubernetes-kubeadm.adoc
Normal file
|
|
@ -0,0 +1,277 @@
|
|||
= Creating a Kubernetes cluster on Fedora
|
||||
Bradley G Smith,
|
||||
:revnumber: F37,F38,F39,F40,rawhide
|
||||
:revdate: 2024-07-24
|
||||
:category: Installation
|
||||
:tags: How-to, kubernetes, dnf, rpm, containers, kubeadm, installation
|
||||
:page-aliases: kubernetes/kubeadm
|
||||
|
||||
// Optional free form useful additional information as comment
|
||||
|
||||
//include::{partialsdir}/3rdparty-message.adoc[]
|
||||
include::partial$3rdparty-message.adoc[]
|
||||
|
||||
[cluster-creation]
|
||||
== Creating a Kubernetes cluster with ```kubeadm``` using Fedora rpms
|
||||
|
||||
Below is a guide to creating a functional Kubernetes cluster on a single Fedora machine that is suitable as a learning and exploring environment.
|
||||
This guide is not intended to create a production environment.
|
||||
|
||||
The guide below generally follows and substantially borrows from the link:https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/[Creating a cluster with kubeadm] guide created by the Kubernetes team.
|
||||
|
||||
Fedora 41 has both versioned (v1.29, v1.30, v1.31) and unversioned (v1.29) Kubernetes rpms. We recommend using the versioned rpms as we do not experience the CrashLoopBackoff problem with CoreDNS noted below.
|
||||
|
||||
. Update system with DNF.
|
||||
Reboot if necessary, although a reboot can be deferred until after the next step.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sudo dnf update
|
||||
----
|
||||
|
||||
. Disable swap.
|
||||
The kubeadm installation process will generate a warning if swap is detected (see link:https://github.com/kubernetes/kubernetes/issues/53533[this ticket for details]).
|
||||
For a learning and lab environment it may be easiest to disable swap.
|
||||
Swap can be left enabled if desired and the kubeadm is configured to not stop if swap is detected.
|
||||
Modern Fedora systems use zram by default.
|
||||
Reboot after disabling swap.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sudo systemctl stop swap-create@zram0
|
||||
sudo dnf remove zram-generator-defaults
|
||||
sudo reboot now
|
||||
----
|
||||
|
||||
. SELinux.
|
||||
Most guides to installing Kubernetes on Fedora recommend that xref:getting-started-with-selinux.adoc[SELinux] be disabled.
|
||||
Kubernetes will work well with SELinux enabled and many containers will work as intended.
|
||||
If problems are encountered then disabling SELinux might be one option to try.
|
||||
See xref:selinux-changing-states-and-modes.adoc[the Quick Doc SELinux guide to changing SELinux states] for more information.
|
||||
|
||||
. Disable the firewall.
|
||||
Kubeadm will generate an installation warning if the firewall is running.
|
||||
Disabling the firewall removes one source of complexity in a learning environment.
|
||||
Modern Fedora systems use firewalld.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sudo systemctl disable --now firewalld
|
||||
----
|
||||
+
|
||||
See the Firewall Rules section in Roman Gherta's article link:https://fedoramagazine.org/kubernetes-with-cri-o-on-fedora-linux-39/[Kubernetes with CRI-O on Fedora 39] for the proper way to configure the Fedora firewall to work with Kubernetes,
|
||||
+
|
||||
The current list of ports and protocols used by a Kubernetes cluster can be found at link:https://kubernetes.io/docs/reference/networking/ports-and-protocols/[https://kubernetes.io/docs/reference/networking/ports-and-protocols/].
|
||||
|
||||
. Install `iptables` and `iproute-tc.`
|
||||
Newer Kubernetes rpms include these packages by default.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sudo dnf install iptables iproute-tc
|
||||
----
|
||||
|
||||
. Configure IPv4 forwarding and bridge filters.
|
||||
Below copied from link:https://kubernetes.io/docs/setup/production-environment/container-runtimes/[https://kubernetes.io/docs/setup/production-environment/container-runtimes/]
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sudo cat <<EOF | sudo tee /etc/modules-load.d/k8s.conf
|
||||
overlay
|
||||
br_netfilter
|
||||
EOF
|
||||
----
|
||||
|
||||
. Load the overlay and bridge filter modules.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sudo modprobe overlay
|
||||
sudo modprobe br_netfilter
|
||||
----
|
||||
|
||||
. Add required `sysctl` parameters and persist.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
# sysctl params required by setup, params persist across reboots
|
||||
sudo cat <<EOF | sudo tee /etc/sysctl.d/k8s.conf
|
||||
net.bridge.bridge-nf-call-iptables = 1
|
||||
net.bridge.bridge-nf-call-ip6tables = 1
|
||||
net.ipv4.ip_forward = 1
|
||||
EOF
|
||||
----
|
||||
|
||||
. Apply `sysctl` parameters without a reboot.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sudo sysctl --system
|
||||
----
|
||||
|
||||
. Verify `br_filter` and overlay modules are loaded.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
lsmod | grep br_netfilter
|
||||
lsmod | grep overlay
|
||||
----
|
||||
|
||||
. Verify that the `net.bridge.bridge-nf-call-iptables`, `net.bridge.bridge-nf-call-ip6tables`, and `net.ipv4.ip_forward` system variables are set to `1` in your sysctl configuration by running the following command:
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sysctl net.bridge.bridge-nf-call-iptables net.bridge.bridge-nf-call-ip6tables net.ipv4.ip_forward
|
||||
----
|
||||
|
||||
. Install a link:https://kubernetes.io/docs/setup/production-environment/container-runtimes/[container runtime].
|
||||
CRI-O is installed in this example.
|
||||
Containerd is also an option.
|
||||
Note: If using cri-o, verify that the major:minor version of cri-o is the same as the version of Kubernetes (installed below).
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sudo dnf install cri-o containernetworking-plugins
|
||||
----
|
||||
|
||||
. Install Kubernetes.
|
||||
In this example, all three Kubernetes applications (`kubectl`, `kubelet`, and `kubeadm`) are installed on this single node machine.
|
||||
Please see the notes above on recommended packages for control plane or worker nodes if the cluster will have both types of machines.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
# Fedora 39 and earlier use:
|
||||
sudo dnf install kubernetes-client kubernetes-node kubernetes-kubeadm
|
||||
|
||||
# Fedora 40 and later use:
|
||||
sudo dnf install kubernetes kubernetes-kubeadm kubernetes-client
|
||||
----
|
||||
|
||||
. Start and enable cri-o.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sudo systemctl enable --now crio
|
||||
----
|
||||
|
||||
. Pull needed system container images for Kubernetes.
|
||||
This is strictly optional.
|
||||
The ```kubeadm init``` command below will pull images, if needed.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sudo kubeadm config images pull
|
||||
----
|
||||
|
||||
. Start and enable `kubelet`.
|
||||
Kubelet will be in a crash loop until the cluster is initialized in the next step.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sudo systemctl enable --now kubelet
|
||||
----
|
||||
|
||||
. Initialize the cluster.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sudo kubeadm init --pod-network-cidr=10.244.0.0/16
|
||||
----
|
||||
|
||||
. kubeadm will generate output to the terminal tracking initialization steps.
|
||||
If successful, the output below is displayed.
|
||||
At this point there is a cluster running on this single machine.
|
||||
After kubeadm finishes you should see:
|
||||
+
|
||||
----
|
||||
Your Kubernetes control-plane has initialized successfully!
|
||||
|
||||
To start using your cluster, you need to run the following as a regular user:
|
||||
|
||||
mkdir -p $HOME/.kube
|
||||
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
|
||||
sudo chown $(id -u):$(id -g) $HOME/.kube/config
|
||||
|
||||
Alternatively, if you are the root user, you can run:
|
||||
|
||||
export KUBECONFIG=/etc/kubernetes/admin.conf
|
||||
----
|
||||
|
||||
. The steps listed above allow a non-root user to use `kubectl`, the Kubernetes command line tool.
|
||||
Run these commands now.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
mkdir -p $HOME/.kube
|
||||
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
|
||||
sudo chown $(id -u):$(id -g) $HOME/.kube/config
|
||||
----
|
||||
|
||||
. Allow the control plane machine to also run pods for applications.
|
||||
Otherwise more than one machine is needed in the cluster.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
kubectl taint nodes --all node-role.kubernetes.io/control-plane-
|
||||
----
|
||||
|
||||
. Install flannel into the cluster to provide cluster networking.
|
||||
There are many other networking solutions besides flannel.
|
||||
Flannel is straightforward and suitable for this guide.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
kubectl apply -f https://github.com/coreos/flannel/raw/master/Documentation/kube-flannel.yml
|
||||
----
|
||||
|
||||
. Display list of running pods in the cluster.
|
||||
All pods should display a status of Running.
|
||||
A status of CrashLoopBackOff may show up for the coredns pod.
|
||||
This happens commonly when installing Kubernetes on a virtual machine and the DNS service in the cluster may not select the proper network.
|
||||
Use your favorite internet search engine to find possible solutions. See also the troubleshooting section below for two possible solutions.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
kubectl get pods --all-namespaces
|
||||
----
|
||||
|
||||
At this point there is a single machine in the cluster running the control plane and available for work as a node.
|
||||
|
||||
Upgrades to Kubernetes clusters requires care and planning.
|
||||
See link:https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/[Upgrading kubeadm clusters] for more information.
|
||||
|
||||
The xref:dnf.adoc#sect-using-dnf-plugin[DNF Versionlock plugin] is useful in blocking unplanned updates to Kubernetes rpms.
|
||||
Occasionally, the Kubernetes version in a Fedora release reaches end-of-life and a new version of Kubernetes is added to the repositories.
|
||||
Or, an upgrade to Fedora on a cluster machine will also result in a different version of Kubernetes.
|
||||
Once DNF Versionlock is installed, the following command will hold kubernetes rpms and the cri-o rpm at the 1.28 major:minor version but still allow patch updates to occur:
|
||||
[source,bash]
|
||||
----
|
||||
sudo dnf versionlock add kubernetes*-1.28.* cri-o-1.28.*
|
||||
----
|
||||
|
||||
[cluster-creation-troubleshooting]
|
||||
== Troubleshooting CrashLoopBackOff
|
||||
|
||||
The CoreDNS team provides a guide to link:https://coredns.io/plugins/loop/#troubleshooting-loops-in-kubernetes-clusters[troubleshooting loops in Kubernetes clusters] with several options to help resolve the problem.
|
||||
|
||||
A "quick and dirty" option, as described by the CoreDNS team, is to edit the CoreDNS configmap using `kubectl`. In the configmap, replace `forward . /etc/resolv.conf` with the IP address of the DNS server for your network. If the DNS server has an IP address of `192.168.110.201` then the result would look like `forward . 192.168.110.201`. To edit the CoreDNS configmap use:
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
kubectl edit configmap coredns -n kube-system
|
||||
----
|
||||
|
||||
`kubectl` will launch the editor for your instance of Fedora. The Fedora default is `nano` which can be easily changed.
|
||||
|
||||
Another option is to disable the systemd-resolved stub resolving on the machine hosting the cluster using the code below. Many thanks for @jasonbrooks (https://pagure.io/user/jasonbrooks) for his review and recommendations.
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
sudo mkdir -p /etc/systemd/resolved.conf.d/
|
||||
sudo cat <<EOF | sudo tee /etc/systemd/resolved.conf.d/stub-listener.conf
|
||||
[Resolve]
|
||||
DNSStubListener=no
|
||||
EOF
|
||||
----
|
||||
|
||||
|
||||
93
modules/ROOT/pages/using-kubernetes-kubelet.adoc
Normal file
93
modules/ROOT/pages/using-kubernetes-kubelet.adoc
Normal file
|
|
@ -0,0 +1,93 @@
|
|||
= Resilient kubelet configuration
|
||||
Bradley G Smith,
|
||||
:revnumber: F39,F40,F41
|
||||
:revdate: 2024-07-28
|
||||
:category: Installation
|
||||
:tags: How-to, kubernetes, dnf, rpm, containers, kubeadm, installation
|
||||
:page-aliases: kubernetes/kubelet
|
||||
|
||||
// Optional free form useful additional information as comment
|
||||
|
||||
//include::{partialsdir}/3rdparty-message.adoc[]
|
||||
include::partial$3rdparty-message.adoc[]
|
||||
|
||||
[[overview]]
|
||||
== kubelet overview
|
||||
|
||||
The ```kublet``` is the Kubernetes agent that runs on every node in a cluster. ```kublet``` is installed using the kubernetes rpm (_e.g._ ```kubernetes1.30``` is a versioned rpm for Kubernetes v1.30). The ```kubelet``` runs as a systemd service on Fedora. In early implementations, the ```kubelet``` was configured via link:https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/[flags] that were set in a systemd unit file and passed to the ```kubelet``` as command line parameters.
|
||||
|
||||
In more recent versions of the ```kubelet``` these flags are deprecated in favor of a link:https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/[configuration file] that uses either JSON or YAML for the configuration syntax.
|
||||
|
||||
The legacy non-versioned rpms use, by default, flags to configure the ```kubelet```. Versioned rpms use the configuration file method.
|
||||
|
||||
With both versioned and non-versioned rpms, all files, including systemd related files, can be erased during version updates (_e.g._ kubernetes1.29 to kubernetes1.30 - minor version updates). If these files are modified by the user then there is risk that useful or important changes can be lost. Systemd provides options that help safeguard against loss of node-specific configurations.
|
||||
|
||||
[[systemd]]
|
||||
== Systemd configuration recommendations
|
||||
|
||||
Flags for the ```kublet``` running on a node are set in a systemd unit file with the relevant file dependent on which rpms are installed.
|
||||
|
||||
The kubernetes rpm (_e.g_ kubernetes1.30 for version 1.30) installs the default ```kubelet``` systemd file at:
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
/usr/lib/systemd/system/kubelet.service
|
||||
----
|
||||
|
||||
The kubernetes-kubeadm rpm installs an overriding ```kubelet``` unit file at:
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
/usr/lib/systemd/system/kubelet.service.d/10-kubeadm.conf
|
||||
----
|
||||
|
||||
We strongly recommend to *not* modify either file as any changes could be lost during an update.
|
||||
|
||||
As documented by the Kubernetes team (link:https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/kubelet-integration/#the-kubelet-drop-in-file-for-systemd)[https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/kubelet-integration/#the-kubelet-drop-in-file-for-systemd]), create the following directory for user managed, system-level systemd ```kubelet``` overrides:
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
$ sudo mkdir -p /etc/systemd/system/kubelet.service.d/
|
||||
----
|
||||
|
||||
Then create a unit file (```.conf``` extension required) and copy the file to the directory listed above. Settings in this file will override settings from either or both of the default systemd files.
|
||||
|
||||
This file is not managed by the system package manager and will be unchanged by kubernetes version updates. Be sure to have software version control and/or a backup plan in place to avoid loss during a Fedora system upgrade or crash.
|
||||
|
||||
[[configfile]]
|
||||
== Configuration file recommendations
|
||||
|
||||
All versioned kubernetes rpms use a ```kubelet``` configuration file by default. If this file does not exist it will be created during the cluster instantiation process. The default configuration file location is:
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
# default configuration file
|
||||
$ /var/lib/kubelet/config.yaml
|
||||
----
|
||||
|
||||
This file is *not* managed by rpm so will persist across kubernetes upgrades.
|
||||
|
||||
[[configfile-dropin]]
|
||||
=== Drop-in configuration file
|
||||
|
||||
Kubernetes 1.30 and newer have a drop-in configuration file option that is *not* enabled by default.
|
||||
In a systemd file define a path using the ```--config-dir``` option:
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
# define configdir
|
||||
--config-dir=/etc/kubernetes/kubelet.conf.d
|
||||
----
|
||||
|
||||
See link:https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/#kubelet-conf-d[the online documentation] for current information including an option to enable this feature for v1.28 or v1.29.
|
||||
|
||||
[[configfile-merge-order]]
|
||||
=== Configuration file merge order
|
||||
|
||||
As the ```kubelet``` starts, configuration settings are merged in the following order (link:https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/#kubelet-configuration-merging-order[merge order documentation]):
|
||||
|
||||
. Feature gates specified over the command line (lowest precedence).
|
||||
. The kubelet configuration.
|
||||
. Drop-in configuration files, according to sort order.
|
||||
. Command line arguments excluding feature gates (highest precedence).
|
||||
|
||||
164
modules/ROOT/pages/using-kubernetes-non-versioned.adoc
Normal file
164
modules/ROOT/pages/using-kubernetes-non-versioned.adoc
Normal file
|
|
@ -0,0 +1,164 @@
|
|||
= Non-versioned Kubernetes RPMS on Fedora
|
||||
Bradley G Smith,
|
||||
:revnumber: F39,F40,F41
|
||||
:revdate: 2024-07-30
|
||||
:category: Installation
|
||||
:tags: How-to, kubernetes, dnf, rpm, containers
|
||||
|
||||
// Optional free form useful additional information as comment
|
||||
|
||||
//include::{partialsdir}/3rdparty-message.adoc[]
|
||||
include::partial$3rdparty-message.adoc[]
|
||||
|
||||
[[sect-overview]]
|
||||
== Overview
|
||||
|
||||
Non-versioned Kubernetes RPMS are the standard rpm format for Kubernetes through Fedora 40. Fedora 41 (currently rawhide) contains both versioned and non-versioned rpms.
|
||||
|
||||
[[sect-kubernetes-rpms]]
|
||||
== Non-versioned Kubernetes rpms in Fedora
|
||||
|
||||
The number, name, and organization of content in Fedora Kubernetes rpms depends on the Fedora release.
|
||||
Fedora 40 and newer releases (starting with Kubernetes v1.29) have one set of rpms.
|
||||
Fedora 39 and older releases have the legacy set of rpms.
|
||||
|
||||
[[sect-fedora-39-and-older]]
|
||||
=== Fedora 39 and older releases
|
||||
|
||||
The table below lists the available Kubernetes rpms in Fedora 39 and older releases, what the rpm contains, and notes on purpose and any restrictions or cautions.
|
||||
|
||||
.Kubernetes rpms in Fedora 39 (and older)
|
||||
[cols="1,1,1", options="header"]
|
||||
|===
|
||||
|RPM Name |Contents |Notes
|
||||
|kubernetes
|
||||
|Empty
|
||||
|Also installs kubernetes-node and kubernetes-master.
|
||||
|
||||
|kubernetes-client
|
||||
|kubectl
|
||||
|Kubernetes command line client.
|
||||
Recommended on any node configured as a control plane as it allows the cluster administrator control over the cluster from an ssh session on the control plane.
|
||||
Install on a machine that can connect to the cluster over the network.
|
||||
|
||||
|kubernetes-kubeadm
|
||||
|kubeadm
|
||||
|Kubeadm initializes a cluster and joins new nodes to a cluster.
|
||||
This rpm is optional but recommended by the Kubernetes team.
|
||||
Install on every node if used.
|
||||
|
||||
|kubernetes-master
|
||||
|kube-apiserver, kube-controller-manager, kube-proxy, kube-scheduler
|
||||
|Systemd services for a kubernetes node.
|
||||
Not needed for most installations as kubeadm will install these components as static pods.
|
||||
If used, then install on each node.
|
||||
Also installs kubernetes-client.
|
||||
|
||||
|kubernetes-node
|
||||
|kubelet
|
||||
|Kubernetes runtime on a node.
|
||||
Required on each node.
|
||||
|===
|
||||
|
||||
[[sect-fedora-39-recommendations]]
|
||||
==== Fedora 39 (and older) Installation recommendations
|
||||
|
||||
For most modern kubernetes clusters install kubernetes-node, kubernetes-kubeadm, and kubernetes-client on each machine in the cluster.
|
||||
If disk space is a constraint only install kubernetes-client on control-plane machines.
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
sudo dnf install kubernetes-kubeadm kubernetes-node kubernetes-client
|
||||
----
|
||||
|
||||
If conducting a manual installation of Kubernetes (see link:https://github.com/kelseyhightower/kubernetes-the-hard-way[Kubernetes The Hard Way]) then install kubernetes-master and kubernetes-kubeadm.
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
sudo dnf install kubernetes-master kubernetes-kubeadm kubernetes-node kubernetes-client
|
||||
----
|
||||
|
||||
[[sect-fedora40-and-41]]
|
||||
=== Fedora 40 and 41 non-versioned rpms
|
||||
|
||||
Kubernetes rpms have been reorganized starting with Kubernetes version 1.29 in Fedora 40.
|
||||
The table below lists the available Kubernetes rpms, what the rpm contains, and notes on purpose and any cautions or restrictions.
|
||||
|
||||
.Kubernetes rpms in Fedora 40 and 41
|
||||
[cols="1,1,1", options="header"]
|
||||
|===
|
||||
|RPM Name|Contents|Notes
|
||||
|kubernetes
|
||||
|kubelet
|
||||
|Kubelet is the Kubernetes runtime on a node.
|
||||
|
||||
|kubernetes-kubeadm
|
||||
|kubeadm
|
||||
|Kubeadm initializes a cluster and joins new nodes to a cluster.
|
||||
This rpm is optional but recommended by the Kubernetes team.
|
||||
Install on every node if used.
|
||||
|
||||
|kubernetes-client
|
||||
|kubectl
|
||||
|Kubernetes command line client.
|
||||
Recommended on any node configured as a control plane as it allows the cluster administrator control over the cluster from an ssh session on the control plane.
|
||||
Install on a machine that can connect to the cluster over the network.
|
||||
|
||||
|kubernetes-systemd
|
||||
|kube-apiserver, kube-controller-manager, kube-proxy, kube-scheduler
|
||||
|Systemd services for a kubernetes control-plane and/or node.
|
||||
Not needed for most installations as kubeadm will install these components as static pods.
|
||||
If used, then install on all nodes.
|
||||
Use systemctl to enable kube-proxy on all nodes. Enable kube-apiserver, kube-controller-manager, and kube-scheduler on control plane nodes.
|
||||
|
||||
|===
|
||||
|
||||
[[sect-fedora-40-recommendations]]
|
||||
==== Fedora 40 (and newer) installation recommendations
|
||||
|
||||
For most modern kubernetes clusters install kubernetes, kubernetes-kubeadm, and kubernetes-client on each machine in the cluster.
|
||||
If disk space is a constraint only install kubernetes-client on control-plane machines.
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
sudo dnf install kubernetes kubernetes-kubeadm kubernetes-client
|
||||
----
|
||||
|
||||
If conducting a manual installation of Kubernetes (see link:https://github.com/kelseyhightower/kubernetes-the-hard-way[Kubernetes The Hard Way]) then install all kubernetes rpms except kubernetes-kubeadm.
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
sudo dnf install kubernetes kubernetes-client kubernetes-systemd
|
||||
----
|
||||
|
||||
[[sect-kubernetes-fedora-crosswalk]]
|
||||
== Kubernetes and Fedora version crosswalk
|
||||
|
||||
Each Fedora release has a corresponding version of Kubernetes available as listed below.
|
||||
The goal is to provide the most current Kubernetes release available when a Fedora release reaches General Availability (GA).
|
||||
This is not always possible resulting in skipped Kubernetes releases.
|
||||
Skipping a release causes problems for Kubernetes cluster administrators given the Kubernetes cluster upgrade process.
|
||||
Alternative ways to package Kubernetes for Fedora are being explored.
|
||||
|
||||
The version of the Go programming language supported for a given Fedora release can also limit the version of Kubernetes available if Kubernetes requires a newer version of Go.
|
||||
|
||||
.Kubernetes versions and the corresponding Fedora release
|
||||
[cols="1,1,1,1", options="header"]
|
||||
|===
|
||||
|Kubernetes Version |Target Fedora Release | Kubernetes End-of-Life | Kubernetes Golang 'Built-With' Version
|
||||
|1.29
|
||||
|F40/F41
|
||||
|2025.02.28
|
||||
|1.21
|
||||
|
||||
|1.28
|
||||
|COPR^1^
|
||||
|2024.10.28
|
||||
|1.21 (was 1.20)
|
||||
|
||||
|1.27
|
||||
|F39
|
||||
|2024.06.28
|
||||
|1.21 (was 1.20)
|
||||
|===
|
||||
|
||||
128
modules/ROOT/pages/using-kubernetes-versioned.adoc
Normal file
128
modules/ROOT/pages/using-kubernetes-versioned.adoc
Normal file
|
|
@ -0,0 +1,128 @@
|
|||
= Versioned Kubernetes RPMS on Fedora
|
||||
Bradley G Smith,
|
||||
:revnumber: F41,rawhide
|
||||
:revdate: 2024-07-27
|
||||
:category: Installation
|
||||
:tags: How-to, kubernetes, dnf, rpm, containers
|
||||
:page-aliases: kubernetes/versioned
|
||||
|
||||
// Optional free form useful additional information as comment
|
||||
|
||||
//include::{partialsdir}/3rdparty-message.adoc[]
|
||||
include::partial$3rdparty-message.adoc[]
|
||||
|
||||
[[sect-overview]]
|
||||
== Overview
|
||||
|
||||
Versioned Kubernetes rpms were introduced in Fedora 41 and will be the format used in subsequent releases.
|
||||
Past practice had one version of Kubernetes available for each Fedora release.
|
||||
The differing release cadences for Fedora (a new release every 6 months) and Kubernetes (a new version every quarter) resulted in either the version of Kubernetes available falling well behind or skipping Kubernetes releases.
|
||||
Neither option provided a good user experience for Fedora users.
|
||||
|
||||
Versioned rpms solve these problems by providing all supported Kubernetes versions on each Fedora release (subject to a Golang constraint - see below).
|
||||
Fedora 41 (currently rawhide) has rpms for Kubernetes 1.31, Kubernetes 1.30, Kubernetes 1.29, and Kubernetes 1.28.
|
||||
These rpms will be named, respectively, kubernetes1.31, kubernetes1.30, kubernetes1.29, and kubernetes1.28.
|
||||
Since these rpms have different names, the Fedora package manager, rpm, identifies them as different applications, not as different versions of the same application.
|
||||
Because of this difference, versioned rpms require changes to the normal package update process is be documented below.
|
||||
|
||||
[[changes]]
|
||||
=== What Changed? ===
|
||||
|
||||
The versioned rpms contain several changes and updates that differ from the non-version rpms. For the most part these changes should not affect usage or rpm updates but a few are worth attention.
|
||||
|
||||
[ordered]
|
||||
kubelet configuration:: ```kubelet``` configuration now uses the ```kubelet``` configuration file rather than flags passed as command line parameters in the systemd unit file.
|
||||
|
||||
kubelet systemd files:: ```kubelet``` systemd unit files are now largely consistent with corresponding unit files used by the Kubernetes team in their rpms. In particular, kubelet now defaults to runtime configuration using the standard ```kubelet``` configuration file. Non-versioned rpms used command line parameters in systemd files to configure```kubelet```.
|
||||
|
||||
kubelet sysuser:: non-versioned rpms created a ```kube``` sysuser for ```kubelet```. This sysuser was used for file and group ownership of some but not all files and directories used by ```kubelet```. This sysuser was not present in rpms from the Kubernetes team and, given its partial implementation in Fedora, removed from the versioned rpms.
|
||||
|
||||
[[golang-constraint]]
|
||||
=== Go language constraint
|
||||
|
||||
Each Kubernetes version (at the _minor_ level, _e.g._ Kubernetes v1.31) is built with a specific version of the go language. Each Fedora release is paired with a specific go version. Go 1.22 is available on Fedora 40 and go 1.23 is available on Fedora 41.
|
||||
|
||||
A new Kubernetes version may be built with a version of Go not available on older Fedora releases thereby blocking the packaging of that Kubernetes version for that Fedora release.
|
||||
|
||||
[[sect-kubernetes-rpms]]
|
||||
== Kubernetes rpms in Fedora
|
||||
|
||||
Versioned Kubernetes rpms have the following organization.
|
||||
Note that this package structure also applies to the kubernetes1.28 and kubernetes1.29 packages which is different from the non-versioned counterparts of these Kubernetes versions.
|
||||
The table below lists the available Kubernetes rpms, what the rpm contains, and notes on purpose and any cautions or restrictions.
|
||||
|
||||
.Versioned Kubernetes rpms in Fedora 41 (and newer)
|
||||
[cols="1,1,1", options="header"]
|
||||
|===
|
||||
|RPM Name|Contents|Notes
|
||||
|kubernetes
|
||||
|kubelet
|
||||
|Kubelet is the Kubernetes runtime on a node.
|
||||
|
||||
|kubernetes-kubeadm
|
||||
|kubeadm
|
||||
|Kubeadm initializes a cluster and joins new nodes to a cluster.
|
||||
This rpm is optional but recommended by the Kubernetes team.
|
||||
Install on every node if used.
|
||||
|
||||
|kubernetes-client
|
||||
|kubectl
|
||||
|Kubernetes command line client.
|
||||
Recommended on any node configured as a control plane as it allows the cluster administrator control over the cluster from an ssh session on the control plane.
|
||||
Install on a machine that can connect to the cluster over the network.
|
||||
|
||||
|kubernetes-systemd
|
||||
|kube-apiserver, kube-controller-manager, kube-proxy, kube-scheduler
|
||||
|Systemd services for a kubernetes control-plane and/or node.
|
||||
Not needed for most installations as kubeadm will install these components as static pods.
|
||||
If used, then install on all nodes.
|
||||
Use systemctl to enable kube-proxy on all nodes. Enable kube-apiserver, kube-controller-manager, and kube-scheduler on control plane nodes.
|
||||
|
||||
|===
|
||||
|
||||
[[sect-fedora-40-installation]]
|
||||
== Versioned rpm installation recommendations
|
||||
|
||||
For most modern kubernetes clusters install kubernetes, kubernetes-kubeadm, and kubernetes-client on each machine in the cluster.
|
||||
If disk space is a constraint only install kubernetes-client on control-plane machines.
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
# using kubernetes 1.30 as an example
|
||||
sudo dnf install kubernetes1.30 kubernetes1.30-kubeadm kubernetes1.30-client
|
||||
----
|
||||
|
||||
If conducting a manual installation of Kubernetes (see link:https://github.com/kelseyhightower/kubernetes-the-hard-way[Kubernetes The Hard Way]) then install all kubernetes rpms except kubernetes-kubeadm.
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
# using kubernetes 1.30 as an example
|
||||
sudo dnf install kubernetes1.30 kubernetes1.30-client kubernetes1.30-systemd
|
||||
----
|
||||
|
||||
[[sect-fedora-40-version-update]]
|
||||
== Versioned rpm update recommendations
|
||||
|
||||
Since rpm treats kubernetes1.30 as a different application from kubernetes1.31, yet both rpms install the same files in the same locationsthey conflict and the normal ```dnf update``` will not succeed in replacing v1.30 with v1.31.
|
||||
There are two options available when using dnf: remove/install or swap.
|
||||
|
||||
The remove and install sequence using normal ```dnf``` commands to first remove one version of Kubernetes and then replace it with the next version. Both ```dnf``` commands will also remove/install any dependencies.
|
||||
|
||||
*Important Note* - this is only needed when changing minor versions, that is replacing v1.30 with v1.31. Updates at the patch level such as v1.30.2 to v1.30.3 use the normal ```dnf update``` command.
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
# Remove and replace with kubernetes 1.30 and 1.31 as an example
|
||||
sudo dnf remove kubernetes1.30 kubernetes1.30-kubeadm kubernetes1.30-client
|
||||
sudo dnf install kubernetes1.31 kubernetes1.31-kubeadm kubernetes1.31-client
|
||||
----
|
||||
|
||||
The ```dnf swap``` command can also be used to change from one Kubernetes release to the next. Using swap avoids re-installation of dependencies but the ```kubernetes1.31*``` dnf package specification will install all matching rpms from the repository and not just the rpms removed by the initial ```kubernetes1.30*``` package specification.:w
|
||||
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
# Remove and replace with kubernetes 1.30 and 1.31 as an example
|
||||
sudo dnf swap kubernetes1.30* kubernetes1.31*
|
||||
----
|
||||
|
||||
|
|
@ -1,7 +1,7 @@
|
|||
= Using Kubernetes on Fedora
|
||||
Bradley G Smith,
|
||||
:revnumber: F37,F38,F39,F40,rawhide
|
||||
:revdate: 2023-12-23
|
||||
:revdate: 2024-07-27
|
||||
:category: Installation
|
||||
:tags: How-to, kubernetes, dnf, rpm, containers
|
||||
|
||||
|
|
@ -13,479 +13,51 @@ include::partial$3rdparty-message.adoc[]
|
|||
[[sect-overview]]
|
||||
== Overview
|
||||
|
||||
This how-to provides an overview of the link:https://kubernetes.io[Kubernetes] (K8s) rpms in the Fedora repositories, how to use them in a few scenarios and a short cluster creation guide using `kubeadm` on a single Fedora machine.
|
||||
This guide provides useful information about link:https://kubernetes.io[Kubernetes] and the Kubernetes rpms available from Fedora.
|
||||
|
||||
Starting with Fedora 41 (currently rawhide) the packaging standard for Kubernetes changed from one version of Kubernetes for each Fedora release (_non-versioned_ rpms) to all versions of Kubernetes available for each release of Fedora (_versioned_ rpms - with availability subject to a link:https://go.dev[Golang] language constraint).
|
||||
These changes are documented here, including what changed, and how installation of these rpms has been affected.
|
||||
A short guide on creating a Kubernetes cluster using ```kubeadm``` is included, as a short introduction to Kubernetes for those new to this technology stack.
|
||||
|
||||
The guide also touches on an alternative source for Kubernetes rpms available in link:https://copr.fedorainfracloud.org[COPR] and potential benefits.
|
||||
|
||||
[[sect-what-is-kubernetes]]
|
||||
=== What is Kubernetes?
|
||||
|
||||
link:https:/kubernetes.io[Kubernetes] is an "open-source system for automating deployment, scaling, and management of containerized applications" on one or more machines.
|
||||
Kubernetes had its genesis in the concepts and principles used at Google to run container-base workloads at scale and with resilience.
|
||||
Kubernetes automates many of the tasks necessary to deploy, manage, and scale applications that are running as a container.
|
||||
This automation is vital when managing applications in data center or cloud environment where there are 100's or 1000's of machines and a corresponding complexity in numbers of applications.Fedora provides several technologies, in addition to Kubernetes, that run containers such as link:https://docker.com[Docker] or link:https://podman.io[Podman].
|
||||
|
||||
Kubernetes is now at the center of a vast ecosystem of products and services (link:https://cncf.io/[Cloud Native Computing Foundation]) that help organizations create, install, run, manage and secure container-based applications and services at any possible scale.
|
||||
|
||||
There are numerous ways to install and configure Kubernetes depending on purpose and target environment.
|
||||
Is this for a home lab on a single machine, a small cluster for home or business automation, edge-based services and applications in remote offices or enterprise scale production workloads in the cloud?
|
||||
Kubernetes can be used in a home lab on a single machine, a small cluster for home or business automation, edge-based services and applications in remote offices or enterprise scale production workloads in the cloud.
|
||||
|
||||
This guide is narrowly focused on the Kubernetes rpms available from Fedora and using `dnf` and the command line to install these rpms on Fedora and create a basic cluster using `kubeadm`.
|
||||
|
||||
[[sect-terminology]]
|
||||
=== Terminology
|
||||
Please visit the xref:virtualization-an-overview.adoc[Fedora Quick Docs Virtualization Guide] to learn more about containers and other virtualization technologies and their availability in Fedora.
|
||||
|
||||
Kubernetes is complex and like many complex systems has its own terminology.
|
||||
The terminology used in this guide are defined here.
|
||||
The Kubernetes teams maintains a comprehensive link:https://kubernetes.io/docs/reference/glossary/[glossary] which is used in the subset below.
|
||||
[[sect-content-guide]]
|
||||
== Content guide
|
||||
|
||||
[horizontal]
|
||||
cluster:: a set of one or more nodes managed as an entity.
|
||||
A cluster has at least one node and one control plane (these can be on the same or separate machines).
|
||||
control plane:: the node or nodes in the cluster hosting the management services for the cluster.
|
||||
At least one node in a cluster has a control plane.
|
||||
A control plane machine can also function as a worker node.
|
||||
node:: a worker machine (either a virtual machine or physical machine) in a Kubernetes cluster that has the services required to run pods.
|
||||
These services include the `kubelet` container runtime and `kube-proxy`.
|
||||
pods:: containerized applications are deployed and managed in Kubernetes as pods.
|
||||
A pod is the base object managed by Kubernetes in a cluster.
|
||||
A pod typically has a single primary container but may include more capabilities including multiple containers.
|
||||
|
||||
[[sect-kubernetes-rpms]]
|
||||
== Kubernetes rpms in Fedora
|
||||
|
||||
The number, name, and organization of content in Fedora Kubernetes rpms depends on the Fedora release.
|
||||
Fedora 40 and newer releases (starting with Kubernetes v1.29) have one set of rpms.
|
||||
Fedora 39 and older releases have the legacy set of rpms.
|
||||
|
||||
[[sect-fedora-39-and-older]]
|
||||
=== Fedora 39 and older releases
|
||||
|
||||
The table below lists the available Kubernetes rpms in Fedora 39 and older releases, what the rpm contains, and notes on purpose and any restrictions or cautions.
|
||||
|
||||
.Kubernetes rpms in Fedora 39 (and older)
|
||||
[cols="1,1,1", options="header"]
|
||||
[cols="1,1"]
|
||||
|===
|
||||
|RPM Name |Contents |Notes
|
||||
|kubernetes
|
||||
|Empty
|
||||
|Also installs kubernetes-node and kubernetes-master.
|
||||
|xref:using-kubernetes-basics.adoc[Basics]
|
||||
|A brief overview of Kubernetes for those new to the technology along with a terminology table.
|
||||
|
||||
|kubernetes-client
|
||||
|kubectl
|
||||
|Kubernetes command line client.
|
||||
Recommended on any node configured as a control plane as it allows the cluster administrator control over the cluster from an ssh session on the control plane.
|
||||
Install on a machine that can connect to the cluster over the network.
|
||||
|xref:using-kubernetes-non-versioned.adoc[Non-versioned rpms - Fedora 40 and older]
|
||||
|The guide to the legacy, non-versioned rpm format for Kubernetes in Fedora 41, 40, and 39.
|
||||
|
||||
|kubernetes-kubeadm
|
||||
|kubeadm
|
||||
|Kubeadm initializes a cluster and joins new nodes to a cluster.
|
||||
This rpm is optional but recommended by the Kubernetes team.
|
||||
Install on every node if used.
|
||||
|xref:using-kubernetes-versioned.adoc[Versioned rpms - Fedora 41 and newer]
|
||||
|The guide to the versioned rpm format for Kubernetes in Fedora 41 and newer.
|
||||
|
||||
|kubernetes-master
|
||||
|kube-apiserver, kube-controller-manager, kube-proxy, kube-scheduler
|
||||
|Systemd services for a kubernetes node.
|
||||
Not needed for most installations as kubeadm will install these components as static pods.
|
||||
If used, then install on each node.
|
||||
Also installs kubernetes-client.
|
||||
|xref:using-kubernetes-kubelet.adoc[Resilient ```kubelet``` configuration]
|
||||
| A brief guide to ```kubelet``` configuration methods.
|
||||
|
||||
|kubernetes-node
|
||||
|kubelet
|
||||
|Kubernetes runtime on a node.
|
||||
Required on each node.
|
||||
|===
|
||||
|xref:using-kubernetes-kubeadm.adoc[Create a cluster]
|
||||
|The guide to using ```kubeadm``` to instantiate a Kubernetes cluster on a single Fedora machine for exploration, testing, and development.
|
||||
|
||||
[[sect-fedora-39-recommendations]]
|
||||
==== Fedora 39 (and older) Installation recommendations
|
||||
|
||||
For most modern kubernetes clusters install kubernetes-node, kubernetes-kubeadm, and kubernetes-client on each machine in the cluster.
|
||||
If disk space is a constraint only install kubernetes-client on control-plane machines.
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
sudo dnf install kubernetes-kubeadm kubernetes-node kubernetes-client
|
||||
----
|
||||
|
||||
If conducting a manual installation of Kubernetes (see link:https://github.com/kelseyhightower/kubernetes-the-hard-way[Kubernetes The Hard Way]) then install kubernetes-master and kubernetes-kubeadm.
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
sudo dnf install kubernetes-master kubernetes-kubeadm kubernetes-node kubernetes-client
|
||||
----
|
||||
|
||||
[[sect-fedora40-and-newer]]
|
||||
=== Fedora 40 and newer releases
|
||||
|
||||
Kubernetes rpms have been reorganized starting with Kubernetes version 1.29 in Fedora 40.
|
||||
Rawhide for Fedora 40 initially started with Kubernetes v1.28 and the legacy package organization but these have been superseded by Kubernetes v1.29 starting in late January 2024.
|
||||
The table below lists the available Kubernetes rpms, what the rpm contains, and notes on purpose and any cautions or restrictions.
|
||||
|
||||
.Kubernetes rpms in Fedora 40 (and newer)
|
||||
[cols="1,1,1", options="header"]
|
||||
|===
|
||||
|RPM Name|Contents|Notes
|
||||
|kubernetes
|
||||
|kubelet
|
||||
|Kubelet is the Kubernetes runtime on a node.
|
||||
|
||||
|kubernetes-kubeadm
|
||||
|kubeadm
|
||||
|Kubeadm initializes a cluster and joins new nodes to a cluster.
|
||||
This rpm is optional but recommended by the Kubernetes team.
|
||||
Install on every node if used.
|
||||
|
||||
|kubernetes-client
|
||||
|kubectl
|
||||
|Kubernetes command line client.
|
||||
Recommended on any node configured as a control plane as it allows the cluster administrator control over the cluster from an ssh session on the control plane.
|
||||
Install on a machine that can connect to the cluster over the network.
|
||||
|
||||
|kubernetes-systemd
|
||||
|kube-apiserver, kube-controller-manager, kube-proxy, kube-scheduler
|
||||
|Systemd services for a kubernetes control-plane and/or node.
|
||||
Not needed for most installations as kubeadm will install these components as static pods.
|
||||
If used, then install on all nodes.
|
||||
Use systemctl to enable kube-proxy on all nodes. Enable kube-apiserver, kube-controller-manager, and kube-scheduler on control plane nodes.
|
||||
|xref:using-kubernetes-cri-o.adoc[CRI-O and CRI-Tools]
|
||||
|The guide to the new versions of link:https://cri-o.io[CRI-O] and link:https://github.com/kuberbetes/cri-tools[CRI-Tools] available in Fedora 41 and newer.
|
||||
|
||||
|===
|
||||
|
||||
[[sect-fedora-40-recommendations]]
|
||||
==== Fedora 40 (and newer) installation recommendations
|
||||
|
||||
For most modern kubernetes clusters install kubernetes, kubernetes-kubeadm, and kubernetes-client on each machine in the cluster.
|
||||
If disk space is a constraint only install kubernetes-client on control-plane machines.
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
sudo dnf install kubernetes kubernetes-kubeadm kubernetes-client
|
||||
----
|
||||
|
||||
If conducting a manual installation of Kubernetes (see link:https://github.com/kelseyhightower/kubernetes-the-hard-way[Kubernetes The Hard Way]) then install all kubernetes rpms except kubernetes-kubeadm.
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
sudo dnf install kubernetes kubernetes-client kubernetes-systemd
|
||||
----
|
||||
|
||||
[[sect-kubernetes-fedora-crosswalk]]
|
||||
== Kubernetes and Fedora version crosswalk
|
||||
|
||||
Each Fedora release has a corresponding version of Kubernetes available as listed below.
|
||||
The goal is to provide the most current Kubernetes release available when a Fedora release reaches General Availability (GA).
|
||||
This is not always possible resulting in skipped Kubernetes releases.
|
||||
Skipping a release causes problems for Kubernetes cluster administrators given the Kubernetes cluster upgrade process.
|
||||
Alternative ways to package Kubernetes for Fedora are being explored.
|
||||
|
||||
The version of the Go programming language supported for a given Fedora release can also limit the version of Kubernetes available if Kubernetes requires a newer version of Go.
|
||||
|
||||
.Kubernetes versions and the corresponding Fedora release
|
||||
[cols="1,1,1,1", options="header"]
|
||||
|===
|
||||
|Kubernetes Version |Target Fedora Release | Kubernetes End-of-Life | Kubernetes Golang 'Built-With' Version
|
||||
|1.30
|
||||
|F41
|
||||
|2025.06.28
|
||||
|1.22
|
||||
|
||||
|1.29
|
||||
|F40
|
||||
|2025.02.28
|
||||
|1.21
|
||||
|
||||
|1.28
|
||||
|COPR^1^
|
||||
|2024.10.28
|
||||
|1.21 (was 1.20)
|
||||
|
||||
|1.27
|
||||
|F39
|
||||
|2024.06.28
|
||||
|1.21 (was 1.20)
|
||||
|
||||
|1.26
|
||||
|F38
|
||||
|End Of Life
|
||||
|1.21 (was 1.19; was 1.20)
|
||||
|===
|
||||
|
||||
^1^ Rawhide for Fedora 40 was initialized with Kubernetes v1.28. Kubernetes v1.29 went live while Fedora 40 was still in rawhide and superseded v1.28. Since Fedora 39 has Kubernetes v1.27 and changing to v1.28 would be problematic for existing clusters, Kubernetes v1.28 was moved to a link:https://copr.fedorainfracloud.org/coprs/buckaroogeek/copr-k8s-1.28/[COPR project].
|
||||
|
||||
[cluster-creation]
|
||||
== Creating a Kubernetes cluster with kubeadm using Fedora rpms
|
||||
|
||||
Below is a guide to creating a functional Kubernetes cluster on a single Fedora machine that is suitable as a learning and exploring environment.
|
||||
This guide is not intended for production environments.
|
||||
|
||||
Each Fedora release has a corresponding Kubernetes release as documented at the link:https://src.fedoraproject.org/rpms/kubernetes[Fedora Package Sources repository for Kubernetes].
|
||||
Fedora 39, for example, has rpms for Kubernetes 1.27.
|
||||
The cluster initialization is the same for all current Fedora releases.
|
||||
These instructions have been tested on Fedora 38 and Fedora 39 virtual machines and on Raspberry Pi 4 hardware running Fedora 38 and Fedora 39 minimal.
|
||||
The guide below generally follows the link:https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/[Creating a cluster with kubeadm] guide.
|
||||
|
||||
. Update system with DNF.
|
||||
Reboot if necessary, although a reboot can be deferred until after the next step.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sudo dnf update
|
||||
----
|
||||
|
||||
. Disable swap.
|
||||
Kubernetes is configured to generate an installation error if swap is detected (see link:https://github.com/kubernetes/kubernetes/issues/53533[this ticket for details]).
|
||||
Modern Fedora systems use zram by default.
|
||||
Reboot after disabling swap.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sudo systemctl stop swap-create@zram0
|
||||
sudo dnf remove zram-generator-defaults
|
||||
sudo reboot now
|
||||
----
|
||||
|
||||
. Disable the firewall.
|
||||
Kubeadm will generate an installation warning if the firewall is running.
|
||||
Disabling the firewall removes one source of complexity in a learning environment.
|
||||
Modern Fedora systems use firewalld.
|
||||
See link:https://devopstales.github.io/kubernetes/k8s-security/#use-firewalld[https://devopstales.github.io/kubernetes/k8s-security/#use-firewalld] for an alternative solution that retains the firewall and opens necessary ports.
|
||||
The current list of ports and protocols used by a Kubernetes cluster can be found at link:https://kubernetes.io/docs/reference/networking/ports-and-protocols/[https://kubernetes.io/docs/reference/networking/ports-and-protocols/].
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sudo systemctl disable --now firewalld
|
||||
----
|
||||
|
||||
. Install `iptables` and `iproute-tc.`
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sudo dnf install iptables iproute-tc
|
||||
----
|
||||
|
||||
. Configure IPv4 forwarding and bridge filters.
|
||||
Below copied from link:https://kubernetes.io/docs/setup/production-environment/container-runtimes/[https://kubernetes.io/docs/setup/production-environment/container-runtimes/]
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sudo cat <<EOF | sudo tee /etc/modules-load.d/k8s.conf
|
||||
overlay
|
||||
br_netfilter
|
||||
EOF
|
||||
----
|
||||
|
||||
. Load the overlay and bridge filter modules.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sudo modprobe overlay
|
||||
sudo modprobe br_netfilter
|
||||
----
|
||||
|
||||
. Add required `sysctl` parameters and persist.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
# sysctl params required by setup, params persist across reboots
|
||||
sudo cat <<EOF | sudo tee /etc/sysctl.d/k8s.conf
|
||||
net.bridge.bridge-nf-call-iptables = 1
|
||||
net.bridge.bridge-nf-call-ip6tables = 1
|
||||
net.ipv4.ip_forward = 1
|
||||
EOF
|
||||
----
|
||||
|
||||
. Apply `sysctl` parameters without a reboot.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sudo sysctl --system
|
||||
----
|
||||
|
||||
. Verify `br_filter` and overlay modules are loaded.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
lsmod | grep br_netfilter
|
||||
lsmod | grep overlay
|
||||
----
|
||||
|
||||
. Verify that the `net.bridge.bridge-nf-call-iptables`, `net.bridge.bridge-nf-call-ip6tables`, and `net.ipv4.ip_forward` system variables are set to `1` in your sysctl configuration by running the following command:
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sysctl net.bridge.bridge-nf-call-iptables net.bridge.bridge-nf-call-ip6tables net.ipv4.ip_forward
|
||||
----
|
||||
|
||||
. Install a link:https://kubernetes.io/docs/setup/production-environment/container-runtimes/[container runtime].
|
||||
CRI-O is installed in this example.
|
||||
Containerd is also an option.
|
||||
Note: If using cri-o, verify that the major:minor version of cri-o is the same as the version of Kubernetes (installed below).
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sudo dnf install cri-o containernetworking-plugins
|
||||
----
|
||||
|
||||
. Install Kubernetes.
|
||||
In this example, all three Kubernetes applications (`kubectl`, `kubelet`, and `kubeadm`) are installed on this single node machine.
|
||||
Please see the notes above on recommended packages for control plane or worker nodes if the cluster will have both types of machines.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
# fedora 39 and earlier use:
|
||||
sudo dnf install kubernetes-client kubernetes-node kubernetes-kubeadm
|
||||
|
||||
#fedora 40 and later use:
|
||||
sudo dnf install kubernetes kubernetes-kubeadm kubernetes-client
|
||||
----
|
||||
|
||||
|
||||
. Start and enable cri-o.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sudo systemctl enable --now crio
|
||||
----
|
||||
|
||||
. Pull needed system container images for Kubernetes.
|
||||
This is strictly optional.
|
||||
The ```kubeadm init``` command below will pull images, if needed.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sudo kubeadm config images pull
|
||||
----
|
||||
|
||||
. Start and enable `kubelet`.
|
||||
Kubelet will be in a crash loop until the cluster is initialized in the next step.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sudo systemctl enable --now kubelet
|
||||
----
|
||||
|
||||
. Initialize the cluster.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
sudo kubeadm init --pod-network-cidr=10.244.0.0/16
|
||||
----
|
||||
|
||||
. kubeadm will generate output to the terminal tracking initialization steps.
|
||||
If successful, the output below is displayed.
|
||||
At this point there is a cluster running on this single machine.
|
||||
After kubeadm finishes you should see:
|
||||
+
|
||||
----
|
||||
Your Kubernetes control-plane has initialized successfully!
|
||||
|
||||
To start using your cluster, you need to run the following as a regular user:
|
||||
|
||||
mkdir -p $HOME/.kube
|
||||
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
|
||||
sudo chown $(id -u):$(id -g) $HOME/.kube/config
|
||||
|
||||
Alternatively, if you are the root user, you can run:
|
||||
|
||||
export KUBECONFIG=/etc/kubernetes/admin.conf
|
||||
----
|
||||
|
||||
. The steps listed above allow a non-root user to use `kubectl`, the Kubernetes command line tool.
|
||||
Run these commands now.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
mkdir -p $HOME/.kube
|
||||
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
|
||||
sudo chown $(id -u):$(id -g) $HOME/.kube/config
|
||||
----
|
||||
|
||||
. Allow the control plane machine to also run pods for applications.
|
||||
Otherwise more than one machine is needed in the cluster.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
kubectl taint nodes --all node-role.kubernetes.io/control-plane-
|
||||
----
|
||||
|
||||
. Install flannel into the cluster to provide cluster networking.
|
||||
There are many other networking solutions besides flannel.
|
||||
Flannel is straightforward and suitable for this guide.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
kubectl apply -f https://github.com/coreos/flannel/raw/master/Documentation/kube-flannel.yml
|
||||
----
|
||||
|
||||
. Display list of running pods in the cluster.
|
||||
All pods should display a status of Running.
|
||||
A status of CrashLoopBackOff may show up for the coredns pod.
|
||||
This happens commonly when installing Kubernetes on a virtual machine and the DNS service in the cluster may not select the proper network.
|
||||
Use your favorite internet search engine to find possible solutions.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
kubectl get pods --all-namespaces
|
||||
----
|
||||
|
||||
At this point there is a single machine in the cluster running the control plane and available for work as a node.
|
||||
|
||||
Upgrades to Kubernetes clusters requires care and planning.
|
||||
See link:https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/[Upgrading kubeadm clusters] for more information.
|
||||
|
||||
The xref:dnf.adoc#sect-using-dnf-plugin[DNF Versionlock plugin] is useful in blocking unplanned updates to Kubernetes rpms.
|
||||
Occasionally, the Kubernetes version in a Fedora release reaches end-of-life and a new version of Kubernetes is added to the repositories.
|
||||
Or, an upgrade to Fedora on a cluster machine will also result in a different version of Kubernetes.
|
||||
Once DNF Versionlock is installed, the following command will hold kubernetes rpms and the cri-o rpm at the 1.28 major:minor version but still allow patch updates to occur:
|
||||
[source,bash]
|
||||
----
|
||||
sudo dnf versionlock add kubernetes*-1.28.* cri-o-1.28.*
|
||||
----
|
||||
|
||||
[[sect-kubernetes-projects-in-copr]]
|
||||
== Kubernetes projects in COPR
|
||||
|
||||
There are Kubernetes projects in link:https://copr.fedorainfracloud.org/[COPR] that might be useful.
|
||||
|
||||
[[sect-versioned-kubernetes-rpms]]
|
||||
=== Versioned Kubernetes RPMS
|
||||
|
||||
The link:https://copr.fedorainfracloud.org/coprs/buckaroogeek/copr-k8s-versioned/[Versioned Kubernetes Packages] project is an experimental project exploring the use of versioned Kubernetes packages.
|
||||
A versioned package has a version number as part of the name such as `kubernetes1.28` or `kubernetes1.28-client`.
|
||||
The goal is to have multiple versions of Kubernetes available for a given Fedora release.
|
||||
This uncouples Fedora versions from Kubernetes versions allowing version upgrades to either Fedora or Kubernetes.
|
||||
A cluster manager can update the Fedora machines while maintaining the cluster version constant.
|
||||
Or the cluster manager can update Kubernetes while retaining the same Fedora release.
|
||||
All Kubernetes releases in this repository use the new package structure.
|
||||
|
||||
[[sect-kubernetes-1.26]]
|
||||
=== Kubernetes 1.26 RPMS
|
||||
The link:https://copr.fedorainfracloud.org/coprs/buckaroogeek/copr-k8s-1.26/[Kubernetes 1.26] project provides Kubernetes 1.26 rpms for all current Fedora releases that provide Go language 1.21 or newer.
|
||||
Kubernetes 1.26 is the default version available in Fedora 38.
|
||||
This project uses the legacy package structure.
|
||||
|
||||
[[sect-kubernetes-1.27]]
|
||||
=== Kubernetes 1.27 RPMS
|
||||
The link:https://copr.fedorainfracloud.org/coprs/buckaroogeek/copr-k8s-1.27/[Kubernetes 1.27] project provides Kubernetes 1.27 rpms for all current Fedora releases that provide Go language 1.21 or newer.
|
||||
Kubernetes 1.27 is the default version available in Fedora 39.
|
||||
This project uses the legacy package structure.
|
||||
|
||||
[[sect-kubernetes-1.28]]
|
||||
=== Kubernetes 1.28 RPMS
|
||||
The link:https://copr.fedorainfracloud.org/coprs/buckaroogeek/copr-k8s-1.28/[Kubernetes 1.28] project provides Kubernetes 1.28 rpms for all current Fedora releases that provide Go language 1.21 or newer.
|
||||
Kubernetes 1.28 is not otherwise available in official Fedora repositories.
|
||||
This project uses the legacy package structure.
|
||||
|
||||
[[sect-kubernetes-1.29]]
|
||||
=== Kubernetes 1.29 RPMS
|
||||
The link:https://copr.fedorainfracloud.org/coprs/buckaroogeek/copr-k8s-1.29/[Kubernetes 1.29] project provides Kubernetes 1.29 rpms in the new package structure.
|
||||
Kubernetes v1.29 requires Go language 1.21 or newer.
|
||||
Kubernetes 1.29 is the default version for Fedora 40.
|
||||
This project uses the new package structure.
|
||||
|
||||
[[sect-kubernetes-1.30]]
|
||||
=== Kubernetes 1.30 RPMS
|
||||
The link:https://copr.fedorainfracloud.org/coprs/buckaroogeek/copr-k8s-1.30/[Kubernetes 1.30] project provides Kubernetes 1.30 rpms in the new package structure.
|
||||
This is an alpha level release from the Kubernetes team.
|
||||
Kubernetes v1.30 requires Go language 1.22 or newer which is only available in Fedora 40 and 41 (rawhide).
|
||||
This project uses the new package structure.
|
||||
[references]
|
||||
== References
|
||||
|
||||
. https://kubernetes.io/
|
||||
. https://kubernetes.io/docs/home/
|
||||
. https://kubernetes.io/docs/concepts/overview/
|
||||
|
|
|
|||
Loading…
Reference in a new issue