outdated
outdated copied to clipboard
Kubectl plugin to find and report outdated images running in a Kubernetes cluster
To use the outdated information in other systems, provide optional JSON output format. You can give an optional `--output=json` flag and the output will be in JSON format like this...
In https://quay.io/repository/jetstack/cert-manager-cainjector, there are many other tags in addition to semver tags. Example output: ``` Image Current Latest Behind quay.io/jetstack/cert-manager-cainjector v1.4.0 8.0.0-b0a39a5 7 ``` There's no actual `8.0.0-b0a39a5` tag, but...
Is there any option to validate images that are coming from private registries?
The outdated plugin doesn't work on an M1 laptop, we need an darwin/m1 build published
In the repo i see that the azure auth provider was added but i don't see any new releases which includes this.
In the demo video it seems that this tool supposed to be able to fetch the latest/behind data in seconds per image. On my cluster, it takes **minutes** per image,...
This looks to be more updated and will allow us to support non-Docker (i.e. OCI) registries
This should be easier to do in a script for automation, including when running in CI
Running outdated on my cluster, with a very light load, I get: ``` index.docker.io/ceph/ceph v14.2.0-20190410 Cannot access registry: failed to read docker config: open /Users/markpundsack/.docker/config.json: too many open files ```
I try the plugin on a cluster. It seems my cert-manager deployment is OK, but according to the registry a new version is available : ``` $ kubectl outdated version...