Rhdh Gke Tests

openshift/rhdh-gke-tests

>- List GKE test entries in RHDH ci-operator config files. Use when listing e2e-gke tests or checking which branches have GKE test entries. Unlike AKS/EKS, GKE uses a pre-existing static cluster — version upgrades are performed via the GCP Console.

544 tokens

context cost

the whole folder, loaded on every use

files

ships runnable scripts

copies elsewhere

how many repositories repackaged it

325

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/openshift/release --skill rhdh-gke-tests

What comes with it

653 bytes besides the instruction

OWNERS

scripts/OWNERS

scripts/list-k8s-test-configs.sh

What it tells the agent to use

found in the instruction text

Bash runs shell commands — read the instruction before connecting

The instruction itself

6 sections, as written by the author

RHDH GKE Test Management

List GKE test entries across RHDH release branches.

Unlike AKS/EKS which set MAPT_KUBERNETES_VERSION in CI config files, GKE uses

a pre-existing static cluster. Version upgrades are performed via the GCP Console.

When to Use

List which GKE test entries exist per RHDH release branch
Verify test coverage across branches

Prerequisites

yq (v4+) for listing tests

Listing Tests

bash "${CLAUDE_SKILL_DIR}/scripts/list-k8s-test-configs.sh" \
  --pattern "^e2e-gke-"

Filter by branch: add --branch main.

Cluster Version Management

The GKE cluster details (name, region, project) are stored in the rhdh secret

under test-credentials. To check the current version and perform upgrades,

use the GCP Console:

Open the GKE clusters page
Select the correct project
Click on the cluster to view version details and available upgrades

NOTE: make update is NOT required — the version lives on the cluster, not in CI config.

rhdh-gke-lifecycle: Check which K8s versions are supported before upgrading

How to use it

Copy the folder

Take openshift/rhdh-gke-tests from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.