Answer
This has been traced to an incorrect password specified somewhere in the Cloud installer's YAML configuration file rather than an actual namespace/Kubernetes problem — recreate the YAML file from the current official template (matching its exact structure and syntax) and carefully re-verify every password and file path in it, rather than troubleshooting namespace or certificate configuration directly, since a bad password value in that file can surface as this seemingly unrelated "namespace must be set" error.