Closed as not planned
Description
Describe the bug
Some CRDs appear in red, but not sure what the reason is.
They contain some deprecated versions of their schema, which is pretty standard, but their most recent schema is not deprecated and should be displayed as such it seems
To Reproduce
In my case, I was deploying a kubernetes cluster with CAPI, most controller resource appear red
Historical Documents
This is an example resource that shows in red
apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
[...]
name: machines.cluster.x-k8s.io
spec:
conversion:
strategy: Webhook
webhook:
[...]
conversionReviewVersions:
- v1
- v1beta1
group: cluster.x-k8s.io
names:
[...]
scope: Namespaced
versions:
- additionalPrinterColumns:
- description: Provider ID
[...]
deprecated: true
name: v1alpha3
schema:
[...]
served: false
storage: false
subresources:
status: {}
- additionalPrinterColumns:
[...]
deprecated: true
name: v1alpha4
schema:
...]
served: false
storage: false
subresources:
status: {}
- additionalPrinterColumns:
[...]
name: v1beta1
schema:
[...]
served: true
storage: true
subresources:
status: {}
status:
acceptedNames:
categories:
- cluster-api
kind: Machine
listKind: MachineList
plural: machines
shortNames:
- ma
singular: machine
conditions:
- lastTransitionTime: "2024-08-19T09:58:32Z"
message: no conflicts found
reason: NoConflicts
status: "True"
type: NamesAccepted
- lastTransitionTime: "2024-08-19T09:58:32Z"
message: the initial names have been accepted
reason: InitialNamesAccepted
status: "True"
type: Established
storedVersions:
- v1beta1
Expected behavior
I think this particular resource should have the standard color (blue)
Screenshots
Versions (please complete the following information):
- OSX
- K9s: 0.32.5
- K8s: v1.31.0