Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Module CRD label to enable status reporting #921

Open
a-thaler opened this issue Jul 22, 2024 · 1 comment
Open

Module CRD label to enable status reporting #921

a-thaler opened this issue Jul 22, 2024 · 1 comment
Labels
decision Related to all issues that need a decision

Comments

@a-thaler
Copy link
Contributor

a-thaler commented Jul 22, 2024

Created on 2024.07.22 by Andreas Thaler (@a-thaler ).

Decision log

Name Description
Title Align on a label to mark a Module CRD as having a reportable status
Due date ASAP
Status Proposed on 2024-07-22
Decision type Binary
Affected decisions -

Context

The different tools for Kyma like the CLI, Dashboard and also metrics for telemetry like to give status about the kyma module status. For that, the tools need a way to identify the module CRs so that they can use the status.state and status.conditions for introspection.

Currently there is no easy way to figure out these resources, they are spread across different API groups.

The goal is to have a unified way to know which CRD is representing a kyma module in order to leverage the status for reporting in a generic way

Decision

Have a consistent labelling on CRD level which indicates that this CRD is a represents a module status. The label is called kyma-project.io/report-module-status: true

Consequences

The approach will allow the different tools to dynamically search for CRDs having the proposed label. Determined CRDs will follow the conventions of module status and should be considered.

@a-thaler a-thaler added the decision Related to all issues that need a decision label Jul 22, 2024
@a-thaler
Copy link
Contributor Author

Relates to #864

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
decision Related to all issues that need a decision
Projects
None yet
Development

No branches or pull requests

1 participant