-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
CRDs listed in red but don't seem to be deprecated #2836
Comments
If a version in crd is “deprecated” or NOT “served” it will be red, you can check the |
Not sure I understand why a version not served AND deprecated would be a problem. Seems like pretty standard CRD lifecycle stuff or am I missing something ? |
Uh-huh, I think it's just “reusing” the color “red” by the way, it doesn't mean “error” or anything like that. Just highlighting it? 🤔️ |
Same as CrashLoopBackOff and Error containers ? In any case that's certainly something that drains more attention than it should. |
Indeed, it might be a bit better to change the color or express it in some other way (e.g. using 🗑 or |
I'm experiencing the same issue. I wonder if perhaps this might share cause with #2842, ie. wrong (old) CRD API version being picked out of multiple ones present in the definition. |
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
Expected behavior
I think this particular resource should have the standard color (blue)
Screenshots
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered: