-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simplify CAPIProvider
example and replace clusterctl mentions
#168
Simplify CAPIProvider
example and replace clusterctl mentions
#168
Conversation
Signed-off-by: Danil-Grigorev <[email protected]>
clusterctl generate works in presence of core CAPI provider, which is provisioned with `clusterctl init`. This functionality overlaps with turtles core CAPIProvider, and may cause issues. Signed-off-by: Danil-Grigorev <[email protected]>
@@ -131,7 +128,7 @@ kubectl create -f cluster1.yaml | |||
:::tip | |||
After your cluster is provisioned, you can check functionality of the workload cluster using `clusterctl`: | |||
```bash | |||
clusterctl describe cluster cluster1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow, this was an ugly one. Good catch!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Danil-Grigorev
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small nit, otherwise LGTM
Co-authored-by: Furkat Gofurov <[email protected]>
CAPIProvider
resource configuration for quick-start with AKS.clusterctl
in favor ofenvsubst
andcurl
to remove requirement forclusterctl init
execution in the user clusters to runclusterctl generate
later.