3. Clusters-in-clusters using Cluster API in CrownLabs

[KUOHANTUNG]

PR from group 3 Clusters-in-clusters using Cluster API in CrownLabs

PR open just to show our codes and Implemented functions whether is right. Have tested in local environment, including creating cluster, cni and exposed port.

The exposed way using nginx passthrough needs target port and nodeport and then certSAN certifacated just by apiserver.

It will first wait the cluster ready then export the kubeconfig file into folders then create cni. but i substitute the service address with external URL name in kubeconfig file, so need to build nginx first.

[kingmakerbot]

Hi @KUOHANTUNG. Thanks for your PR.

I am @kingmakerbot.
You can interact with me issuing a slash command in the first line of a comment.
Currently, I understand the following commands:

• /rebase: Rebase this PR onto the master branch
• /merge: Merge this PR into the master branch
• /hold: Adds hold label to prevent merging with /merge
• /unhold: Removes the hold label to allow merging with /merge
• /deploy-staging: Deploy a staging environment to test this PR (the build-all flag enables user environments building)
• /undeploy-staging: Manually undeploy the staging environment

Make sure this PR appears in the CrownLabs changelog, adding one of the following labels:

• kind/breaking: 💥 Breaking Change
• kind/feature: 🚀 New Feature
• kind/bug: 🐛 Bug Fix
• kind/cleanup: 🧹 Code Refactoring
• kind/docs: 📝 Documentation

[KUOHANTUNG]

someting i have modifed, e.g add finalizer that it will delete kubeconfigs when delete the instance, adding visualizer which can monitor the status of each worker