-
Notifications
You must be signed in to change notification settings - Fork 13
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
Helm quick-start guide for operator, turtles and rancher #12
Helm quick-start guide for operator, turtles and rancher #12
Conversation
Signed-off-by: Danil Grigorev <[email protected]>
… components Signed-off-by: Danil Grigorev <[email protected]>
Signed-off-by: Danil Grigorev <[email protected]>
Signed-off-by: Danil Grigorev <[email protected]>
58e64de
to
148e7e3
Compare
Signed-off-by: Danil Grigorev <[email protected]>
148e7e3
to
ec8b0c5
Compare
1. Installing in in the same cluster as the rancher manager. | ||
|
||
Recommended path of installation for the operator is by using helm. To install it in your cluster you need to add repository first: |
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.
What do you think to covering how to install it via the Rancher Manager UI as well?
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.
I think this is already covered in #19
docs/getting-started/intro.md
Outdated
| Name | Version | Details | | ||
| ------------------------ | ---------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | |
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.
Also i think we need a banner saying that this is for early adopters only at this point.
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.
Added a mention of early adopters contact in the table, should it lead somewhere specific?
9d39ffc
to
4bc0010
Compare
Signed-off-by: Danil Grigorev <[email protected]>
Signed-off-by: Danil Grigorev <[email protected]>
4bc0010
to
da3f412
Compare
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.
Looking good @Danil-Grigorev 🎉
8d4d87c
to
2498461
Compare
This section describes how an infrastructure provider such as `Azure` could be added using `Cluster API Operator`. | ||
|
||
### Installing Azure Infrastructure Provider |
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.
should we refer to the capi operator docs instead of duplicating it? My concern is, keeping this up-to-date with capi operator docs might be challenging in the future
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.
We can always pin it to a version of the operator docs to use, and the docs are describing a fixed state of some release of operator and turtles IMO. Additionally the value of the documentation is in simple access to the most common use cases in a single unified location. We may explore some better documentation options for the CAPI Operator, as a single README.md file is quite inconvenient to always refer to. It could clearly be separated into multiple sections.
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.
+1 for deduplicating
0c452fc
to
0d490e5
Compare
- Add secrions for the CAPI operator installation as a dependency Signed-off-by: Danil Grigorev <[email protected]>
0d490e5
to
217f9d1
Compare
This section describes how an infrastructure provider such as `Azure` could be added using `Cluster API Operator`. | ||
|
||
### Installing Azure Infrastructure Provider |
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.
+1 for deduplicating
a79f0c7
to
95aa333
Compare
95aa333
to
82dd05b
Compare
Signed-off-by: Danil Grigorev <[email protected]>
82dd05b
to
04615c7
Compare
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.
Lets get this in. We can they do a complete review of all the docs
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.
Few suggestions for the future reference when we re-iterate over
This section describes how to install `Cluster API Operator` in the Kubernetes cluster. | ||
|
||
## Installing CAPI and providers |
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.
## Installing CAPI and providers | |
## Installing Cluster API (CAPI) and providers |
|
||
### Install manually with Helm (alternative) | ||
To install `Cluster API Operator` with version `1.4.6` of the `CAPI` + `Docker` provider using helm, follow these steps: |
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.
I think it is worth mentioning why we are using specific CAPI version, v1.4.6 in this case and later versions of it can be used in the future due to some limitations of the Rancher ?
helm repo add capi-operator https://kubernetes-sigs.github.io/cluster-api-operator | ||
``` | ||
2. Update the Helm repository by running the following command: |
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.
2. Update the Helm repository by running the following command: | |
2. Update the Helm repository: |
helm repo update | ||
``` | ||
3. Install the `Cluster API Operator` using the following command, which will also install `cert-manager`: |
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.
3. Install the `Cluster API Operator` using the following command, which will also install `cert-manager`: | |
3. Install the `Cluster API Operator`, which will also install `cert-manager`: |
--timeout 90s --wait # Core Cluster API with kubeadm bootstrap and control plane providers will also be installed | ||
``` | ||
*Note: `cert-manager` is a hard requirement for CAPI and `Cluster API Operator`* |
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.
*Note: `cert-manager` is a hard requirement for CAPI and `Cluster API Operator`* | |
*Note: `cert-manager` is a hard requirement for `CAPI`and `Cluster API Operator`* |
``` | ||
|
||
The `infrastructure` flag is set to `docker:v1.4.6;azure:v1.4.6`, representing the desired provider names. This means that the `Cluster API Operator` will install and manage multiple provider systems, `Docker` and `Azure` respectively, with versions `1.4.6` specified. |
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.
The `infrastructure` flag is set to `docker:v1.4.6;azure:v1.4.6`, representing the desired provider names. This means that the `Cluster API Operator` will install and manage multiple provider systems, `Docker` and `Azure` respectively, with versions `1.4.6` specified. | |
The `infrastructure` flag is set to `docker:v1.4.6;azure:v1.4.6`, representing the desired provider names. This means that the `Cluster API Operator` will install and manage multiple providers, `Docker` and `Azure` respectively, with versions `v1.4.6` specified in this example. |
*Note: In the future, we will support different deployment topologies* | ||
|
||
The recommended path of installation for the operator is by using `Helm`. To install it in the cluster, a repository should be added first: |
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.
The recommended path of installation for the operator is by using `Helm`. To install it in the cluster, a repository should be added first: | |
The recommended path of installation for the operator is by using `Helm`. To install it in the cluster, a chart repository should be added first: |
*Note: this section will be extended with additional details later* | ||
|
||
A `rancher-turtles` repository should be added first: |
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.
A `rancher-turtles` repository should be added first: | |
A `rancher-turtles` chart repository should be added first: |
### Deleting providers | ||
|
||
To remove the installed providers and all related kubernetes objects just delete the following CRs: |
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.
To remove the installed providers and all related kubernetes objects just delete the following CRs: | |
To remove the installed providers and all related Kubernetes objects, just delete the following CRs: |
|
||
# Basic Cluster API Provider Installation | ||
|
||
This section describes the basic process of installing `CAPI` providers using the operator. The `Cluster API Operator` manages five types of objects: |
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.
This section describes the basic process of installing `CAPI` providers using the operator. The `Cluster API Operator` manages five types of objects: | |
This section describes the basic process of installing `CAPI` providers using the operator. The `Cluster API Operator` manages five types of provider objects: |
Fixes #7
Fixes #5
Deployed version: https://danil-grigorev.github.io/rancher-turtles-docs