better colorscheme for kubecolor

[hidetatz]

What's this?

This is a space to duscuss the better color scheme of kubecolor for the community.

Current kubecolor's architecture

Kubecolor executes kubectl command internally, with given arguments. For example, if you run kubecolor get pods -o yaml, then kubecolor internally runs kubectl get pods -o yaml , and captures the output, then colorizes it.

Kubecolor first judges if it should do the coloring by isColoringSupported function. If it is judged it should not be colorized, then kubecolor just prints it out.

We can categorize the kubectl output into 4 types:

• Table
• Json
• Yaml
• Custom

Table

Table is a format which shows the data into rows and columns.

When this is printed: get, top, api-resources.

Json

Json is printed when an option -o json is specified. (Not all subcommands support it)

Yaml

Yaml is printed when an option -o yaml is specified. (Not all subcommands support it)

Custom

Some subcommands shows their output in original format.
When this is printed: apply, describe, explain, version, options.

apply:

describe:

explain:

version:

options:

What will we discuss?

We'll discuss if we can improve how the output of kubecolor looks by updating current colorscheme. We basically have 3 things to discuss:

• Is current colorscheme good? Can we improve it by introducing something new?
• Is current colorscheme ok from accessibility point of view? For example, can color blind people use kubecolor?
• Should we make kubecolor's color configurable? If yes, what interface should it take? (e.g. do we use config file? what's the structure?)

If you have some opinions about them, please leave it as comments here.

Related issue: #40

Disclaimer

• Please don't discuss things not related to the color. It should be in another discussion topic or another issue.
• Anyone can leave comments here, but the kubecolor's author @dty1er is responsible to all the decisions.