squakez commented on PR #3325: URL: https://github.com/apache/camel-k/pull/3325#issuecomment-1144515725
Thanks for the feedback, much appreciated!! > * What if the dev namespace uses a local operator but the production depends on a cluster operator (or vice versa)? Is such promotion not allowed? I think it still can be done. The idea is that we *copy* the Integration spec plus the container which was tested and validated in a previous stage. I think the destination operator should be still able to cope with that. > * Do we need to check user's privileges for the target namespace? Or is it ok to let it fail if they are not permitted? We may understand which is the best ux there. If I am not wrong, the client we use to interact with the cluster is inheriting privileges from the user who has performed the login. I guess in a very first iteration we can let it fail, and add a check for valid permission in a later stage if we want. > * Users might want to transform some labels (or annotations) depending on the types of envs (namespaces). Should we provide such feature as well? Yeah, that is something we should analyze better. I've already thought we should check for various resources in the destination namespace. We should include also some parameter in order to transform the "typical" resources bound to an environment (annotations, envs, affininity/tolerations, etc...). -- 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. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
