uyuni
uyuni copied to clipboard
uyuni server: container image/container build
Question
Hello, we would like to migrate the uyuni server from a VM to a container image deployed in Rancher cluster So: question1: if this is the official image registry.opensuse.org/home/deneb_alpha/branches/systemsmanagement/uyuni/master_510bump/containers/uyuni/server:2024.09 If I create a deployment, what are the associated volumes for: /etc/rhn and /var/spacewalk question2: we'd like to use the container with an external postgresDB question3: is this the official Docker file? https://github.com/uyuni-project/uyuni/blob/master/containers/server-image/Dockerfile if so, why is missing Expose ports ?
- that is not the official image. The official one is: egistry.opensuse.org/uyuni/server:latest You also have a helmchart at registry.opensuse.org/uyuni/server-helm:latest
- You can try, but that is not supported yet. It's on our roadmap and should be one of the next steps
- we are exposing the ports in the helmchart
Did you try the tool mgradm? It can deploy uyuni directly to your kubernetes cluster and setup everything for you.
that is not the official image. The official one is: egistry.opensuse.org/uyuni/server:latest You also have a helmchart at registry.opensuse.org/uyuni/server-helm:latest
You can try, but that is not supported yet. It's on our roadmap and should be one of the next steps
we are exposing the ports in the helmchart
Did you try the tool mgradm? It can deploy uyuni directly to your kubernetes cluster and setup everything for you.
I'll have a look over the weekend. Thanks :)
@rjmateus ,
So,
Rancher 2.9.0/RKE 1.28.13
helm install uyuni-server oci://registry.opensuse.org/uyuni/server-helm -n uyuni-server --set ingress=nginx --set fqdn=uyuni-itm8.apps.mydomain.dk
root@mgmtrke2m01:~# kubectl get po -n uyuni-server
NAME READY STATUS RESTARTS AGE
uyuni-6bf577f497-blbgs 1/1 Running 4 (73s ago) 25m
kubectl logs -f uyuni-6bf577f497-blbgs -n uyuni-server
Defaulted container "uyuni" out of: uyuni, init-etc-tls (init), init-var-cobbler (init), init-var-salt (init), init-var-pgsql (init), init-var-cache (init), init-var-log (init), init-srv-salt (init), init-srv-www (init), init-srv-tftpboot (init), init-srv-formulametadata (init), init-srv-pillar (init), init-srv-susemanager (init), init-srv-spacewalk (init), init-root (init), init-etc-apache2 (init), init-etc-rhn (init), init-etc-systemd-multi (init), init-etc-systemd-sockets (init), init-etc-salt (init), init-etc-tomcat (init), init-etc-cobbler (init), init-etc-sysconfig (init), init-etc-postfix (init), init-etc-sssd (init)
As you can see , pod is running but all the containers are in init state....