License upgrade path unclear

[infocusmodereal]

I am running a cluster in version 24.1 in K8s on which I would like to upgrade the community license to our premium license. The documentation states the following:

licenseSecret
The Secret that contains the contents of license files. The Secret must share a namespace with the custom resource (CR). Each of the keys in the Secret is mounted as a file in /home/dbadmin/licensing/mnt.
If this value is set when the CR is created, the operator installs one of the licenses automatically, choosing the first one alphabetically.

If you update this value after you create the custom resource, you must manually install the Secret in each Vertica pod.

But there are not steps to "manually install the Secret in each Vertica pod".

After making an update to the licenseSecret parameter in the spec, I am able to see the file properly mounted in the pods:

[root@hostname ~]# kubectl -n vertica-cluster exec -it vertica-cluster-default-0 -- /bin/bash
Defaulted container "server" out of: server, vertica-logger
bash-5.1$ 
bash-5.1$ ls -lrtah /home/dbadmin/licensing/mnt
total 0
lrwxrwxrwx 1 root 5000  26 Apr 14 16:54 vertica_license.xml -> ..data/vertica_license.xml
lrwxrwxrwx 1 root 5000  32 Apr 14 16:54 ..data -> ..2025_04_14_16_54_52.3999000152
drwxr-sr-x 2 root 5000  60 Apr 14 16:54 ..2025_04_14_16_54_52.3999000152
drwxrwsrwt 3 root 5000 100 Apr 14 16:54 .
drwxr-xr-x 1 root root  17 Apr 14 16:55 ..

But the license does not get updated in the cluster. The current license is still the community version. What specific steps should be followed to update the license? Are there any documents for that?

[infocusmodereal]

I was able to get this working after doing this:

SELECT install_license('/home/dbadmin/licensing/mnt/vertica_license.xml');

I'm leaving the issue opened so this gets added to the documentation. But feel free to close if you consider this not useful.

Thanks!

[roypaulin]

Thanks! I will keep it open.