Gaëtan Lehmann

> Currently my concerns are mainly 2: table colors and key-value color duplication. It would be helpful if you can tell me some thoughts. > > I am neither UI...

sorry @dty1er I somehow missed your comments. Here are a few snapshots to illustrate the output of kubecolor with my changes:    strings output look good to me...

Is there a known workaround for this problem? Should we file a bug report at bincode?

Thanks! I'll file a bug report tomorrow.

I guess https://github.com/servo/bincode/issues/227 is related — would it be good enough for custom_error?

I see that the docker registry is able to redirect to its S3 backend, so I should be able to use my S3 service quite efficiently just by using a...

I realize this is a non backward compatible change. Any idea for a better implementation is welcome!

in addition to terraform, this is also a problem with helm which require a manual intervention in that case. Clearly not ideal!

we could have a `force=True` arg in `default_registry`. It would default to `False` and allow to actually force the value even when `local-registry-hosting` is defined in the cluster

I haven't looked at the tests (quite obviously!) — I'm waiting on a opinion on this change before taking care of that :-)