https://github.com/yadvi12/k8s-ansible-playbook
K8s multinode cluster setup on AWS RHEL8 Instance using Ansible Playbook.
https://github.com/yadvi12/k8s-ansible-playbook
ansible ansible-playbook aws k8s kubeadm kubernetes-cluster
Last synced: 3 months ago
JSON representation
K8s multinode cluster setup on AWS RHEL8 Instance using Ansible Playbook.
- Host: GitHub
- URL: https://github.com/yadvi12/k8s-ansible-playbook
- Owner: yadvi12
- Created: 2021-02-04T06:15:25.000Z (over 4 years ago)
- Default Branch: main
- Last Pushed: 2021-02-11T08:15:16.000Z (over 4 years ago)
- Last Synced: 2025-06-30T22:02:12.153Z (3 months ago)
- Topics: ansible, ansible-playbook, aws, k8s, kubeadm, kubernetes-cluster
- Language: Python
- Homepage:
- Size: 71.3 KB
- Stars: 11
- Watchers: 2
- Forks: 5
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
Awesome Lists containing this project
README
# Kubernetes Ansible Playbook
Build a Kubernetes cluster using Ansible with kubeadm. The goal is to easily install a Kubernetes cluster on machines running RHEL8 and centos on top of AWS public cloud.
System requirements:
- Deployment environment must have Ansible 2.9.0+
- Master and nodes must have passwordless SSH access
## Usage:
- Install ansible 2.9.0+ in your system.
- Clone this repository in any location you want.
- Create a folder "/etc/ansible" in your system.
- Copy the "ansible.cfg" file in /etc/ansible location.
- Open the ansible.cfg file and change the required parameters.
- Cd to the location of cloned repository.
- Export the aws key and value pair using
```sh
EXPORT AWS_ACCESS_KEY_ID="7***********9A"
EXPORT AWS_SECRET_ACCESS_KEY="9***************7S"
EXPORT AWS_REGION="ap-south-1"
```
- Run the playbook using "ansible-playbook setup.yml" command.
## Verification:
The playbook will download /etc/kubernetes/admin.conf file to $HOME/admin.conf.
- Login to the master node.
- Verify cluster is fully running using kubectl:
```sh
kubectl get nodes
kubectl get pods
kubectl get pods -n "kube-system"
```
## Get Involved:
* Read [Community Guidelines]() for all
kinds of ways to contribute to and interact with the project,
including how to submit bug reports and
code to repository.
* Submit a proposed code update through a pull request to the ``master`` branch.
* Talk to the owner before making larger changes
to avoid duplicate efforts. This not only helps everyone
know what is going on, it also helps save time and effort if we decide
some changes are needed.
## License:
The Project is released under the terms of the MIT License.