config file is invalid, err: an empty namespace may not be set when a resource name is provided

Products

• VMware Tanzu Data Suite

Issue/Introduction

Upgrading GPSS from 1.X to 2.X ->
When the container runs in OCP, (when the entrypoint is invoked) ("gpss") this error message displays in the container logs: 

config file is invalid, err: an empty namespace may not be set when a resource name is provided

Cause

GPSS looks for the environment variables KUBERNETES_SERVICE_HOST and KUBERNETES_SERVICE_PORT. If these are set, GPSS assumes it's running within Kubernetes.
 
GPSS then uses Kubernetes pod tags to determine the network configuration. If the pod has the tag "app.kubernetes.io/app", it looks for a corresponding service with the same name as the tag value. Further, it uses this service information to set the following configurations:
 

• ListenAddress.Host
• GPFdist.host and GPFdist.port: This is determined based on the service type:
  • Loadbalancer service
  • ClusterIP service
  • Nodeport service

 

Resolution

Since built in Kubernetes support is currently available, it is suggested to consider the new GPSS kubernetes offering, "Tanzu Greenplum Streaming Server on Kubernetes 1.0".

Additional options to mitigate this error are:

• Set KUBERNETES_SERVICE_HOST and KUBERNETES_SERVICE_PORT to empty in the pod env spec.
• Add the above label to the pod, and create a corresponding service.