Skip to content

port-forward works when pgsql_proxy_bind_address is 0.0.0.0 instead of 0.0.0.0:5433Β #41

@hongbo-miao

Description

@hongbo-miao

I had a question regarding how to port-forward web UI correctly at https://forum.yugabyte.com/t/how-to-port-forward-correctly/1181

I try to deploy by operator based on this tutorial https://docs.yugabyte.com/latest/deploy/kubernetes/single-zone/oss/yugabyte-operator/

kubectl create -f deploy/crds/yugabyte.com_ybclusters_crd.yaml
kubectl create -f deploy/operator.yaml
kubectl create -f deploy/crds/yugabyte.com_v1alpha1_ybcluster_cr.yaml

The files mentioned above are at https://github.com/yugabyte/yugabyte-operator/tree/966ef1978ed5d714119548b2c4343925fe49f882/deploy

Alan Caldera answered me (thanks!)

I made it work by adding

    gflags:
      - key: webserver_interface
        value: "0.0.0.0"

However, I met some unexpected things.

Based on the document https://docs.yugabyte.com/latest/reference/configuration/yb-tserver/#pgsql-proxy-bind-address

pgsql_proxy_bind_address is default to 0.0.0.0:5433.

However, in reality, port-forward works when use

      - key: pgsql_proxy_bind_address
        value: "0.0.0.0"

but this does not work:

      - key: pgsql_proxy_bind_address
        value: "0.0.0.0:5433"

It would be great to fix either doc or code, thanks! πŸ˜ƒ

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions