Expected result after deploy? empty yaml-files?
Hi, just a bit curious as how the kubernetes part of the premix is supposed to work. after going through and enabling the services I'am interested in such as sonarr,radarr etc. I ran the "ansible-playbook -i hosts.blarg deploy.yml" and it created the files in my flux repo... but the "configmap-rook-ceph.yaml" and "default-values-rook-ceph.yaml" are completly empty. Is this per design and for me to edit, or should I expect another result?
The Cluster seems to be up and running, but some pods are not, and I think one of the reasons could be that i have no persistant storage working, since the rook-ceph has not been deployed, probably due to empty config-files?
2 Replies
mmm..that's not the expected result
what should happen is that you end up with workable helmrelease/configmaps pre-populated with the upstream defaults from the chart, which you can then adjust to your requirements..
Could it have something to do with permissions to the folders or files? My setting for the repo:
flux_repo_path: /home/enmi/Documents/fp-homeops and my user "enmi" is the owner of the folder. I got the following errors on probably all services, but i just ran deploy again, and it jumped to the next service.
And the premix is in /home/enmi/Documents/k8s/geek-cookbook-premix/ (Im using Documents here but it is actually "Dokument", since my ubuntu-desktop is localized for sweden)
Tried running this on linuxmint instead of ubuntu 23.10 seams to have worked better...