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
similar to #278 it would be nice to create a step to process all the sources in config-root to find all the image tags in every Deployment / Pod etc and create a YAML file with all the images (and which resources they are referenced from)
this would help folks grok what images are needed; what registries are used, what versions are used etc
folks could use this data to then make further tools such as:
ensuring all images are accessible
mirroring / replicating images to other registries to support air gapped on premise type repositories or to work around locations which cannot access specific registries. e.g. in China its often hard to access gcr.io
The text was updated successfully, but these errors were encountered:
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten
similar to #278 it would be nice to create a step to process all the sources in
config-root
to find all the image tags in everyDeployment / Pod
etc and create a YAML file with all the images (and which resources they are referenced from)this would help folks grok what images are needed; what registries are used, what versions are used etc
folks could use this data to then make further tools such as:
The text was updated successfully, but these errors were encountered: