NVIDIA / NVIDIA/holodeck

feat(provider): GKE managed clusters (experimental), layered on GCE plumbing

Open
#854 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
30
Forks
17
PR merge metrics
No merged PRs in 30d

Description

GKE via cloud.google.com/go/container, reusing the GCE auth/plumbing (#853) and the same experimental gating (mock-validated only until GCP credentials exist).

Shares the managed-control-plane path decided for EKS (#852) — whichever capability/ManagedCluster shape lands there applies here.

Sequenced last: depends on both the GCE provider (#853) and the EKS abstraction decision (#852).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the GCE provider work in #853 and the managed-control-plane abstraction decision in #852, then inspect the Go client at cloud.google.com/go/container. The work is done when GKE managed clusters reuse the GCE auth/plumbing and shared managed-cluster shape, with experimental gating and mock validation until GCP credentials are available.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, google-cloud
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.