colors for crds

[sherlant]

Hello,

there is a way for colored crds in k9s like pods ? I don't know if it's hardcoded for pods or depends on a status of resource.

thx

[placintaalexandru]

Hello @sherlant
Can you elaborate a little bit about this issue? Which color, more precisely, are you referring to?
There are a lot of places where colors are hardcoded and the skin.yaml is not taken into account. I attempt to fix part of that using this PR, but CRDS did not use a hardcoded color as far as I remember.

[sherlant]

Hello,
yes, of course. I want colors like this on crds :

[placintaalexandru]

Ok. I looked through the code and it seems that the CRDs don't have a function that is used to render their colours so the default one is used. When, more precisely, do you want the CRD to be red?

[sherlant]

yes,
but not all time, based on a status condition for example

[placintaalexandru]

Ok. I'll have a look at it these days

[sherlant]

thanks a lot

[sherlant]

Hello,
have you any news ?

[placintaalexandru]

Hello,

CRD's don't have a specific status, like PODs (pending, running, failed/completed, container status unknown).
It is possible for a subresource of a CRD to have a status field, defined in .status when creating the CRD, however this status field depends on the CRD type and is not something unique.

For example you could have:

• subresource1 where Kind: CRD1 with .status:

{
    "memory": "658Ki",
    "pods": "31"
}

• subresource2 where Kind: CRD2 with .status:

{
    "id": "12345",
    "zone": "dev"
}

Both status fields are different

[sherlant]

Hi,
thx for your reply.
I understand, but there are no way for k9s to have a convention with that ? If a particular field in .status is set, with conventional values, k9s use it to display the good color ?
And all crd's creator is free to use it or no ?

[placintaalexandru]

At the moment there is no such convention.
If you want, you can close this one and make a feature request

[sherlant]

Ok thanks you, i gonna try to do this asap.