feat(tenant): add label with tenant name for each tenant

[oliverbaehler]

Initial efforts for the implementation of:
projectcapsule/capsule-proxy#328

[netlify]

✅ Deploy Preview for capsule-documentation canceled.

Name	Link
🔨 Latest commit	c44aba2
🔍 Latest deploy log	https://app.netlify.com/sites/capsule-documentation/deploys/6566636bd2ea970008683723

[prometherion]

I dunno why we would need a new recipe, lint when we already have golint.

[prometherion]

We should keep the already existing labels, otherwise, we're gonna overwrite the user ones.

[oliverbaehler]

I don't agree, using capsule specific labels seems like we are creating just a technical dept for the future. You could say the same thing here, no?
#911

I would prefer using a well-known label here as well.

[prometherion]

I didn't explain properly, here.

Let's say I have a Tenant:

NAME    STATE    NAMESPACE QUOTA   NAMESPACE COUNT   NODE SELECTOR   AGE
solar   Active                     0                                 15s

I'm labelling it for several reasons:

$: kubectl label tnt solar my-label=value
tenant.capsule.clastix.io/solar labeled

$: kubectl get tnt --show-labels
NAME    STATE    NAMESPACE QUOTA   NAMESPACE COUNT   NODE SELECTOR   AGE   LABELS
solar   Active                     0                                 49s   my-label=value

With the tnt.SetLabels provided by your code we're gonna overwrite the user labels, such as my-label.

[oliverbaehler]

@prometherion Ah right, sorry for the missunderstanding!

[oliverbaehler]

Tried to play around with pre-commit. But it's annoying. Removed the target.

[oliverbaehler]

I don't agree, using capsule specific labels seems like we are creating just a technical dept for the future. You could say the same thing here, no?
#911

I would prefer using a well-known label here as well.

[prometherion]

Tests are failing but they should have been fixed with the latest commits on main, may I ask you to rebase, please?

[oliverbaehler]

@prometherion I have extend it with a webhook, otherwise there could be potential for escalation between the time of an update and a reconcile. I hope that's alright.