kubernetes-sigs/cluster-api-provider-vsphere

Modify the template generation logic for CAPV templates

Open

#1,384 opened on Jan 28, 2022

View on GitHub
 (8 comments) (0 reactions) (2 assignees)Go (320 forks)auto 404
good first issuehelp wantedkind/featurelifecycle/rotten

Repository metrics

Stars
 (417 stars)
PR merge metrics
 (PR metrics pending)

Description

/kind feature

Describe the solution you'd like Currently, the template generation code for kibe-vip based templates generates a ClusterResourceSet which installs the CPI/CSI on the workload cluster. The names of these resources created by the CRS are not dynamically generated. Hence if trying to reuse the same manifest template for different workload clusters results in the same secrets/config maps(used by the CRS) being updated. This could have unintended consequences when working with multiple clusters.

Anything else you would like to add: It would be great if we could prefix the resources with the name of the cluster to enable reuse of the same templates for different workload clusters.

Environment:

  • Cluster-api-provider-vsphere version: n/a
  • Kubernetes version: (use kubectl version): n/a
  • OS (e.g. from /etc/os-release): n/a

/help /good-first-issue

Contributor guide

Research direction
Investigate the template generation logic for CAPV, specifically the ClusterResourceSet creation for kube vip based templates. Identify where secrets and config maps are created and modify the code to prefix these resources with the cluster name to enable reuse across different workload clusters.
Tech stack
go
Domain
infrastructurebackend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoKubernetes basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75