Add default labels to TCP resource

[ptx96]

At the moment, any reference or example related to a TCP resource is without labels;

it would be advisable to add them (statically or dynamically) in order to better filter the target resources in case of interaction with other products (e.g. velero backup and restore procedure)

[prometherion]

It seems to me we don't need any change in the code, rather, only some guidelines and best practices to share with the community.

[geoffrey1330]

@prometherion I want to pick up this issue

[prometherion]

@geoffrey1330 thanks, let's wait first the feedback from @ptx96 since the issue/feature request is unclear in the objects and the desired goal.

[ptx96]

We should add a default label to the TCP resource inside every TCP yaml definition we wrote in the docs / samples section;

for example:

https://kamaji.clastix.io/getting-started/#tenant-control-plane

should be:

cat > ${TENANT_NAMESPACE}-${TENANT_NAME}-tcp.yaml <<EOF
apiVersion: kamaji.clastix.io/v1alpha1
kind: TenantControlPlane
metadata:
  name: ${TENANT_NAME}
  namespace: ${TENANT_NAMESPACE}
  labels:
    tenant.clastix.io: ${TENANT_NAME}
spec:
  dataStore: default
  controlPlane:
[...]

in order to be ready "out of the box" for side apps that use --selector logic;
here we have an example for velero:

https://velero.io/docs/v1.4/resource-filtering/#--selector

---

Thank you for offering to contribute @geoffrey1330 !

The files of interest for the issue should be as follows:

docs/content/getting-started.md
docs/content/guides/kamaji-azure-deployment.md
docs/content/guides/upgrade.md
docs/content/reference/benchmark.md
config/samples/kamaji_v1alpha1_tenantcontrolplane_konnectivity.yaml
config/samples/kamaji_v1alpha1_tenantcontrolplane.yaml
config/samples/kamaji_v1alpha1_tenantcontrolplane_kine.yaml
config/samples/kamaji_v1alpha1_tenantcontrolplane_additionalvolumes.yaml
config/samples/kamaji_v1alpha1_tenantcontrolplane_additionalcontainers.yaml

[geoffrey1330]

Could you please assign the issue to me