You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
K3s is the recommended way to run diracx for installation without an existing kubernetes like cluster (k8s, openshift, magnum, etc). However, the problem will be to expose that cluster to outside. That involves DNS/routing and also certificate handling.
For the DNS aspect, the commonly found solution involves metallb and external_dns
For certificates handling, I need to investigate. cert-manager does not allow static certificates.
The text was updated successfully, but these errors were encountered:
Hi @bertrandrigaud , me and @atsareg are effectively trying to run the diracx chart on bare VMs today, using 3 VMs (Alma9). The cluster will need to be exposed to the outside, and we are running into the issues described above. For the moment (as a poor-man-solution) we moved to NodePort for MySQL and OpenSearch: #114 . We will also assign a certificate to each VM. This denies some of the flexibility that we could have from the system, so improvements in this respect would be welcome. Did you have chance to investigate the possible solutions mentioned above?
K3s is the recommended way to run
diracx
for installation without an existing kubernetes like cluster (k8s, openshift, magnum, etc). However, the problem will be to expose that cluster to outside. That involves DNS/routing and also certificate handling.For the DNS aspect, the commonly found solution involves metallb and external_dns
For certificates handling, I need to investigate. cert-manager does not allow static certificates.
The text was updated successfully, but these errors were encountered: