Skip to content

Commit

Permalink
Update README file
Browse files Browse the repository at this point in the history
  • Loading branch information
Karthik-K-N committed Apr 12, 2022
1 parent 8c72d59 commit ee0b35d
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 32 deletions.
2 changes: 1 addition & 1 deletion docs/book/src/SUMMARY.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@
- [Power VS Cluster](./topics/powervs/index.md)
- [Prerequisites](./topics/powervs/prerequisites.md)
- [Creating a cluster](./topics/powervs/creating-a-cluster.md)
- [External Cloud Provider](./topics/powervs/external-cloud-provider.md)
- [Creating a cluster with External Cloud Provider](./topics/powervs/external-cloud-provider.md)
- [Developer Guide](./developer/index.md)
- [Rapid iterative development with Tilt](./developer/tilt.md)
- [Guide for API conversions](./developer/conversion.md)
Expand Down
33 changes: 2 additions & 31 deletions docs/book/src/topics/powervs/external-cloud-provider.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,7 @@
- The [external cloud provider template](https://github.com/kubernetes-sigs/cluster-api-provider-ibmcloud/blob/main/templates/cluster-template-powervs-cloud-provider.yaml) will use [clusterresourceset](https://cluster-api.sigs.k8s.io/tasks/experimental-features/cluster-resource-set.html) and will create the necessary config map, secret and roles to run the cloud controller manager
- As a prerequisite set the `powervs-provider-id-fmt` [flag](https://github.com/kubernetes-sigs/cluster-api-provider-ibmcloud/blob/64c9e1d17f1733c721f45a559edba3f4b712bcb0/main.go#L220) with value v2

### Deploy Power VS cluster with IBM Power VS cloud provider based on required usecase

### UseCase 1: Deploy cluster with node initialization support
### Deploy Power VS cluster with IBM Power VS cloud provider

```
IBMPOWERVS_SSHKEY_NAME="my-pub-key" \
Expand All @@ -31,31 +29,4 @@
```

When the cluster is created with above parameters, The IBM Power VS cloud provider will
1. Initialize the node by fetching appropriate VM information such as IP, zone, region from Power Cloud.

### UseCase 2: Deploy cluster with node initialisation and cloud load balancer support
```
IBMPOWERVS_SSHKEY_NAME="my-pub-key" \
IBMPOWERVS_VIP="192.168.151.22" \
IBMPOWERVS_VIP_EXTERNAL="158.175.162.22" \
IBMPOWERVS_VIP_CIDR="29" \
IBMPOWERVS_IMAGE_NAME="capibm-powervs-centos-8-1-22-4" \
IBMPOWERVS_SERVICE_INSTANCE_ID="7845d372-d4e1-46b8-91fc-41051c984601" \
IBMPOWERVS_NETWORK_NAME="capi-test-3" \
IBMACCOUNT_ID="ibm-accountid" \
IBMVPC_RESOURCE_GROUP="powervs-resource-group-name" \
IBMVPC_SUBNET_NAMES="subnet-name" \
IBMVPC_NAME="vpc-name" \
IBMVPC_REGION="vpc-region" \
IBMPOWERVS_REGION="powervs-region" \
IBMPOWERVS_ZONE="powervs-zone" \
BASE64_API_KEY=$(echo -n $IBMCLOUD_API_KEY | base64) \
clusterctl generate cluster ibm-powervs-1 --kubernetes-version v1.22.4 \
--target-namespace default \
--control-plane-machine-count=3 \
--worker-machine-count=1 \
--from ./cluster-template-powervs-cloud-provider.yaml | kubectl apply -f -
```
When the cluster is created with above parameters, The IBM Power VS cloud provider will
1. Initialize the node by fetching appropriate VM information such as IP, zone, region from Power Cloud.
2. Create a LoadBalancer in IBM VPC whenever there is service of type LoadBalancer is created in cluster.
1. Initialize the node by fetching appropriate VM information such as IP, zone, region from Power Cloud.

0 comments on commit ee0b35d

Please sign in to comment.