Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Automated Ansible Setup #317

Merged
merged 46 commits into from Feb 7, 2023
Merged

Automated Ansible Setup #317

merged 46 commits into from Feb 7, 2023

Conversation

CommanderStorm
Copy link
Member

@CommanderStorm CommanderStorm commented Nov 28, 2022 •
edited

This PR provides the setup script for automatically setting up our future HA cluster (currently our deployment is really not in this ballpark. This would be a big improvement.)
It is currently very WIP.

Current Roadblock:
ZIT is sitting on their hands for “important reasons”.
We cannot switch to a quicker provider for

  • “We cannot help a central service, as our Profs would not allow this”~ Rechnerbetriebsgruppe or
  • “Our Vereinszweck sadly does not allow this”~ StuStaNet or
  • “We won't offer this”~ Compref

This will mostly just go through a Docs-review.

@CommanderStorm CommanderStorm self-assigned this Nov 28, 2022
@CommanderStorm CommanderStorm added the deployment Related to the the deployment-infrastructure label Dec 9, 2022
This was referenced Dec 9, 2022
Merged
Merged
Closed
@CommanderStorm CommanderStorm marked this pull request as ready for review January 17, 2023 12:43
@CommanderStorm
Copy link
Member Author

@octycs from this Review I would like to get a OK, if the docs would be clear to you

octycs
octycs reviewed Feb 6, 2023
View reviewed changes
Copy link
Contributor

@octycs octycs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are some places where subdomains of the old domain (nav.tum.sexy) are still used. Is that correct?

deployment/ansible/roles/common/tasks/git.yml Outdated Show resolved Hide resolved
deployment/ansible/roles/k8s/tasks/components/kuma.yml Show resolved Hide resolved
deployment/ansible/roles/k8s/tasks/components/kuma.yml Show resolved Hide resolved
deployment/ansible/roles/k8s/tasks/components/kuma.yml Show resolved Hide resolved
deployment/ansible/roles/k8s/tasks/k3s_setup.yml Show resolved Hide resolved
deployment/ansible/roles/k8s/templates/traefik.yaml Show resolved Hide resolved
deployment/ansible/roles/common/tasks/unatended_upgrades.yml Outdated Show resolved Hide resolved
@CommanderStorm
inital untested configuration
573852e
@CommanderStorm
updated the ip adresses to the real ones
56796c9
@CommanderStorm
removed duplicate tldr
ea58b26
@CommanderStorm
added the hostname
fb2a017
@CommanderStorm
added additional context to the inventory file
5874111
@CommanderStorm
fixed nano pointing to the wrong path
4c94d8a
@CommanderStorm
refactored the site.yml for better run performance
ffc8870
@CommanderStorm
slightly refactored the ssh config
b907fe5
@CommanderStorm
fixed typo in sshd config
459b6f4
@CommanderStorm
added the correct ansible_port to the inventory
82176e6
@CommanderStorm
Migrated UFW configuration to the SSH
50c8788
@CommanderStorm
fixed hostnames not being configurable in the LRZ
86fa8d5
@CommanderStorm
merged the k3s setup into the leader
4055bb2
@CommanderStorm
added support vor ipv6 traffic
9a48905
@CommanderStorm
fixed the hostname having a weird prefix
b1f060e
@CommanderStorm
removed unatended_upgrades from the installation script, as this is d…
0e22efd 
…one by the LRZ
@CommanderStorm
reconfigured k3s for embedded etcd
b449399
@CommanderStorm
merged leader and leaders blocks
dbdaa03
@CommanderStorm
added wait_for blocks to the k3s installation
36c1cb3
@CommanderStorm
refactored the way ips are extracted from the inventory
25b19ca
@CommanderStorm
refactored
49364fe
@CommanderStorm
fixed the fail2ban handler
d5bb66e
@CommanderStorm
added ipv4 to the vpn config
6b51839
@CommanderStorm
added uptime-kuma as a uptime monitor
4a21fbb
@CommanderStorm
limited ssh to ipv6
dab02c2
@CommanderStorm
removed character, which should not have been there
b9d4da1
@CommanderStorm
fixed typo in K3S_NODE_NAME configuration
6f1dfc7
@CommanderStorm
made sure that reboot notifications are not delivered
5febd44
@CommanderStorm
improved the Readme
ac82389
@CommanderStorm
added the correct loadbalancer_ip
34e180a
@CommanderStorm
refactored how the k3s setup is layed out
aa29d04
@CommanderStorm
fixed k3s not being to access the k8s variables
f207790
@CommanderStorm
move ufw configuration from the ufw block to the kuberentes setup
c6dd9fb
@CommanderStorm
fixed some ssh entries not being removed from UFW
7f1685c
@CommanderStorm
fixed bugs in the k3s setup
0d1fe7e
@CommanderStorm
moved the ufw config of k3s to a different file
4bb3cda
@CommanderStorm
fixed the cluster not being able to communicate with each other
13c8ec2
@CommanderStorm
separated the individual nodes kubernetes installation to get around …
15a693b 
…a weird race condition
@CommanderStorm
added commented out k3s-uninstall script
f97c6b9
@CommanderStorm
moved the templates over from frank.elsinga.de to nav.tum.sexy
57a6703
@CommanderStorm
inital installation of k8s components
5992e1d
@CommanderStorm
fixed the order in which the components are installed
b668fd4
@CommanderStorm
Allow the LB to check if k8s is online
3ba46b5
@octycs octycs merged commit f848bd2 into main Feb 7, 2023
@octycs octycs deleted the ansible branch February 7, 2023 22:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@octycs octycs Awaiting requested review from octycs

Assignees

@CommanderStorm CommanderStorm

Labels
deployment Related to the the deployment-infrastructure
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@CommanderStorm @octycs