gke-e2e-testing

Automate GCSFuse CSI driver conformance testing on GKE clusters with Ginkgo.

9|6|Updated Jan 11, 2025
One-click install
npx skills add https://github.com/GoogleCloudPlatform/gcsfuse-tools --skill gke-e2e-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gke-e2e-testing
Source: https://github.com/GoogleCloudPlatform/gcsfuse-tools/tree/main/npi/.agents/skills/gke-e2e-testing
Command: npx skills add https://github.com/GoogleCloudPlatform/gcsfuse-tools --skill gke-e2e-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the complex, multi-step process of validating GCSFuse CSI driver functionality on GKE, ensuring POSIX compliance and integration stability while preventing manual configuration errors.

Core Features & Use Cases

  • Isolated Environment Management: Enforces strict KUBECONFIG isolation to protect host system configurations during cluster interaction.
  • Automated Test Execution: Orchestrates Ginkgo-based E2E test suites with configurable parallelization and selective test focusing.
  • Conformance Reporting: Parses raw test outputs into structured JSON results for NPI qualification and integration validation.

Quick Start

Use the gke-e2e-testing skill to execute the full conformance test suite on the target GKE cluster after configuring the isolated environment.

Frequently Asked Questions about gke-e2e-testing

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

FAQPage Schema
How do I automate GCSFuse CSI driver conformance testing on a GKE cluster?

Automate GCSFuse CSI driver conformance testing on GKE by managing isolated KUBECONFIG contexts and executing Ginkgo test suites. This validates functional correctness, POSIX compatibility, and workload identity integration for Stage 2 NPI pipeline validation.

What is the best way to run Ginkgo E2E test suites for GKE without affecting my host configuration?

The best way to run Ginkgo E2E test suites safely is by enforcing strict KUBECONFIG isolation, which protects your host system configurations during GKE cluster interaction while orchestrating tests with configurable parallelization and selective test focusing.

Do I need gcloud and kubectl to perform GCSFuse end-to-end testing on GKE?

Yes, you need gcloud and kubectl to perform GCSFuse end-to-end testing on GKE, as they are required to manage cluster operations and isolated KUBECONFIG contexts. The Ginkgo test framework is also necessary to execute the E2E conformance test suites.

How does GKE conformance reporting work for GCSFuse CSI driver validation?

GKE conformance reporting works by parsing raw Ginkgo test outputs into structured JSON results for GCSFuse CSI driver validation. This automated process ensures POSIX compliance and integration stability while qualifying functional correctness for Stage 2 NPI pipeline validation.

Can I focus on specific Ginkgo tests when running GCSFuse conformance checks on GKE?

Yes, you can focus on specific Ginkgo tests when running GCSFuse conformance checks on GKE. The automated test execution orchestrates Ginkgo-based E2E test suites with configurable parallelization and selective test focusing to validate specific functional correctness or POSIX compatibility scenarios.