-
Notifications
You must be signed in to change notification settings - Fork 59
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
control-service: ability to set builder image per python version #2490
control-service: ability to set builder image per python version #2490
Conversation
…rsion Why Currently, we don't have the ability to set different builder image per supported Python version. This prevents us from VDK deployment which consists of regular and secure data job base images, since both builder implementations differ. What Introduced optional property to the supported python versions called `builderImage`: ``` {3.9: {vdkImage: 'ghcr.io/versatile-data-kit-dev/versatiledatakit/quickstart-vdk:release', baseImage: 'ghcr.io/versatile-data-kit-dev/versatiledatakit/data-job-base-python-3.9:latest', builderImage: 'ghcr.io/versatile-data-kit-dev/versatiledatakit/job-builder:1.3.3'}}" ``` The property is optional if it is not present CS will default to the `datajobs.builder.image=registry.hub.docker.com/versatiledatakit/job-builder:1.3.3`. Testing Done: Unit and IT tests. Signed-off-by: Miroslav Ivanov [email protected]
…rsion Why Currently, we don't have the ability to set different builder image per supported Python version. This prevents us from VDK deployment which consists of regular and secure data job base images, since both builder implementations differ. What Introduced optional property to the supported python versions called `builderImage`: ``` {3.9: {vdkImage: 'ghcr.io/versatile-data-kit-dev/versatiledatakit/quickstart-vdk:release', baseImage: 'ghcr.io/versatile-data-kit-dev/versatiledatakit/data-job-base-python-3.9:latest', builderImage: 'ghcr.io/versatile-data-kit-dev/versatiledatakit/job-builder:1.3.3'}}" ``` The property is optional if it is not present CS will default to the `datajobs.builder.image=registry.hub.docker.com/versatiledatakit/job-builder:1.3.3`. Testing Done: Unit and IT tests. Signed-off-by: Miroslav Ivanov [email protected]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
Please make sure to also update the example at https://github.com/vmware/versatile-data-kit/tree/main/examples/supported-python-versions-example/control-service-setup
You can do that now or in a follow-up PR.
Thanks for the reminder! |
…er-python-version
…er-python-version
Why
Currently, we don't have the ability to set different builder image per supported Python version. This prevents us from VDK deployment which consists of regular and secure data job base images, since both builder implementations differ.
What
Introduced optional property to the supported Python versions called
builderImage
:The property is optional if it is not present CS will default to the
datajobs.builder.image=registry.hub.docker.com/versatiledatakit/job-builder:1.3.3
.Testing Done:
Unit and IT tests.
Signed-off-by: Miroslav Ivanov [email protected]