Jianbo Sun

This issue is actually the same with K8s strategicMergepatch in library at "k8s.io/apimachinery/pkg/util/strategicpatch"

> let ContainerizedWorkload controller to check if volume trait is bound with this Component, then generate child resource and patch child resource label to the workload CR. I agree, we...

> @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...

This should not be an issue as user can fulfill their config if they use non-core workloads. In this case, you could write component like this: ``` apiVersion: core.oam.dev/v1alpha2 kind:...

What about: ``` apiVersion: core.oam.dev/v1alpha2 kind: ApplicationConfiguration metadata: name: myapp spec: - component: frontend traits: - trait: apiVersion: alibaba.com/v1 kind: HPA spec: min: 10 max: 100 cpuUsage: 60 - type:...

@captainroy-hy sure, thanks!

@ryanzhang-oss 'patch' will not remove un-related fields

Hi, @Ananya-1106 Welcome! This repo is a more like libariry of OAM implementation, we suggest you to get start from [KubeVela](https://github.com/oam-dev/kubevela) and the `oam-kubernetes-runtime` lib was contained there.

I have a immature idea: ``` apiVersion: core.oam.dev/v1alpha2 kind: ApplicationConfiguration metadata: name: app spec: components: - componentName: file-storage traits: - trait: apiVersion: extended.oam.dev/v1alpha2 kind: Stateful spec: stateful: true - componentName:...

@jack0liu A better name will solve it