kubernetes-sigs / kubernetes-sigs/cluster-api

Add a Custom Resource metrics configuration file to the release artifacts

Open
#7,229 14 comments 0 reactions 0 assignees View on GitHub
help wanted kind/feature priority/important-longterm triage/accepted
Dominant language
Go
Stars
4.3k
Forks
1.6k
Avg merge
1d 3h
Merged PRs (30d)
113

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

Open the contributing guide

Research direction

Start by reading issues #6458 and #7158, then inspect how Cluster API release artifacts are generated and packaged. Determine how the existing core-resource metrics configuration should be generated from code and attached to future releases. Done means operators can find the matching Custom Resource metrics configuration in each release artifact.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
observability, release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.