issues
search
techno-tim
/
k3s-ansible
The easiest way to bootstrap a self-hosted High Availability Kubernetes cluster. A fully automated HA k3s etcd install with kube-vip, MetalLB, and more. Build. Destroy. Repeat.
https://technotim.live/posts/k3s-etcd-ansible/
Apache License 2.0
2.41k
stars
1.05k
forks
source link
fix(ci): only run CI for PRs
#430
Closed
timothystewart6
closed
9 months ago
timothystewart6
commented
9 months ago
Proposed Changes
this closes #429
there's no point of running CI after a merge since we don't deploy
this causes builds to queue up for no reason
this should disable it
Checklist
[ ] Tested locally
[ ] Ran
site.yml
playbook
[ ] Ran
reset.yml
playbook
[x] Did not add any unnecessary changes
[x] Ran pre-commit install at least once before committing
[x] 🚀
Proposed Changes
Checklist
site.yml
playbookreset.yml
playbook