Jinja good first issues

This issue proposes adding support for Helm version 4.x. The motivation is to leverage new features and security enhancements available in this major release, as indicated by the provided Helm documentation link.

This issue proposes updating the Continuous Integration (CI) pipeline to include Fedora 44 and deprecate Fedora 42. The work involves adding a new Fedora 44 image, migrating existing tests, updating CI configurations, and refreshing documentation to reflect the supported Fedora releases.

This issue requests running the Kubernetes conformance test for version 1.35 using Kubespray v2.31.0. The goal is to submit the test results to the `cncf/k8s-conformance` repository to ensure Kubespray maintains CNCF Certified Kubernetes coverage for this release.

The webzfs package uses wildcards in its sudoers configuration, which is incompatible with sudo-rs, the default sudo implementation in Ubuntu 26.04. This prevents webzfs from functioning correctly, requiring users to either revert to the older sudo.ws or find a workaround. The issue suggests that webzfs should either adapt its sudoers configuration or this incompatibility should be documented.

The user is requesting a NixOS package for the 'webzfs' project. Currently, no such package exists in the NixOS unstable channel. The user expresses interest in creating it themselves but also welcomes contributions from others.

This feature request aims to automate the publishing of collection artifacts for releases. The goal is to integrate this process into existing CI/CD pipelines, with potential destinations including Ansible Galaxy or GitHub Releases. Initial implementation will focus on automation, with artifact signing as a future enhancement.

This issue requests the addition of support for openSUSE Leap 16.0 to the KubeVirt project. This involves updating the image builder, adding test cases, adjusting OS-specific logic, updating documentation, and removing outdated Leap 15.x entries. The motivation is to align with the current supported openSUSE release as Leap 15.6 has reached its end of life.

The README file for the `activemq_uninstall` role incorrectly formats example playbooks, lacking YAML syntax. This issue requires reviewing all related README files to ensure consistent YAML formatting for example playbooks, similar to the `wildfly_driver` role.

The Docker image for the 'codex' project has been moved to a new registry (ghcr.io/ajslater/codex). This issue requires testing the existing role with this new image and updating any necessary configurations to reflect the change.

Kubespray generates etcd certificates with inconsistent file permissions and ownership on the initial control-plane node compared to subsequent control-plane nodes. This discrepancy can lead to operational issues, such as backup failures, due to restricted read access on the first node.

This issue requests the addition of official support for openSUSE MicroOS as a target operating system within Kubespray. MicroOS is a minimal, transactional OS ideal for container workloads, and its inclusion would expand Kubespray's compatibility.

This issue requests an update to the default Flannel version used by Kubespray from v0.28.4 to v0.28.9. This bump is necessary to incorporate security fixes for two CVEs, add readiness and liveness probes for improved health monitoring, and enhance networking reliability.

This issue proposes upgrading the default `nerdctl` version used by Kubespray from v2.3.0 to v2.3.5. The upgrade is necessary to incorporate bug fixes and new features, such as Compose health-check support, while maintaining compatibility with existing containerd versions. The proposed changes involve updating checksums, ensuring the correct version is resolved, and propagating Ansible variables.

This issue proposes upgrading the default CRI-O version used by Kubespray from v1.36.3 to v1.36.4. The upgrade is necessary to incorporate bug fixes, including a critical nil pointer dereference, and to leverage new performance-enhancing features. The process involves updating checksums, ensuring the correct version is selected, and propagating these changes through the Ansible variables.

This issue proposes updating the molecule tests from CentOS 8 to Rocky Linux 9, as CentOS 8 is no longer maintained. While significant progress has been made on a `rocky9` branch, the 389DS service fails to start during GitHub Actions CI runs, indicating a configuration or compatibility issue with the new OS.

The user is experiencing instability and routing errors on Edgerouter X devices after upgrading to OpenWrt 25.12. Specifically, the `olsrd` service is repeatedly failing to delete routes, leading to a spammed log and unstable network connections. This issue has been observed on two different locations configured with the `ubnt_edgerouter-x` device.

This issue requests a fix for an "Idempotence test" specifically on Debian systems. The goal is to ensure that running the test multiple times has the same effect as running it once, indicating proper handling of repeated operations.

The issue describes the significant difficulty in developing across multiple related GitHub repositories due to how dependencies are managed. Changes require manual editing of `pyproject.toml` files in several locations to point to local development versions, leading to errors and a cumbersome workflow.

This issue requests the addition of a new product, 'PILGRIM MATE Bier', to the system. The linked URL provides product details, and a warning about alcohol content is noted. This likely involves updating a product catalog or database with new item information.

This issue proposes the addition of a new feature or product called "Spar Mate". The title and labels "help wanted" and "missing product" suggest that this is a new development effort that the project is seeking community contributions for. The attached image likely provides more context on what "Spar Mate" entails.

This issue proposes adding 'Volg Mate' to the project, with a link to a Mastodon post for more details. The 'help wanted' and 'missing product' labels suggest it's a feature request for a new integration or component.

Cilium agents fail to start with CrashLoopBackOff when `cilium_tunnel_mode` is set to `disabled` and `cilium_routing_mode` to `native` in Kubespray v2.30.0. The Helm chart incorrectly attempts to initialize tunnel protocols despite the user's explicit configuration, leading to a conflict.

This issue proposes refactoring Kubespray's apiserver loadbalancer configuration variables. The goal is to consolidate multiple inconsistent and redundant variables into two clear, well-defined variables for both external and internal API access. This change aims to improve clarity and reduce confusion in the codebase and documentation.