[Help]: Discover with different hostname

[heruan]

Describe Your Issue or Question

I installed the StatefulSet and Service on a Kubernetes K3s cluster (Raspberry Pi 5) and it's correctly discovered:

I'd like to be discovered on backup.local instead of k8s-node-1.local (backup is a CNAME for k8s-node-1). I have tried to set the ADVERTISED_HOSTNAME environment variable to backup but once I do so, the share disappear from discovery (it only appears if I mount it explicitly in Finder). What am I missing to correctly use ADVERTISED_HOSTNAME?

Expected Behavior

Once I set ADVERTISED_HOSTNAME discovery still works.

Steps to Reproduce

1. deploy with ADVERTISED_HOSTNAME
2. try to discover in TM Settings

How You're Launching the Container

With the provided Kubernetes manifest.

Container Logs

Joining mDNS multicast group ...
Network interface enumeration completed.
Registering new address record for ...
Server startup complete. Host name is k8s-node-1.local. Local service cookie is 1143535626.
Service "backup" (/etc/avahi/services/smbd.service) successfully established.
become_local_master_stage2: *****

Samba name server K8S-NODE-1 is now a local master browser for workgroup WORKGROUP on subnet 10.42.0.0

*****
become_local_master_stage2: *****

Samba name server K8S-NODE-1 is now a local master browser for workgroup WORKGROUP on subnet 10.42.0.1

*****
become_local_master_stage2: *****

Samba name server K8S-NODE-1 is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.11

*****

[heruan]

I was able to solve this by using the node's Avahi daemon instead of the container one.