Can't add label groups on a cron job

Questions and Answers Web UI
1

On Qovery’s console I’m trying to add a label group to a CronJob.

I select the label group, then click “save”, it shows a confirmation “service updated” but when I refresh the page, the label group is gone.

Debugging the network shows that the PUT request on https://api.qovery.com/job/:jobId has a payload with:

  labels_groups: []
2

Hello @wewelll,

Thanks for the report, I tried to reproduce this issue on our side but I was unable to.
Could you please send me the link to your service?

Best,
Rémi

3

The link to my service is : https://console.qovery.com/organization/fcdd956b-60bb-4d2c-906c-80d7ac3bb53d/project/93eaf665-f67d-45ad-b5e7-7f9fa3dbca46/environment/36a0966f-f74a-49cf-944a-e2702860c6af/application/2bed8e8f-ebbe-4efb-9e7e-4286401b24f3/settings/general

I’m trying to add a label for the Datadog Admission Controller :
admission.datadoghq.com/enabled: "true"

4

Thanks for sharing,

I apologize for the issue. Indeed we had a problem with the Cron Job as a container. I’ve added a release with the fix, so it should be fine now.

Please let me know if you encounter any other issues!

Best,
Rémi

6

Thank you @Remi_Bonnet for your fix.

Now when I save the CronJob, the label stays in the console, but it seems that the label is not propagated to the Pod resource.

I have checked the generated YAML of the pod on K9s and I can’t see the datadog label on it …

7

In the CronJob resource, I can see the label in spec.jobTemplate.metadata.labels, but I think it should also be added to spec.jobTemplate.spec.template.metadata.labels

8

Hello @wewelll
Indeed, an issue has been identified and fixed on our side.
The fix will be available in the next release of our engine in the coming days.

Regards,
Fabien

9

Hello @wewelll
The fix has been released.
Can you retry and check it is ok on your side?

Thank you.

Regards,
Fabien