Kubernetes installation not updating server_name?

Installation & Configuration
1

Hi all,

I currently have a server with Collabora Online working, which I installed by using “apt install coolwsd”, nginx and let’s encrypt.

I also have an instance of NextCloud which points to that Collabora working all fine as expected.

Now, I decided to setup a new Collabora server, this time using Kubernetes, and then I followed this tutorial for it.

I chose to use nginx, installed it, and all tests seem the installation worked fine, except that, when I update my NextCloud to point to that new server instead, it shows this error below:

Your browser has been unable to connect to the Collabora server: http://no2.mydomain.com
This URL is determined on the Collabora server either from the configured URL or the server_name parameter in coolwsd.xml.

My values.yaml has this content below:


collabora:
  server_name: no2.mydomain.com
  password: admin
  username: admin

autoscaling:
  enabled: true
  minReplicas: 1
  maxReplicas: 3

I logged into the pod to see how /etc/coolwsd/coolwsd.xml looks like, and it has no value in the server_name tag, as you can see below:

<server_name desc="External hostname:port of the server running coolwsd. If empty, it's derived from the request (please set it if this doesn't work). May be specified when behind a reverse-proxy or when the hostname is not reachable directly." type="string" default=""></server_name>

I also tried with aliasgroups and/or ssl.enable=true:

collabora:
  server_name: no2.mydomain.com
  aliasgroups:
    - host: "http://no2.mydomain.com:443"
  extra_params: --o:ssl.enable=true
  password: admin
  username: admin

But got the same result :frowning:

Does anyonw know what can be wrong?

Thanks

2

Hi, for my part I created configmaps rather than the values.yaml file, so I updated my coolwsd.xml and I send it to the pods via the configmap.

3

hummm, I see. Did you follow any tutorial or guidance on how to install Collabora on Kubernetes using ConfigMap? I used this here, that’s based on a Helm chart, and as I’m neither too good on Collabora nor on K8s, I guess I wouldn’t know how to setup from scratch without a tutorial or the like.

4

I’m sorry, but I didn’t follow a tutorial, I had the idea to add the configmap because I had problems testing with the values.yaml.
I create the configmap from a file that I extracted from a pod, here is the command I use to create the configmap:
kubectl create configmap coolwsd --from-file=coolwsd.xml --dry-run=client -o yaml | kubectl apply -f -

Then you have to attach the volume in your POD deployment:

volumes:
  - name: "coolwsd"
    configMap:
        name: "coolwsd"

And mount it also for PODS:

volumeMounts:
  - name: "coolwsd"
    mountPath: "/etc/coolwsd/coolwsd.xml"
    subPath: "coolwsd.xml"

Don’t forget to modify the lines:
server name with the dns name that you give to your server
frame_ancestors with the servers authorized to connect to your CODE