Workload Labeling Proposal

[zzxwill]

to recommend a simple way - Workload Labeling, to easily
establish connections between Workloads, Components,
AppConfigurations, and pods.

Signed-off-by: Zheng Xi Zhou [email protected]

[zzxwill]

@wonderflow I doubt whether there is a more 'strict' way for an OAM user to set the label definition.oam.dev/unique-pod after checking the corresponding WorkloadDefinition, as I think he/she might forget the label.
Besides, the one who prepares WorkloadDefinition might not know the which label pod-template-hash/controller-revision-hash will be generated for the Pod by the workload.

[wonderflow]

I suggest we create a new field in workloadDefinition.spec instead of using a label.

[wonderflow]

WorkloadDefinition is created by Platform builder

[wonderflow]

I don't like using OAM users here, it can't be understood clearly.

We general distinguish users by

• Platform builder
• Application Operator
• Application Developer

[wonderflow]

@wonderflow I doubt whether there is a more 'strict' way for an OAM user to set the label definition.oam.dev/unique-pod after checking the corresponding WorkloadDefinition, as I think he/she might forget the label.
Besides, the one who prepares WorkloadDefinition might not know the which label pod-template-hash/controller-revision-hash will be generated for the Pod by the workload.

What do you mean by saying OAM user here? If I understood you clearly, you may mean platform builder here? A platform builder won't forget anything if they are building service for their users.