nicolaferraro commented on issue #595: Set platform as integration contexts owner URL: https://github.com/apache/camel-k/pull/595#issuecomment-480853258 Well... I'm not sure, but give my two cents.. Technically the owner relationship seems to matter to the [garbage collector](https://kubernetes.io/docs/concepts/workloads/controllers/garbage-collection/) in Kubernetes. Owning in kubernetes language means in some way that the owned object cannot live without the owner. In this case it's ok to say that both `IntegrationContext` and `Integration` cannot live without a platform. But in many cases, the owning relationship seems to indicate actual **control**. E.g. a Deployment owns a ReplicaSet that in turns owns some Pods. It means that you're not allowed to make changes to the pods or to the replica set because they're owned by someone else that controls their state. In this semantics, a Integration is not controlled by the platform in any way and users are allowed to change it. IntegrationContexts created by the users follow the same rules. IntegrationContexts created by the platform are ok to be owned by the platform itself.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
