DerekTBrown commented on PR #111: URL: https://github.com/apache/yunikorn-release/pull/111#issuecomment-1283043050
To describe the usecase a bit more; we need to be able to perform separate deployments for the infrastructure pieces (the YuniKorn scheduler) and the configuration (the queue ConfigMap in particular). There are a few reasons for this: 1. We want to release changes to the configuration at a different cadence / through a different process than the rest of the infrastructure. For instance, we want to automate the configuration of queues. In our particular case, we do this through multiple Argo applications. 2. We want to control the permissions to touch configuration and the infrastructure separately. I imagine that other users will have similar stories; they run YuniKorn as a piece of platform infrastructure, and want to be able to periodically re-deploy configuration. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
