Image name as selector: implementation in odo #6677
Labels
area/devfile-spec
Issues or PRs related to the Devfile specification and how odo handles and interprets it.
kind/user-story
An issue of user-story kind
priority/High
Important issue; should be worked on before any other issues (except priority/Critical issue(s)).
sprint demo
Indicates an issue for which a demo should be recorded and presented at the end of the sprint.
Milestone
/kind user-story
User Story
As an odo user, I want
odo
to push images from Image Components to a given registry and use that for all matching Kubernetes/OpenShift components manifests, without having to hardcode that information into my Devfile, so that I can keep my devfile portable.See #6565 and devfile/api#985 (comment) for more context.
Acceptance Criteria
odo dev and odo deploy commands should have a flag that allows users to specify image registry, this overrides the global configuration (preference)odo dev
,odo deploy
andodo build-images
should push the images to the specified registryLinks
imageName
in Image component as selector #6565imageName
as a selector in the Devfile library #6676The text was updated successfully, but these errors were encountered: