XIGXOG

KubeFox distills deployments to unique components only. Your teams deploy at the App level. If an App comprises 40 components and 3 components are changed for a new version, then only those 3 components will be deployed. From a developer's perspective, they are running a different version fo the App. From a provisioning perspective, you're supporting those two versions on the same cluster with the minimum number of resources... KubeFox can support multiple versions of an App simultaneously on the same cluster, but with the minimum number of components (defined as unique components only). It can achieve this because it routes requests dynamically at runtime. Technical gobblygok aside, that means that KubeFox can use unchanged components for different versions of an App - all the while making it appear that each version is running in isolation on the cluster... One school of thought is that DevOps is threatened by KubeFox. While it's true that KubeFox handles many DevOps tasks..