kubernetes-sigs/cluster-api

Add a Custom Resource metrics configuration file to the release artifacts

Open

#7,229 opened on Sep 16, 2022

View on GitHub
 (14 comments) (0 reactions) (0 assignees)Go (1,532 forks)auto 404
help wantedkind/featurepriority/important-longtermtriage/accepted

Repository metrics

Stars
 (4,267 stars)
PR merge metrics
 (PR metrics pending)

Description

User Story

As a operator I would like to have metrics for my running Cluster API verison for day-2 operations.

Detailed Description

We recently added a first configuration for metrics for the core CAPI resources via

  • #6458

It would be great to add the configuration as artifact to future releases so an operator could also easily find the matching configuration when updating Cluster API.

Before doing so, we might want to ensure to generate the configuration from code as outlined in

  • #7158.

/kind feature

Contributor guide

Research direction
Understand the current metrics configuration generation from issue #6458 and #7158, then add the generated configuration file to the release artifacts.
Tech stack
gokubernetes
Domain
backenddevopsrelease
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
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
GitKubernetesGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60