Hey everyone! We're in the process of migrating a large legacy application to Kubernetes, and it will be used across various sites with different production environments. Given that we have some unique requirements that standard features won't cover, we're thinking about creating a single version or 'core' of the software. My question is: is it correct to refer to this as a "core" and what we will have at each site as "instances"? Additionally, what are the best practices for implementing this setup? How are others in the industry handling similar scenarios? Thanks in advance for your insights!
1 Answer
This sounds like the exact problem Kustomize was designed to solve! It's perfect for managing different Kubernetes configurations for each deployment.
Exactly! Using Kustomize for Kubernetes management lets you tailor deployments easily, but the core functionality of your software still needs to be developed properly.