dreamythedev/ansible_role_cri_o

An ansible role to install cri-o CRI on your Kubernetes nodes. Currently, only Debian10 nodes are supported by this project.

Welcome to role_cri-o 👋

A role to install CRI-O on Debian

🏠 Homepage

Usage

You can use this role in your Ansible playbook like this :

- name: "Install CRI-O on Kubernetes nodes"
  hosts: kubernetes-nodes
  roles: 
    - ansible_role_cri-o

You can install a specific version of CRI-O by adding the cri_o_kubernetes_version in your hostvars or groupvars :

cri_o_kubernetes_version: 1.20

Author

👤 Matthieu Chevreux

• Twitter: @404MomNotFound
• Github: @DreamyProtect
• LinkedIn: @Matthieu Chevreux

🤝 Contributing

Contributions, issues and feature requests are welcome!
Feel free to check issues page.

Show your support

Give a ⭐️ if this project helped you!

📝 License

Copyright © 2020 Matthieu Chevreux.
This project is BSD 3--Clause "New" or "Revised" License licensed.

---

This README was generated with ❤️ by readme-md-generator

ansible_role_cri_o's Issues

CRI-O is not running by default

At the end of the role, CRI-O is not running as default, this is a problem when using kubeadm to bootstrap a cluster as it is not able to recognize it.

The automated release is failing 🚨

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Missing package.json file.

A package.json file at the root of your project is required to release on npm.

Please follow the npm guideline to create a valid package.json file.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀