cephadm: don't add --publish options to clustered instances

Clustered instances use host networking (for reasons) and nothing
benefits from having --publish options in the container cli
doing nothing and possibly being misleading (as there could be
way more ports bound than the container runtime shows).

Signed-off-by: John Mulligan <[email protected]>

Author: phlogistonjohn

src/cephadm/cephadmlib/daemons/smb.py

@@ -225,11 +225,17 @@ def args(self) -> List[str]:
 
     def container_args(self) -> List[str]:
         cargs = []
-        if self.cfg.smb_port:
-            cargs.append(f'--publish={self.cfg.smb_port}:{Ports.SMB.value}')
-        if self.cfg.metrics_port:
-            metrics_port = self.cfg.metrics_port
-            cargs.append(f'--publish={metrics_port}:{metrics_port}')
+        if not self.cfg.clustered:
+            # if we are not clustered we use container networking (vs. host
+            # networking) and need to publish ports via podman/docker.
+            # All published ports happen at the primary container.
+            if self.cfg.smb_port:
+                cargs.append(
+                    f'--publish={self.cfg.smb_port}:{Ports.SMB.value}'
+                )
+            if self.cfg.metrics_port:
+                metrics_port = self.cfg.metrics_port
+                cargs.append(f'--publish={metrics_port}:{metrics_port}')
         cargs.extend(_container_dns_args(self.cfg))
         return cargs