CI: collision of chainsaw test Job ConfigMaps between different tests
While looking at the chainsaw test added in !6766 (merged) , I noticed that:
- the Job output mentions
workload-team-defs-vapwhich is a different test https://gitlab.com/sylva-projects/sylva-core/-/jobs/15989584189/artifacts/external_file/management-cluster-dump/chainsaw-test/run-chainsaw-tests-keycloak-users-groups-repo-6q45w/logs.txt - the Job ConfigMap produced for that Kustomization is the same one as for other Jobs ... we have a collision
for chainsaw-test-runner-workload-team-defs:
inventory:
entries:
- id: _chainsaw-test__Namespace
v: v1
- id: _chainsaw-test-runner-workload-team-defs_rbac.authorization.k8s.io_ClusterRole
v: v1
- id: _chainsaw-test-runner-workload-team-defs_rbac.authorization.k8s.io_ClusterRoleBinding
v: v1
- id: chainsaw-test_chainsaw-test-runner-workload-team-defs__ServiceAccount
v: v1
# -------------
- id: chainsaw-test_chainsaw-config__ConfigMap
v: v1
# -------------
- id: chainsaw-test_run-chainsaw-tests-workload-team-defs_batch_Job
v: v1for chainsaw-test-runner-keycloak-users-groups:
inventory:
entries:
- id: _chainsaw-test__Namespace
v: v1
- id: _chainsaw-test-runner-keycloak-users-groups-repo_rbac.authorization.k8s.io_ClusterRole
v: v1
- id: _chainsaw-test-runner-keycloak-users-groups-repo_rbac.authorization.k8s.io_ClusterRoleBinding
v: v1
- id: chainsaw-test_chainsaw-test-runner-keycloak-users-groups-repo__ServiceAccount
v: v1
# -------------
- id: chainsaw-test_chainsaw-config__ConfigMap
v: v1
# -------------
- id: chainsaw-test_run-chainsaw-tests-keycloak-users-groups-repo_batch_Job
v: v1