OK, I managed to improve lots of things in those setups and make the setup more reliable (even in case it takes really really long for everything to be up).
https://codeberg.org/johanneskastl/gitlab_on_k3s_vagrant_libvirt_ansible
Now with four branches, one for Gitlab installed via helm chart and one using the Gitlab Operator.
And each of them with and without a Gitlab Runner being installed into the cluster.
#GitLab #Kubernetes #k3s #devops #Ansible #vagrant #libvirt #hellyeah
I had time to update my old #Teleport #vagrant setup to work with the current @opensuse packages maintained by yours truly.
https://codeberg.org/johanneskastl/teleport_with_vagrant_libvirt
Also some roles were cleaned up, tested and are now fully compliant to #AnsibleLint...
Here you are: Vagrant-Setup with Ansible deploying k3s and GitLab inside k3s.
https://codeberg.org/johanneskastl/gitlab_on_k3s_vagrant_libvirt_ansible
https://github.com/johanneskastl/gitlab_on_k3s_vagrant_libvirt_ansible
Currently without the Runner, that comes next.
#GitLab #DevOps #k3s #kubernetes #Ansible #vagrant #hellyeah
@jwolynko When it comes to on-prem, GitLab still seems to be the preferred solution (GitHub enterprise seems to be deprecated, thank the universe for that). I personally am running Forgejo wherever possible.
But most of the customers I know do run some form of GitLab. And I wanted to make sure I had a working test setup, whenever I need one. Currently I wanted to do some testing for GitLab runners on Kubernetes.
The package based ones are pretty simple to setup (not talking about maintenance, of course).
https://codeberg.org/johanneskastl/gitlab_vagrant_libvirt_ansible
https://codeberg.org/johanneskastl/gitlab_and_runner_vagrant_libvirt_ansible
Here is a small Docker CLI plugin I did, that launches a Vagrant-managed VM using Parallels on macOS and sets up a Docker context for it. Useful if you want a lightweight, no-surprises alternative to Docker Desktop — works on Intel & ARM, with binfmt for cross-arch builds.
"docker vagrant up" and you're ready to go.
Ansible-pull и GitLab CI/CD: когда лучше тянуть, чем толкать
Ansible — мощный инструмент автоматизации, но его push-модель не всегда удобна. Когда требуется централизованный контроль большого числа серверов, могут возникнуть проблемы: 📌 Нестабильные сети → клиент может быть недоступен во время обновления. 📌 Сложности с NAT → серверы находятся в закрытых "серых" сетях. 📌 Перемещаемые устройства → подключаются к сети только время от времени. Разбираемся, как ansible-pull решает эти проблемы на стенде , а также настраиваем CI/CD для тестирования и совместной разработки Ansible-ролей
https://habr.com/ru/articles/890276/
#ansiblelint #ansible #ansible_playbook #vagrant #docker #dockercompose #dockerfile #gitlab #git #cicd
Uuuuuuuh, #OpenBao (the open source fork of #Hashicorp #Vault) just released version 2.2.0 and now includes the UI, that was missing so far.
The package for @opensuse was adapted, tested and worked out fine. Will soon be available in #Tumbleweed!
If you want to test this out, feel free to use this vagrant-libvirt setup of mine:
https://codeberg.org/johanneskastl/openbao_vagrant_libvirt_ansible
#openSUSE #secretsmanagement #opensource #hellyeah #vagrant #libvirt
A relire : Vagrant Manager, l'outil pour gérer vos machines Vagrant
https://blog.shevarezo.fr/post/2016/07/15/vagrant-manager-outil-gerer-machines-vagrant
Johannes Kastl
Frank Patz-Brockmann
Iain Cuthbertson
Habr
triF5
shevabam