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
Right now we can configure the image for all the "operands" with parameters to the CR, but the workers deployed by the orchestrator are always bound to the orchestrator's tag.
This is a problem if the orchestrator is tagged differently or pulled using a sha so we should allow users to specify image strings for the manageiq-base-worker, manageiq-webserver-worker and manageiq-ui-worker images through the operator.
This will also require some changes on the manageiq side to pull the env vars and use them when deploying the workers.
This will allow advanced users more flexability in how
the worker images are specified. Specifically this allows
changing the image name itself and also allows for digest-based
identifiers (rather than using only tags)
Applies to ManageIQ/manageiq-pods#557
This will allow advanced users more flexability in how
the worker images are specified. Specifically this allows
changing the image name itself and also allows for digest-based
identifiers (rather than using only tags)
Applies to ManageIQ/manageiq-pods#557
carbonin
added a commit
to carbonin/manageiq-pods
that referenced
this issue
Jun 19, 2020
Previously a user was not able to change the actual image name for
the worker images nor were they able to deploy with anything other
than the namespace and tag deployed for the orchestrator.
This gives a bit more flexability in that one image can be replaced
at a time and also allows a user to specify an image ref with a
digest rather than a tag
FixesManageIQ#557
Right now we can configure the image for all the "operands" with parameters to the CR, but the workers deployed by the orchestrator are always bound to the orchestrator's tag.
This is a problem if the orchestrator is tagged differently or pulled using a sha so we should allow users to specify image strings for the
manageiq-base-worker
,manageiq-webserver-worker
andmanageiq-ui-worker
images through the operator.This will also require some changes on the manageiq side to pull the env vars and use them when deploying the workers.
cc @Fryguy
The text was updated successfully, but these errors were encountered: