[Feature] Cloned Mode

Cloned Mode - ClusterSpec & Profile

Cloned Mode enables clusters to be built from a ClusterSpec, and/or a Profile and operate from a git repository structure that is 100% independent of the base clusterSpec, Profile, and the Profiles referenced Bundles.

Why Clone?

• Cloning allows for rapid experimentation of new clusterSpec changes, Profile changes and Bundles without impacting other clusters
• Cloning allows for snowflakes that still comply with declarative management
• Cloning enables users to have their own cluster and administrators can maintain control of the clusters configuration. Resulting in less "well it works on my cluster" syndrome *Cloning enables troubleshooting on identical clusters without the worry or impacting the production configuration

How does Cloned Mode work?

When a cluster is created using cloned mode the clusterSpec and the Profile are duplicated/cloned in Git. Arlon maintains the Profile as an object that no other cluster can use, all the bundles in the profile are cloned. Lastly, the clusterSpec is also cloned. In Git a user can expect to see the following

|-- /myGit/myClusters/
  |---> ClonedCluster1/
   |----> ClusterSpec/
     ------> myClonedSpec
   |----> Profile/
     ------> myClonedProfile
   |----> clonedBundles/
     ------> App1
     ------> App2
     ------> RBAC
     ------> Network Policy