Paul Sweeney

I'll admit I've not a great understanding of the CRD alpha/beta/v1 versioning - by which I mean how does the consumer identify breaking/non-breaking changes, patches etc? Using it would obviously...

So @FogDong / @linaking-guidewire I get how v1alpha/v1beta/v1 works when taking a new definition through concept to full "v1" implementation. But how does this work if we are adding a...

Thanks @fboismenu . I'm mostly in agreement on your points. One thing I'd like to note though is the proposal here to _allow_ rollout of new definition versions (my emphasis)....

Thanks for reminding me about this @dhiguero, I've got sidetracked lately. Yes the scenario you have raised - of having multiple versions of the same definition (might be component, trait...

IMHO auto update should never be the default, particularly in live. If others want it then fine let them as an option but I wouldn't want to see auto update...

Ah ok, so if I understand, your proposal to auto-update only applies if the developer has _not_ specified a version number. In this case they would get patch and new...

Thanks @oanasc, a good thing to raise. My only thought is what behaviour would we get if the cluster config version is changed? For user-changed version the update would only...

Actually, I'm not proposing the auto-upgrade, but others have 🙂. I do see that others may want it, particularly in dev environments, so happy to go along provided it's configurable...

> Configuring the security-context in K8s can be quite intricate, requiring a certain level of expertise to get it right. We should consider the use-case carefully to make this trait....

Yeah I'll add this 🙂 - [[Feature] Support for explicit versioning of definitions #6435](https://github.com/kubevela/kubevela/issues/6435 )