[clearml-agent] unrecognized arguments: --create-queue

[salucien]

Describe the bug a clear and concise description of what the bug is.

Hey everyone
When I want to create an agent through the chart, my pods are in an error state with the following error :

python3 k8s_glue_example.py --queue default --namespace default --template-yaml /root/template/template.yaml --create-queue

usage: k8s_glue_example.py [-h] [--queue QUEUE] [--ports-mode]
                           [--num-of-services NUM_OF_SERVICES]
                           [--base-port BASE_PORT]
                           [--base-pod-num BASE_POD_NUM]
                           [--gateway-address GATEWAY_ADDRESS]
                           [--pod-clearml-conf POD_CLEARML_CONF]
                           [--overrides-yaml OVERRIDES_YAML]
                           [--template-yaml TEMPLATE_YAML]
                           [--ssh-server-port SSH_SERVER_PORT]
                           [--namespace NAMESPACE] [--max-pods MAX_PODS]
                           [--use-owner-token] [--standalone-mode]
                           [--child-report-tags CHILD_REPORT_TAGS [CHILD_REPORT_TAGS ...]]

k8s_glue_example.py: error: unrecognized arguments: --create-queue

Besides crendentials and url, I did not change anything from the values.yaml file from the repo.
After testing, my values.yaml worked with chart versions 5.1.3, 5.1.4, 5.1.5 (didn't test prior) but stopped working with the 5.2.0 version.

What's your helm version?

v3.10.3

What's your kubectl version?

v1.27.2

What's the chart version?

5.2.0

Enter the changed values of values.yaml?

None

[koolvn]

+1 here

[valeriano-manassero]

Related chart update just disables by default create-queue flag. It's just a workaround until we get an updated image able to manage this flag.

[github-actions]

This issue is stale because it has been open for 4 weeks with no activity.

[github-actions]

This issue was closed because it has been inactive for 2 weeks since being marked as stale.

[github-actions]

This issue is stale because it has been open for 4 weeks with no activity.

[github-actions]

This issue was closed because it has been inactive for 2 weeks since being marked as stale.

[github-actions]

This issue is stale because it has been open for 4 weeks with no activity.