You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A bit of a goofy idea, and would only be as a "wouldn't it be cool if" kind of feature.
Expected Behavior
When doing kubectl describe, it would be nice if the Docker image name was a link to the registry.
This can be done via the OSC 8 escape sequence.
For example, the "Image" part of:
$ kubectl describe pods...Containers: trustmanager: Container ID: containerd://b0151dd97058ba40968eec66d024795c762fba9365c106518f97d1b1c6183684 Image: quay.io/jetstack/trust-manager:v0.8.0 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ this here
There's no way to really guess how to construct the links, so there's going to need some heuristic-based hardcoding (and potentially configurable later via ~/.kube/color.yaml file).
To begin with, it should know how to convert the following images to the following URLs:
Some links can't go directly to the exact tag or digest as you need more information to build the link than what you have available (such as Docker Hub links that need both image tag and digest to construct the URL). There can be future improvements to kubecolor that make this more exact.
Should also handle no tag as :latest
Current Behavior
Just displayed as (colored) text.
Context
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.
A bit of a goofy idea, and would only be as a "wouldn't it be cool if" kind of feature.
Expected Behavior
When doing
kubectl describe
, it would be nice if the Docker image name was a link to the registry.This can be done via the OSC 8 escape sequence.
For example, the "Image" part of:
There's no way to really guess how to construct the links, so there's going to need some heuristic-based hardcoding (and potentially configurable later via
~/.kube/color.yaml
file).To begin with, it should know how to convert the following images to the following URLs:
quay.io/jetstack/trust-manager:v0.8.0
quay.io/jetstack/trust-manager@sha256:e45773dbc05105a19e0750fdb2524ba056ae1568f37b7ed99d42ad64264734fc
docker.io/grafana/grafana:10.4.0
docker.io/grafana/grafana@sha256:f9811e4e687ffecf1a43adb9b64096c50bc0d7a782f8608530f478b6542de7d5
grafana/grafana:10.4.0
grafana/grafana@sha256:f9811e4e687ffecf1a43adb9b64096c50bc0d7a782f8608530f478b6542de7d5
nginx:alpine
nginx@sha256:31bad00311cb5eeb8a6648beadcf67277a175da89989f14727420a80e2e76742
ghcr.io/riskident/jelease:v0.6.2
ghcr.io/riskident/jelease@sha256:927d3b2af3f4528053ac541498482f1e39a6912aa8f8c289a2cc1e4db53503fd
gcr.io/etcd-development/etcd:v3.5.12
gcr.io/etcd-development/etcd@sha256:cebe24b890641de3e7ff8a640c4597bdda321090c29f4dedcedaa8cadbbe08e1
docker.elastic.co/elasticsearch/elasticsearch:7.12.1
docker.elastic.co/elasticsearch/elasticsearch@sha256:561bf27aa989803bfbac48ebd48e32daadb4215cf7940c599a62c13f225427fa
Some links can't go directly to the exact tag or digest as you need more information to build the link than what you have available (such as Docker Hub links that need both image tag and digest to construct the URL). There can be future improvements to kubecolor that make this more exact.
Should also handle no tag as
:latest
Current Behavior
Just displayed as (colored) text.
Context
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.
More info about OSC 8, and list of terminal support: https://github.com/Alhadis/OSC8-Adoption/
The text was updated successfully, but these errors were encountered: