Skip to main content
Book a demo

Connect Google Kubernetes Engine to Glean

Give Glean governed access to Google Kubernetes Engine through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Glean setup guide

Set up

Add Google Kubernetes Engine to Glean in four steps

Admins approve the server once. Everyone in Glean then gets it through the same governed connection.

  1. 1

    Approve Google Kubernetes Engine in Runlayer

    Add Google Kubernetes Engine from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Glean to Runlayer

    Users add the Runlayer Plugin to Glean by following Runlayer’s setup guide. Glean reaches Google Kubernetes Engine’s tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Glean setup guide
  3. 3

    Sign in to Google Kubernetes Engine

    Each user signs in to Google Kubernetes Engine with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Google Kubernetes Engine from Glean

    Google Kubernetes Engine’s approved tools appear in Glean. Every call is checked against policy and recorded.

Tools

Google Kubernetes Engine tools in Glean

Google Kubernetes Engine reports its tools when your organization connects it, so the list depends on your deployment.

Control

What Runlayer can see and stop in Glean

Some controls apply to every client at the gateway. Others depend on what Glean exposes to Runlayer.

  • Gateway policy (available)

    Every Google Kubernetes Engine call from Glean passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Glean as the client, the tool, and the policy and scanner decisions.

  • OTLP telemetry (available)

    Glean can send supported OpenTelemetry events to Runlayer for observe-only session visibility.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for Glean yet, so control happens at the gateway.

In Glean

  • Runlayer sees Glean activity through OpenTelemetry traces for monitoring only; enforcement happens at the gateway.

Frequently asked questions

Connect more

Find another combination