How to change default namespace

Hi!
I'm trying to install vespa in kubernetes by this instruction
I installed vespa in vespa namespace, but all componets are trying to use 'default' namespace

[2024-12-06 15:44:46.602] WARNING config-sentinel sentinel.vespalib.net.async_resolver could not resolve host name: 'vespa-configserver-2.vespa-internal.default.svc.cluster.local' [2024-12-06 15:44:46.602] WARNING config-sentinel sentinel.vespalib.net.async_resolver could not resolve host name: 'vespa-admin-0.vespa-internal.default.svc.cluster.local' [2024-12-06 15:44:46.602] WARNING config-sentinel sentinel.vespalib.net.async_resolver could not resolve host name: 'vespa-configserver-0.vespa-internal.default.svc.cluster.local' [2024-12-06 15:44:46.602] WARNING config-sentinel sentinel.vespalib.net.async_resolver could not resolve host name: 'vespa-configserver-1.vespa-internal.default.svc.cluster.local' [2024-12-06 15:44:46.607] WARNING config-sentinel sentinel.vespalib.net.async_resolver could not resolve host name: 'vespa-feed-container-1.vespa-internal.default.svc.cluster.local' [2024-12-06 15:44:46.608] WARNING config-sentinel sentinel.vespalib.net.async_resolver could not resolve host name: 'vespa-feed-container-0.vespa-internal.default.svc.cluster.local' [2024-12-06 15:44:46.608] WARNING config-sentinel sentinel.vespalib.net.async_resolver could not resolve host name: 'vespa-content-0.vespa-internal.default.svc.cluster.local' [2024-12-06 15:44:46.608] WARNING config-sentinel sentinel.vespalib.net.async_resolver could not resolve host name: 'vespa-content-1.vespa-internal.default.svc.cluster.local' [2024-12-06 15:44:46.611] WARNING config-sentinel sentinel.vespalib.net.async_resolver could not resolve host name: 'vespa-query-container-0.vespa-internal.default.svc.cluster.local' [2024-12-06 15:44:46.612] WARNING config-sentinel sentinel.vespalib.net.async_resolver could not resolve host name: 'vespa-query-container-1.vespa-internal.default.svc.cluster.local'

How to fix this?

Start with the linked GKE multinode-HA instruction and inspect how the Kubernetes namespace is configured for the Vespa components. Compare the deployed resources with the generated service hostnames, and consider the issue resolved when components installed in the vespa namespace resolve hosts using that namespace instead of default.