Port Overrides

Last modified on August 10, 2022

By default, all resources of a given type share the same port on the client side. This port is usually the default port used by that database type, such as port 3306 for MySQL or port 5432 for Postgres. If the port is already taken on the client, it auto-increments instead.

To connect to a different resource of the same type, disconnect from the first resource and connect to the second. You can use a port override when connecting to resources of the same type simultaneously.

Port Overrides

Port overrides are enabled by default. If they were disabled by your organization, you can turn them on in the Admin UI > Settings > Port Overrides section. You can specify port overrides for all resource types, including SSH servers and Kubernetes clusters.

Port overrides for Kubernetes

Port overrides on Kubernetes clusters require updating the kubectl configuration in order to access the clusters successfully.

Please do the following:

  1. In the Admin UI, go to Settings > Port Overrides and specify the port override number for your Kubernetes cluster.
  2. Check that your cluster is connected.
  3. Update the kubectl configuration.
    1. If using the GUI, go to the Account menu and select Update kubectl configuration.

    2. If using the CLI, run the following command with the force option:

      sdm k8s update-config --force
      

Now you can successfully access the resource again.

End-User Experience

Port overrides ensure that users automatically have ports assigned for each resource and can connect to multiple resources of the same type concurrently.

Port Overrides On
Port Overrides On
Top