GKE
This guide describes how to manage access to an Google Kubernetes Engine (GKE) cluster. Adding a GKE cluster takes place in the StrongDM Admin UI, Google Cloud Console, and Google Developers Console.
Prerequisites
Before you begin, ensure that the GKE endpoint you are connecting is accessible from one of your StrongDM gateways or relays. See our guide on nodes for more information.
Add Your GKE Cluster in the StrongDM Admin UI
Log in to the Admin UI and go to Infrastructure > Clusters.
Click the Add cluster button.
Select Google Kubernetes Engine as the Server Type and set other resource properties to configure how the StrongDM relay connects.
Click Create to save the resource.
The Admin UI updates and shows your new cluster in a green or yellow state. Green indicates a successful connection. If it is yellow, click the pencil icon to the right of the server to reopen the Connection Details screen. Then click Diagnostics to determine where the connection is failing.
Resource properties
Configuration properties are visible when you add a Cluster Type or when you click to view the cluster's settings. The following table describes the settings available for your GKE cluster.
Display Name
Required
Meaningful name to display the resource throughout StrongDM; exclude special characters like quotes (") or angle brackets (< or >)
Cluster Type
Required
Select Google Kubernetes Engine
Proxy Cluster
Required
Defaults to "None (use gateways)"; if using proxy clusters, select the appropriate cluster to proxy traffic to this resource
Endpoint
Required
Endpoint of the GKE cluster, such as 35.232.191.126; relay server should be able to connect to your GKE endpoint
Connectivity Mode
Required
Select either Virtual Networking Mode, which lets users connect to the resource with a software-defined, IP-based network; or Loopback Mode, which allows users to connect to the resource using the local loopback adapter in their operating system; this field is shown if Virtual Networking Mode enabled for your organization
IP Address
Optional
If Virtual Networking Mode is the selected connectivity mode, an IP address value in the configured Virtual Networking Mode subnet in the organization network settings; if Loopback Mode is the selected connectivity mode, an IP address value in the configured Loopback IP range in the organization network settings (by default, 127.0.0.1); if not specified, an available IP address in the configured IP address space for the selected connectivity mode will be automatically assigned; this field is shown if Virtual Networking Mode and/or multi-loopback mode is enabled for your organization
Port Override
Optional
If Virtual Networking Mode is the selected connectivity mode, a port value between 1 and 65535 that is not already in use by another resource with the same IP address; if Loopback Mode is the selected connectivity mode, a port value between 1024 to 64999 that is not already in use by another resource with the same IP address; when left empty with Virtual Networking Mode, the system assigns the default port to this resource; when left empty for Loopback Mode, an available port that is not already in use by another resource is assigned; preferred port also can be modified later from the Port Overrides settings
DNS
Optional
If Virtual Networking Mode is the selected connectivity mode, a unique hostname alias for this resource; when set, causes the desktop app to display this resource's human-readable DNS name (for example, k8s.my-organization-name) instead of the bind address that includes IP address and port (for example, 100.64.100.100:5432)
Secret Store
Optional
Credential store location; defaults to Strong Vault; to learn more, see Secret Store options
Server CA
Optional
Server CA, which is available under the Show Credentials link just to the right of the endpoint in the Google Cloud Platform console
Service Account Key
Required
Service account key in JSON format; you can generate this key in the Google Developers Console; ensure it is associated with a user having the appropriate level of access to the cluster for your use case; once generated, upload the key using the button below the Service Account Key box
Healthcheck Namespace
Optional
If enabled for your organization, the namespace used for the resource healthcheck; defaults to default if empty; supplied credentials must have the rights to perform one of the following kubectl commands in the specified namespace: get pods, get deployments, or describe namespace
Authentication
Required
Authentication method to access the cluster; select either Leased Credential (default) or Identity Aliases (to use the Identity Aliases of StrongDM users to access the cluster)
Identity Set
Required
Displays if Authentication is set to Identity Aliases; select an Identity Set name from the list
Healthcheck Username
Required
If Authentication is set to Identity Aliases, the username that should be used to verify StrongDM's connection to it; username must already exist on the target cluster
Resource Tags
Optional
Resource Tags consisting of key-value pairs <KEY>=<VALUE> (for example, env=dev)
Display name
Some Kubernetes management interfaces, such as Visual Studio Code, do not function properly with cluster names containing spaces. If you run into problems, please choose a Display Name without spaces.
Google credentials
When your users connect to this cluster, they have exactly the rights permitted by this Google Service Account key. See this Google document for more information.
Secret Store options
By default, server credentials are stored in StrongDM. However, these credentials can also be saved in a secrets management tool.
Non-StrongDM options appear in the Secret Store dropdown menu if they are created under Settings > Secrets Management. When you select another Secret Store type, its unique properties display. For more details, see Configure Secret Store Integrations.
Last updated
Was this helpful?