dschier
/
ansible-k3s
1
0
Fork 0
Code Issues Pull Requests Releases Activity
Just a draft
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2 Commits
1 Branch
0 Tags
30 KiB
HTML 100%
 
main
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'main'
${ noResults }
Go to file
dschier 31d7ff5983 Cluster setup and client config 
The cluster setup should work reliable now and servers will join after etcd is up.
Furthermore, the client configuration will be added to the output directory now.
Other files have seen improvements, too. But it is as it is, in heavy development :)
 		2 years ago
output Cluster setup and client config 2 years ago
templates Cluster setup and client config 2 years ago
.gitignore Cluster setup and client config 2 years ago
README.md Cluster setup and client config 2 years ago
Vagrantfile Cluster setup and client config 2 years ago
ansible.cfg Cluster setup and client config 2 years ago
k3s_cluster.yml Cluster setup and client config 2 years ago
k3s_container.yml Cluster setup and client config 2 years ago
kubeconfig Cluster setup and client config 2 years ago

README.md

Ansible for k3s deployment

An Ansible repository to deploy a k3s kubernetes cluster.

Motivation

Having different shapres of kubernetes on hand is somewhat mandatory for typical DevOps and development tasks.

Description

This repository allows to build different types of k3s kubernetes setups locally and on specified machines.

Features

This section describes the features of the repository.

Cluster location

You can set up the cluster, wherever you want. You just need to configure the inventory accordingly and you are good to go.

Vagrant

TBD

Your own machines

TBD

Cluster Size

You can build different clusters by changing the amount of servers and agents. Some typical scenarios, you may be interested in, are described below.

Single instance

A single kubernetes instance is useful for local development and testing. It is similar to microk8s or minikube setups.

HA Setup

You can setup a high available kubernetes cluster with 3 servers. This is useful to develop kubernetes services, ingress, HA testing and loadbalancer functionality.

Single server, multiple agents

If you want to test pod affinity, horizontal auto scaling or just want to use multiple agents, you can define one server and multiple agents.

HA Setup with multiple agents

Define at minimum 3 servers and 1 agent to get a high available setup. This is very close to a production cluster and can be useful to test production setups.

Container deployments

The repository will offer options to configure some additional scenarios.

TBD

TBD