feat: add children labels and annotations

[olevski]

closes #779

In the case of conflicts with selector labels or anything that is set on the children internally for amalthea then the value set from amalthea internally will have precendece.

/deploy

[leafty]

I think you need to re-generate the CRD, it doesn't look up to date.

[olevski]

I think you need to re-generate the CRD, it doesn't look up to date.

Yes I reran the codegen and pushed the changes.

[RenkuBot]

You can access the deployment of this PR at https://renku-ci-am-964.dev.renku.ch

[leafty]

Looks good to me, but I would merge only after we have a corresponding PR in renku-data-services which show that the template field works as intended.

[olevski]

Looks good to me, but I would merge only after we have a corresponding PR in renku-data-services which show that the template field works as intended.

So I deployed the CRD and tested manually in the CI deployment.

What I did:

• created a project
• launched a session
• changed the reconcile strategy to always
• added annotations to the template of the AmaltheaSession, they appeared in all the child resources
• added a label in the template that conflict with the selector labels, this was ignored and it was not added anywhere, the logs showed a message about the conflicting label
• added a non-conflicting label and it showed up everywhere
• removed a label from the template and it was removed in all children
• removed an annotation from the template and it was removed in all children

[olevski]

I also added tests for the label and annotation propagation in the go code.

[RenkuBot]

Tearing down the temporary RenkuLab deplyoment for this PR.