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
OSBS team is requesting we update env vars in our manifest files that specify multiple images/values to just specify one. This is to fall inline with their automation efforts with SHA digests. For example:
I know this format is used to support upgrades for AMQ Streams, so this issue is to discuss the feasibility/possibility of this being changed or if we should push back on the requirement. If it is possible, what should the format look like?
The text was updated successfully, but these errors were encountered:
kyguy
changed the title
Possblity of updating "pullspecs"
Possiblity of updating "pullspecs"
Apr 30, 2020
kyguy
changed the title
Possiblity of updating "pullspecs"
Possibility of updating "pullspecs"
Apr 30, 2020
As discussed offline, these changes would not be worth the incurred overhead. Looking into alternatives, for instance, using annotations to hold pull.specs for OSBS [1]. OSBS would retrieve the pull.specs from the annotations and replace all of the equivalent pull.specs listed in the CSV file with the SHA digests. The only issue is that the type of SHAs digests that are swapped in are manifest digest lists which are not supported by the OpenShift internal registry and will break our S2I feature. We need platform specific digests
OSBS team is requesting we update env vars in our manifest files that specify multiple images/values to just specify one. This is to fall inline with their automation efforts with SHA digests. For example:
I know this format is used to support upgrades for AMQ Streams, so this issue is to discuss the feasibility/possibility of this being changed or if we should push back on the requirement. If it is possible, what should the format look like?
The text was updated successfully, but these errors were encountered: