* fix(helm): skip OCI registry progress messages on stdout
Helm 4.2.1 moved the registry client's progress messages from stderr to
stdout (helm/helm#32056), so on an OCI reference they now precede the real
output. helm parses the stdout of `helm show chart` and helm_template
returns the stdout of `helm template`, and neither can detect this from the
return code because both commands exit 0.
Helm rewrites '+' to '_' in OCI tags, which makes it also print a free-text
explanation. That is not valid YAML, so a chart version carrying semver
build metadata failed outright. Without the '+' the messages parse as a
mapping instead, silently adding Pulled/Digest keys to the chart info.
Match helm's message verbatim rather than seeking the start of the real
output: the payload has three shapes and can be empty, whereas the messages
are always at the front and byte-identical. A reworded message then fails
loudly instead of consuming a line of real output.
Fixes: #1222
* test(helm): cover OCI charts whose version has build metadata
Pushes a chart versioned 1.0.0+build.1 to the local registry and asserts
that helm installs it idempotently with the version reported verbatim, and
that helm_template returns only rendered manifests. A second version without
build metadata covers the case where the registry messages parse as YAML.
Pinned to Helm 4.2.4: the target is only meaningful on >= 4.2.1, which is
where the messages moved to stdout. The rest of the helm matrix tops out at
v4.0.0, which is why this went unnoticed.
Verified to fail on the parent commit and pass on the fix.
* test(helm): drop Go template from chart fixture
The yamllint sanity test parses chart templates with libyaml, where
`{{ default "test" .Values.myValue }}` is an unhashable mapping key. The
existing chart fixtures carry a yamllint!skip entry in every
tests/sanity/ignore-*.txt for exactly this, but the target never renders
the chart with values, so the template served no purpose. Making the
fixture plain YAML keeps the ignore lists from growing.
* test(ci): empty commit to re-trigger CI
(cherry picked from commit c098ecc8c8)
Co-authored-by: Yuriy Novostavskiy <yuriy@novostavskiy.kyiv.ua>
Kubernetes Collection for Ansible
This repository hosts the kubernetes.core (formerly known as community.kubernetes) Ansible Collection.
Description
The collection includes a variety of Ansible content to help automate the management of applications in Kubernetes and OpenShift clusters, as well as the provisioning and maintenance of clusters themselves.
Included Content
Click on the name of a plugin or module to view that content's documentation:
Connection plugins
| Name | Description |
|---|---|
| kubernetes.core.kubectl | Execute tasks in pods running on Kubernetes. |
K8s filter plugins
| Name | Description |
|---|---|
| kubernetes.core.k8s_config_resource_name | Generate resource name for the given resource of type ConfigMap, Secret |
Lookup plugins
| Name | Description |
|---|---|
| kubernetes.core.k8s | Query the K8s API |
| kubernetes.core.kustomize | Build a set of kubernetes resources using a 'kustomization.yaml' file. |
Modules
| Name | Description |
|---|---|
| kubernetes.core.helm | Manages Kubernetes packages with the Helm package manager |
| kubernetes.core.helm_info | Get information from Helm package deployed inside the cluster |
| kubernetes.core.helm_plugin | Manage Helm plugins |
| kubernetes.core.helm_plugin_info | Gather information about Helm plugins |
| kubernetes.core.helm_pull | download a chart from a repository and (optionally) unpack it in local directory. |
| kubernetes.core.helm_registry_auth | Helm registry authentication module |
| kubernetes.core.helm_repository | Manage Helm repositories. |
| kubernetes.core.helm_template | Render chart templates |
| kubernetes.core.k8s | Manage Kubernetes (K8s) objects |
| kubernetes.core.k8s_cluster_info | Describe Kubernetes (K8s) cluster, APIs available and their respective versions |
| kubernetes.core.k8s_cp | Copy files and directories to and from pod. |
| kubernetes.core.k8s_drain | Drain, Cordon, or Uncordon node in k8s cluster |
| kubernetes.core.k8s_exec | Execute command in Pod |
| kubernetes.core.k8s_info | Describe Kubernetes (K8s) objects |
| kubernetes.core.k8s_json_patch | Apply JSON patch operations to existing objects |
| kubernetes.core.k8s_log | Fetch logs from Kubernetes resources |
| kubernetes.core.k8s_rollback | Rollback Kubernetes (K8S) Deployments and DaemonSets |
| kubernetes.core.k8s_scale | Set a new size for a Deployment, ReplicaSet, Replication Controller, or Job. |
| kubernetes.core.k8s_service | Manage Services on Kubernetes |
| kubernetes.core.k8s_taint | Taint a node in a Kubernetes/OpenShift cluster |
| kubernetes.core.kubeconfig | Generate, update, and optionally write Kubernetes kubeconfig files |
Requirements
Ansible version compatibility
This collection has been tested against the following Ansible versions: >=2.16.0.
Plugins and modules within a collection may be tested with only specific Ansible versions. A collection may contain metadata that identifies these versions. PEP440 is the schema used to describe the versions of Ansible.
Helm Version Compatibility
This collection supports Helm v3.x and newer. Please note that specific modules or certain parameters may have additional version requirements.
Python Support
- Collection supports 3.9+
Note: Python2 is deprecated from 1st January 2020. Please switch to Python3.
Kubernetes Version Support
This collection supports Kubernetes versions >= 1.24.
Installation
Before using the Kubernetes collection, you need to install it with the Ansible Galaxy CLI:
ansible-galaxy collection install kubernetes.core
You can also include it in a requirements.yml file and install it via ansible-galaxy collection install -r requirements.yml, using the format:
---
collections:
- name: kubernetes.core
version: 6.5.0
Installing the Kubernetes Python Library
Content in this collection requires the Kubernetes Python client to interact with Kubernetes' APIs. You can install it with:
pip3 install kubernetes
Use Cases
It's preferable to use content in this collection using their Fully Qualified Collection Namespace (FQCN), for example kubernetes.core.k8s_info:
---
- hosts: localhost
gather_facts: false
connection: local
tasks:
- name: Ensure the myapp Namespace exists.
kubernetes.core.k8s:
api_version: v1
kind: Namespace
name: myapp
state: present
- name: Ensure the myapp Service exists in the myapp Namespace.
kubernetes.core.k8s:
state: present
definition:
apiVersion: v1
kind: Service
metadata:
name: myapp
namespace: myapp
spec:
type: LoadBalancer
ports:
- port: 8080
targetPort: 8080
selector:
app: myapp
- name: Get a list of all Services in the myapp namespace.
kubernetes.core.k8s_info:
kind: Service
namespace: myapp
register: myapp_services
- name: Display number of Services in the myapp namespace.
debug:
var: myapp_services.resources | count
If upgrading older playbooks which were built prior to Ansible 2.10 and this collection's existence, you can also define collections in your play and refer to this collection's modules as you did in Ansible 2.9 and below, as in this example:
---
- hosts: localhost
gather_facts: false
connection: local
collections:
- kubernetes.core
tasks:
- name: Ensure the myapp Namespace exists.
k8s:
api_version: v1
kind: Namespace
name: myapp
state: present
For documentation on how to use individual modules and other content included in this collection, please see the links in the 'Included content' section earlier in this README.
Ansible Turbo Mode Tech Preview
Note: Ansible Turbo mode is supported only with
ansible-coreversions lower than 2.19. Starting fromansible-core2.19, thecloud.commoncollection is no longer supported, and therefore Ansible Turbo mode is also not supported inkubernetes.core. IfENABLE_TURBO_MODEis set to1(or any truthy value) withansible-core >= 2.19.0, it may lead to fails.
The kubernetes.core collection supports Ansible Turbo mode as a tech preview via the cloud.common collection (requires ansible-core < 2.19). By default, this feature is disabled. To enable Turbo mode for modules, set the environment variable ENABLE_TURBO_MODE=1 on the managed node. For example:
---
- hosts: remote
environment:
ENABLE_TURBO_MODE: 1
tasks:
...
To enable Turbo mode for k8s lookup plugin, set the environment variable ENABLE_TURBO_MODE=1 on the managed node. This is not working when
defined in the playbook using environment keyword as above, you must set it using export ENABLE_TURBO_MODE=1.
Please read more about Ansible Turbo mode - here.
Testing
Testing with ansible-test
The tests directory contains configuration for running sanity and integration tests using ansible-test.
You can run the collection's test suites with the commands:
make test-sanity
make test-integration
make test-unit
Testing with molecule
There are also integration tests in the molecule directory which are meant to be run against a local Kubernetes cluster, e.g. using KinD or Minikube. To set up a local cluster using KinD and run Molecule:
kind create cluster
make test-molecule
Contributing to this Collection
If you want to develop new content for this collection or improve what is already here, clone the Git repository into one of the configured COLLECTIONS_PATHS and work on it there.
See Contributing to kubernetes.core.
Join the Ansible community:
The Ansible Bullhorn newsletter announces releases and important changes. For more information, see the Ansible communication guide.
Code of Conduct
This project follows the Ansible Code of Conduct. If you encounter abusive behavior, see the policy violations section for how to raise a complaint.
Support
As Red Hat Ansible Certified Content, this collection is entitled to support through the Ansible Automation Platform (AAP) using the Create issue button on the top right corner. If a support case cannot be opened with Red Hat and the collection has been obtained either from Galaxy or GitHub, there may be community help available on the Ansible Forum.
Note: The
stable-4branch (all4.x.yreleases) is no longer supported. No backports or releases are performed onstable-4.
We announce releases and important changes through Ansible's The Bullhorn newsletter. Subscribe via this link.
We take part in the global quarterly Ansible Contributor Summit. Track The Bullhorn and join when announced.
For the latest supported versions, see Release Notes and Roadmap.
Report bugs, request features, or ask questions by opening an issue in the GitHub repository.
Release Notes and Roadmap
Releases are automatically built and pushed to Ansible Galaxy for any new tag. Before tagging a release, make sure to do the following:
- Update the version in the following places:
- The
versioningalaxy.yml - This README's
requirements.ymlexample - The
VERSIONinMakefile
- The
- Update the CHANGELOG:
- Make sure you have
antsibull-changeloginstalled. - Make sure there are fragments for all known changes in
changelogs/fragments. - Run
antsibull-changelog release.
- Make sure you have
- Commit the changes and create a PR with the changes. Wait for tests to pass, then merge it once they have.
- Tag the version in Git and push to GitHub.
After the version is published, verify it exists on the Kubernetes Collection Galaxy page.
The process for uploading a supported release to Automation Hub is documented separately.
Related Information
- Using Ansible collections
- Ansible communication guide
- Continuous integration (CI) overview
- SonarCloud integration
- Ansible Turbo mode (tech preview)
Code of conduct
We follow the Ansible Code of Conduct in all our interactions within this project.
If you encounter abusive behavior, please refer to the policy violations section of the Code for information on how to raise a complaint.
License Information
GNU General Public License v3.0 or later
See LICENSE to see the full text.