Avoid use of static image lists when gathering images used in deployment

[i-chvets]

Description

This issue is a derivative of #679

List of images that are used in Charmed Kubeflow deployment is required for various use cases. Some most important ones to date are scanning images for vulnerabilities and creating airgapped deployment environment.

In order to generate a list of images each repository contains image gathering script which can be used individually or as a part of workflow or another tool. The exact functionality of how images are collected differs from repository to repository. In some cases, a static list of images is hardcoded in such scripts that contains images that could not be retrieved dynamically. Those images were observed in CKF deployments and were hardcoded to facilitate progress on image scanning and airgapped deployment work items.

Static lists are not a proper way of tracking what images are referenced in final deployment, because updating of these static lists is manual process that is very likely to introduce errors.

Solution

In each repository where image gathering script contains static list of images implement dynamic way of gathering those images. If dynamic image collection is not possible add disclaimer in image gathering script explaining what are the reasons and provide link to this issue.

List of repositories in which image gathering script contains static list:

• https://github.com/canonical/knative-operators
• https://github.com/canonical/istio-operators

[i-chvets]

Changes have been made. There are no static lists in image gathering scripts. Closing.