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

when a status.conditions has unknown it should be explicit #173

Open
bergerx opened this issue Oct 1, 2021 · 0 comments
Open

when a status.conditions has unknown it should be explicit #173

bergerx opened this issue Oct 1, 2021 · 0 comments
Labels
good first issue Good for newcomers template only Something that involves only go template changes

Comments

@bergerx
Copy link
Owner

bergerx commented Oct 1, 2021

Currently, we only color-code it based on the status field value. But the status field conventionally has one of these 3 values: "True", "False", "Unknown".

The current behavior is to accept Unknown as an explicit faulty status rather than missing information. We should be explicit about the "Unknown" value in such cases.

See https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#typical-status-properties for more details.

@bergerx bergerx moved this to To do in Template Improvements Jul 26, 2024
@bergerx bergerx added good first issue Good for newcomers template only Something that involves only go template changes labels Jul 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers template only Something that involves only go template changes
Projects
Development

No branches or pull requests

1 participant