rackspace-spot-access

Retrieve a Rackspace Spot kubeconfig and debug ARC runners with spotctl.

Updated Sep 23, 2025
One-click install
npx skills add https://github.com/Matchpoint-AI/matchpoint-github-runners-helm --skill rackspace-spot-access
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rackspace-spot-access
Source: https://github.com/Matchpoint-AI/matchpoint-github-runners-helm/tree/main/.claude/skills/rackspace-spot-access
Command: npx skills add https://github.com/Matchpoint-AI/matchpoint-github-runners-helm --skill rackspace-spot-access

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides step-by-step instructions for accessing the Rackspace Spot Kubernetes cluster to debug ARC runners using spotctl. The guide covers installation, authentication via GCP Secret Manager, kubeconfig retrieval, and common debugging commands. Activates on "spotctl", "cluster access", "rackspace debug", "kubeconfig", or "spot cluster".

Core Features & Use Cases

  • Token retrieval: Retrieve the API token from GCP Secret Manager.
  • Spotctl configuration: Configure spotctl with organization and token.
  • Kubeconfig access: Retrieve kubeconfig for the matchpoint-runners cluster and export KUBECONFIG.
  • Connectivity checks: Verify cluster readiness with kubectl.
  • Use Case: Debug ARC runners in Rackspace Spot with guided commands to quickly identify issues.

Quick Start

Use the rackspace-spot-access skill to retrieve the API token from GCP Secret Manager and configure spotctl for the matchpoint-runners cluster, then generate the kubeconfig and verify kubectl connectivity.

Frequently Asked Questions about rackspace-spot-access

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I access the Rackspace Spot Kubernetes cluster for ARC runner debugging?

Access the Rackspace Spot Kubernetes cluster by installing spotctl, retrieving your API token from GCP Secret Manager, configuring spotctl with your organization credentials, and generating the kubeconfig for the matchpoint-runners cluster. Use kubectl to inspect pods, nodes, events, and logs across runner namespaces.

What do I need to set up before configuring spotctl for cluster access?

Before configuring spotctl, ensure you have the API token stored in GCP Secret Manager and role-based access permissions to retrieve it. You'll also need spotctl installed locally and kubectl configured to connect to the matchpoint-runners cluster.

How do I retrieve and use the kubeconfig for the matchpoint-runners cluster?

Retrieve the kubeconfig using spotctl after authentication, then export it to the KUBECONFIG environment variable. This enables kubectl connectivity to inspect ARC runner pods, nodes, and logs across namespaces.

Can I use spotctl with GCP Secret Manager for token management?

Yes. Spotctl integrates with GCP Secret Manager to retrieve API tokens securely. Configure spotctl with your organization and the retrieved token to authenticate and access the Rackspace Spot Kubernetes cluster for ARC debugging.

What kubectl commands work for debugging ARC runners in Rackspace Spot?

After configuring spotctl and exporting kubeconfig, use kubectl to list and inspect pods, nodes, and events across runner namespaces, and retrieve container logs to identify ARC runner issues and connectivity problems.