Skip to content
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.

Sign up for GitHub

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: update supported python version example #2494

Merged
merged 2 commits into from
Jul 28, 2023
Merged

control-service: update supported python version example #2494

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
46793cf
control-service: update supported python version example
mivanov1988 Jul 28, 2023
9fa6466
Merge main into person/miroslavi/update-supported-python-versions-exa…
github-actions[bot] Jul 28, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions examples/supported-python-versions-example/control-service-setup/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,6 +74,25 @@ deploymentSupportedPythonVersions:
deploymentDefaultPythonVersion: "pre-release"
```

If you want to assign a separate job builder for each Python version, this can be accomplished by including the
`builderImage` optional property:

```yaml
deploymentSupportedPythonVersions:
3.9-release:
baseImage: "registry.hub.docker.com/versatiledatakit/data-job-base-python-3.9:latest"
vdkImage: "registry.hub.docker.com/versatiledatakit/quickstart-vdk:release"
builderImage: "registry.hub.docker.com/versatiledatakit/job-builder:release"
3.9-pre-release:
baseImage: "registry.hub.docker.com/versatiledatakit/data-job-base-python-3.9:latest"
vdkImage: "registry.hub.docker.com/versatiledatakit/quickstart-vdk:pre-release"

deploymentDefaultPythonVersion: "3.9-pre-release"
```

The presence of the `builderImage` property is OPTIONAL; if it is not provided, the Control Service will automatically
default to the `deploymentBuilderImage`.

> NOTE: The full content of the values.yaml file would depend on the configuration
> of the Control Service. If you use a custom Control Service instance, you can
> add the above code directly to the values.yaml file used to deploy the Service.
Expand Down