Handling Modules in Restricted Environments

[janmedrek]

Description

Restricted Environments are going to have limited access to repositories. This affects both OCI registries and Docker repositories where the images are stored.

KLM should be able to function in such an environment by having the option to configure/template registry URLs used in the module lifecycle.

Acceptance Criteria

• It is possible to configure the OCI registry for KLM
• It is possible to configure the Docker repository for KLM
• KLM will use configured repositories for fetching module manifests
• KLM can deploy modules with configured repositories

Open Questions

• Should the manifests already include Docker repository URLs? Or should it be "templatable" and filled in by the KLM when the module is processed?

Reasons

Some environments require different repository/registry configurations. Access may be limited on the network level.

Issues

Restricted Market operational readiness

• Troubleshooting Guide: KymaCR stuck during deletion #1934
• Troubleshooting Guide: General Module Trouble Shooting #1933

Implementation

• [Restricted Markets] Support Docker image localization #1858
• [Restricted Markets] Make credential selector as klm flag #1944
• [Restricted Markets] Implement Caching for Docker-Login-Secrets in KLM #1977