This repository was archived by the owner on Oct 28, 2024. It is now read-only.
⚠️ Moving Control Plane Provider and Infra Provider #57
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR separates the Control Plane Provider from the Infrastructure provider allowing them to be deployed separately which will help us down the line if we end up wanting to support #44 but also helps us to better the experience for
clusterctl
once we get our first release out to help fulfill #54.Testable Steps
Create
kind
clusterInstall
cert-manager
Clone CAPI and Deploy Dev release
We need to deploy the unreleased version of CAPI for
v1alpha4
API support.Create Docker Images, Manifests and Load Images
Deploy CAPN
Apply Sample Cluster
Get
KUBECONFIG
clusterctl get kubeconfig cluster-sample > kubeconfig
Port Forward
In a separate shell, you will need to
port-forward
the apiserver service.Connect to Cluster
To use the
KUBECONFIG
without modification we first need to setup a host record for theapiserver service name, to do this we can append that to
/etc/hosts
cat /etc/hosts # Normal hosts file 127.0.0.1 cluster-sample-apiserver
Connect to the Cluster! 🎉
Related
Closes #45
Signed-off-by: Chris Hein [email protected]