-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workflows built in SFCP namespace always use latest tag for builder image #486
Comments
Signed-off-by: Ricardo Zanini <zanini@redhat.com>
@domhanak Actually, the |
@ricardozanini Yea apologies for that, what I meant is simply a new NS on a cluster that has SFCP set. Will take a look. |
…pache#487) Signed-off-by: Ricardo Zanini <zanini@redhat.com>
Describe the bug
Problem seems to be rooted in SFCP not using values from:
ConfigMap of operator -> controllers_cfg.yaml
and just use the default builder configmap dockerfile.
Expected behavior
SFCP workflows use the builder image from controllers-config ConfigMap of operator -> controllers_cfg.yaml
Actual behavior
SFCP workflows use the builder image from builder configmap
How to Reproduce?
Output of
uname -a
orver
No response
Golang version
No response
Operator-sdk version
No response
SonataFlow Operator version or git rev
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: