k8s-discovery
k8s-discovery copied to clipboard
Expose more info: current context, is in kluster, is dev env
Additional info about the target cluster, for me mainly for safety check when running out of cluster (e.g: refuse to run on production cluster)
BTW, how the handle the difference in module name when doing a pull request?
Hi @asafo, apologies for the delayed response.
There's no way to fork and create a module with the same name. But you could work on the same module name in local and push that into a branch.
I really like your additions. But can you please port that back into the same module name as original? I will then merge and release as a new featured parallel release.