-
Notifications
You must be signed in to change notification settings - Fork 35
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
Change prefix-name for the orchestrated pods via an environment variable/cli argument #82
Comments
Currently, the label should be added on the docker container. For example, using testcontainers-java, it would be something in the line of:
See also: #36 |
Thank you, @joyrex2001, for your response. I'm seeking a method to manage this within my pipeline template without altering the test cases directly. Could we potentially utilize Kubernetes container environment variables within Kubedock or labels at the pod holding kubedock? My goal is to transmit the pipeline job name(or its hash) as a prefix. This way, if multiple pipeline instances are running Kubedock concurrently, we can assign distinct prefixes to the pods orchestrated by each instance. Overall I want to make sure that we have no clashes with names of orchestrated pods when multiple pipelines are running with their own kubedock container in same namespace? |
This is not possible at the moment, but it makes sense to be able to configure this behaviour via an environment variable/cli argument as well. |
I added the environment variable |
Thanks @joyrex2001 for prompt action. |
I am trying to apply prefix name for all the orchestrated pods by kubedock.
Referring below -
"By default, all containers will be orchestrated using kubernetes pods. If a container has been given a specific name, this will be visible in the name of the pod. If the label com.joyrex2001.kubedock.name-prefix has been set, this will be added as a prefix to the name."
Attempts Made:
Observation:
Despite these attempts, the pods are still being created using the format kubedock-containerId.
What is the correct approach to ensure the prefix name is successfully applied to the pod-names?
The text was updated successfully, but these errors were encountered: