-
Feature
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
BU Product Work
-
False
-
-
False
-
100% To Do, 0% In Progress, 0% Done
-
6
-
0
Feature Overview (aka. Goal Summary)
Enable support for ImageTagMirrorSet (ITMS) in HyperShift to allow tag-based image proxying. This feature bridges the gap in functionality for workloads that rely on image tags, aligning HyperShift with OpenShift (OCP) capabilities introduced in version 4.13, addressing growing customer demand for tag-based image pulls.
Goals (aka. expected user outcomes)
- Users can configure ImageTagMirrorSet in HostedCluster CRs for HyperShift.
- Changes to ImageTagMirrorSet propagate to /etc/containers/registries.conf on worker nodes in hosted clusters.
- Enhance support for workloads and operators pulling images by tags (e.g., community and certified operators).
Requirements (aka. Acceptance Criteria):
Deployment considerations | List applicable specific needs (N/A = not applicable) |
Self-managed, managed, or both | Self-managed |
Classic (standalone cluster) | |
Hosted control planes | Yes |
Multi node, Compact (three node), or Single node (SNO), or all | |
Connected / Restricted Network | |
Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) | |
Operator compatibility | |
Backport needed (list applicable versions) | |
UI need (e.g. OpenShift Console, dynamic plugin, OCM) | |
Other (please specify) |
Use Cases (Optional):
- Disconnected Environment: Operators in air-gapped clusters need ITMS for tag-based image pulls (e.g., certified operator installation).
- Custom Mirror Configuration: Cluster Service Consumers administrators set up ITMS to map custom registries to specific tags.
Background
HyperShift currently supports ImageDigestMirrorSet (IDMS) but lacks functionality for tag-based mirrors (ImageTagMirrorSet). This limitation affects customers using workloads or operators that rely on tags for image pulls. The demand for ITMS arises due to the reliance on tags in some deployment scenarios, particularly in disconnected environments.
Documentation Considerations
- Highlight scenarios where ITMS should not be used (e.g., mutable tags in critical workloads).
- Include ITMS configurations for disconnected Environments
- is depended on by
-
RFE-6335 HyperShift should allow images to be pulled using tags and support ITMS.
- Under Review