|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Devops Exercises||58,358||a day ago||53||other||Python|
|Linux, Jenkins, AWS, SRE, Prometheus, Docker, Python, Ansible, Git, Kubernetes, Terraform, OpenStack, SQL, NoSQL, Azure, GCP, DNS, Elastic, Network, Virtualization. DevOps Interview Questions|
|90daysofdevops||23,911||5 days ago||1||May 09, 2022||8||other||Shell|
|I am using this repository to document my journey learning about DevOps. I began this process on January 1, 2022, and plan to continue until March 31. I will be dedicating one hour each day, including weekends, to gaining a foundational understanding of the various aspects of DevOps. This will be a 90-day intensive study period. 2022 & 2023 inc.|
|Kubespray||14,502||2 days ago||217||apache-2.0||Jinja|
|Deploy a Production Ready Kubernetes Cluster|
|Kubeasz||9,478||a month ago||11||April 25, 2021||11||apache-2.0||Jinja|
|Ansible For Devops||7,491||10 days ago||92||mit||Python|
|Ansible for DevOps examples.|
|Homelab||7,162||19 days ago||17||gpl-3.0||Go|
|Modern self-hosting framework, fully automated from empty disk to operating services with a single command.|
|Devops Guide||7,132||3 days ago||8||mit||HTML|
|DevOps Guide - Development to Production all configurations with basic notes to debug efficiently.|
|Kubeoperator||4,802||a month ago||48||apache-2.0||Go|
|KubeOperator 是一个开源的轻量级 Kubernetes 发行版，专注于帮助企业规划、部署和运营生产级别的 K8s 集群。|
|Opendevops||3,367||7 months ago||67||gpl-3.0||Python|
|Boilerplates||2,864||8 days ago||15||mit||HCL|
|This is my personal template collection. Here you'll find templates, and configurations for various tools, and technologies.|
community.kubernetes collection is being renamed to
kubernetes.core. As of version 2.0.0, the collection has been replaced by deprecated redirects for all content to
kubernetes.core. If you are using FQCNs starting with
community.kubernetes, please update them to
This repo hosts the
kubernetes.core) Ansible Collection.
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.
Before using the Kubernetes collection, you need to install it with the Ansible Galaxy CLI:
ansible-galaxy collection install community.kubernetes
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: community.kubernetes version: 2.0.1
Content in this collection requires the OpenShift Python client to interact with Kubernetes' APIs. You can install it with:
pip3 install openshift
It's preferable to use content in this collection using their Fully Qualified Collection Namespace (FQCN), for example
--- - hosts: localhost gather_facts: false connection: local tasks: - name: Ensure the myapp Namespace exists. community.kubernetes.k8s: api_version: v1 kind: Namespace name: myapp state: present - name: Ensure the myapp Service exists in the myapp Namespace. community.kubernetes.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. community.kubernetes.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: - community.kubernetes 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.
If you want to develop new content for this collection or improve what's already here, the easiest way to work on the collection is to clone it into one of the configured
COLLECTIONS_PATHS, and work on it there.
tests directory contains configuration for running sanity and integration tests using
You can run the collection's test suites with the commands:
make test-sanity make test-integration
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 setup a local cluster using KinD and run Molecule:
kind create cluster make test-molecule
Releases are automatically built and pushed to Ansible Galaxy for any new tag. Before tagging a release, make sure to do the following:
kubernetes.corecollection (see following section).
After the version is published, verify it exists on the Kubernetes Collection Galaxy page.
Until the contents of repository are moved into a new
kubernetes.core repository on GitHub, this repository is the source of both the
community.kubernetes repositories on Ansible Galaxy.
To publish the
kubernetes.core collection on Ansible Galaxy, do the following:
make downstream-release(on macOS, add
LC_ALL=Cbefore the command).
The process for uploading a supported release to Automation Hub is documented separately.
GNU General Public License v3.0 or later
See LICENCE to see the full text.