Features Pricing Build Docs Demos About Register or sign in
GCP Service inventory

GKE clusters

Every GKE cluster with Kubernetes version, node-pool count, location and endpoint.

Category Inventory
Service ID gcp_gke_clusters
Scope One region
Mock data. This preview shows how the pane renders when embedded in a page. Add an access key linked to your cloud account to see that account's data.

How often it refreshes

Cached data is served within the window your plan guarantees. Faster refresh is one of the things a higher plan buys.

ExplorerBuilderTeam
20 min5 min3 min

Linking to LightPane

Once you connect one or more cloud accounts in LightPane you can create access keys, which are what allow panes to read those accounts. A key is a text string: the prefix lp_ak_ followed by 43 characters drawn from A–Z a–z 0–9 - _ (URL-safe base64 of 32 random bytes), so 49 characters in all.

Each cloud account you connect is also given an account handle — a short name such as zesty-ridge, minted by LightPane when you link the account and never changed afterwards. It lets a pane reference the same account for good, without putting a cloud account ID in your page. Use the handle, not the account's editable alias: renaming an alias makes a pane match nothing, and that failure is silent — the pane shows an ordinary empty state, not an error. More on naming accounts.

When adding the code below into your web page, replace lp_ak_YOUR_ACCESS_KEY and YOUR_ACCOUNT_HANDLE with your own access key and account handle.

  • No key? Paste this exactly as it is. With the placeholder still in, the pane renders clearly-marked mock data, so you can place and style it before you connect anything. (A key that is present but rejected shows an error instead — a live dashboard must never quietly fall back to sample numbers.)
  • No handle? The pane falls back to the access key's default account. That works, but the default moves if the key's grants change — naming a handle is what guarantees the same account every time.

How to embed

Have an account? Use this pane in the console → — it fills in your access key, account handle and region, and builds the finished snippet for you.

Embedding within a web page

lp.js is the only script you add. It loads the LightPane runtime and, for each pane container on the page, fetches that pane's own code for you — so the first block never changes however many panes you add.

1

Once per page, in <head>

<script>window.lpEmbed = { accessKey: "lp_ak_YOUR_ACCESS_KEY" };</script>
<script src="https://lightpane.cloud/embed/lp.js"></script>
2

One container, where the pane should appear

<div data-lp-service="gcp_gke_clusters"
     data-lp-account="YOUR_ACCOUNT_HANDLE"
     data-lp-attributes="project,name,status,location,current_master_version"></div>

data-lp-service is how lp.js knows what to load — without it the pane will not appear. data-lp-attributes picks which columns render; omit it for the service default.

Embedding in an iframe

For somewhere you cannot add scripts — Confluence, Notion, a wiki, a SharePoint page — or anywhere a self-contained window suits better than a pane woven into the parent page.

<iframe src="https://lightpane.cloud/embed/v1/?service=gcp_gke_clusters&provider=gcp&account=YOUR_ACCOUNT_HANDLE#k=lp_ak_YOUR_ACCESS_KEY"
        title="GKE clusters"
        style="width:100%;height:460px;border:0"></iframe>

The key sits after the #, so it stays in the browser and is never sent to our servers as part of the URL.

Choosing columns

data-lp-attributes takes a comma-separated list of attribute IDs. It sets both which attributes become columns and the order they appear in. Leave it off and the pane renders its default set — the attributes marked Default below.

The first six attributes stay in the row. Any beyond six fold into the row's expandable drawer, as do columns that will not fit the width the host page gives the pane. The first column is never folded away, so lead with the attribute you most want read at a glance. How panes resize has the measured widths at which each column drops.

Labels — position changes the behaviour

Auditing how labels are applied, and simply having them to hand, are different jobs — so labels is treated differently depending on where you put it in the list.

Where you put labels What the pane does
First in the list It leaves the columns entirely and every row opens expanded, so each resource’s labels are visible without a click.
Anywhere else It shows as a count — (2 Labels) — and the chips sit inside the drawer, closed until the row is expanded.
Left out — the default They do not appear at all: no column, no drawer section. No pane carries labels in its default set.

Put it first when the page is about labels — auditing coverage before a cost-allocation report, finding the resources that have none, checking a required key is applied across an estate. Leave it later in the list, or off, when labels are reference detail and you want the rows to stay scannable.

<div data-lp-service="gcp_gke_clusters"
     data-lp-account="YOUR_ACCOUNT_HANDLE"
     data-lp-attributes="labels,project,name,status,location"></div>

Attributes available

Each of these can be named in data-lp-attributes. Copy the value — that is the attribute ID the pane matches on.

Default columns

What the pane renders when data-lp-attributes is absent, in this order.

Name Value Type
Project project text
Name name text
Status status status_badge
Location location text
Master version current_master_version text
Node count node_count text
Network network gcp_resource_name
Endpoint endpoint text
Create time create_time datetime

Additional attributes

Not rendered unless you ask for them. Naming any attribute at all replaces the default set entirely, so list every column you want — including the defaults you want to keep.

Name Value Type
Node version current_node_version text
Subnetwork subnetwork gcp_resource_name
Labels labels tags_table