Update docs on specifying flavors

Author: vishesh92

docs/book/src/clustercloudstack/configuration.md

@@ -4,8 +4,6 @@ The cluster configuration file can be generated by using [`clusterctl generate c
 This command actually uses [a template file][template-file] and replaces the values surrounded by `${}` with environment variables. 
 You have to set all required environment variables in advance. The following sections explain some more details about what should be configured.
 
-Note: You can also use [template files][template-file] by manually replacing values in copies of the template file.
-
 ```bash
 clusterctl generate cluster capi-quickstart \
   --kubernetes-version v1.21.3 \
@@ -14,9 +12,25 @@ clusterctl generate cluster capi-quickstart \
   > capi-quickstart.yaml
 ```
 
-Note: additional template files are provided, offering capabilities beyond the default template file.  These can be
-utilized via the *clusterctl --flavor* parameter.  Additional environment variables are often required by these templates.
-See clusterctl documentation for further details about *flavors*.
+You can also use [template files][template-file] by manually replacing values in copies of the template file.
+
+
+> **Note**
+>
+> Additional template files are provided, offering capabilities beyond the default template file.  These can be
+> utilized via the *clusterctl --flavor* parameter.  Additional environment variables are often required by these templates.
+> The following flavors are supported as of now:
+> - *managed-ssh*
+> - *ssh-material*
+> - *with-disk-offering*
+> - *with-existing-vpc-network*
+> - *with-kube-vip*
+>
+> To check the available variables for a flavor, execute the following command:
+> ```bash
+> clusterctl generate cluster capi-quickstart --flavor <flavor> --list-variables
+> ```
+> See clusterctl documentation for further details about *flavors*.
 
 In order to fetch the configuration parameters via the terminal, please install [cmk][cmk-download] and [jq][jq-download]
 
@@ -109,6 +123,9 @@ spec:
 If the network already exists, offering, gateway and netmask will be ignored.
 Similarly, if the VPC already exists, offering and cidr will be ignored.
 
+If you want to use an existing network inside a VPC, you can specify the flavor as `with-existing-vpc-network` while
+generating the cluster configuration file and set the `CLOUDSTACK_VPC_NAME` environment variable to the name of the VPC.
+
 #### CloudStack Endpoint Credentials Secret (*optional for provided templates when used with provided getting-started process*)
 
 A reference to a Kubernetes Secret containing a YAML object containing credentials for accessing a particular CloudStack 

docs/book/src/development/releasing.md

@@ -8,7 +8,9 @@
     - [gcloud][gcloud-install]
 
 2. Set up and log in to gcloud by running `gcloud init`
-> Note: In order to publish any artifact, you need to be a member of the [k8s-infra-staging-capi-cloudstack][k8s-infra-staging-capi-cloudstack] group
+> **Note**
+>
+> In order to publish any artifact, you need to be a member of the [k8s-infra-staging-capi-cloudstack][k8s-infra-staging-capi-cloudstack] group
 
 ## Creating only the docker container
 
@@ -31,7 +33,8 @@ Create the necessary release in GitHub along with the following artifacts ( foun
 - infrastructure-components.yaml
 - cluster-template*.yaml
 
-> Note:
+> **Note**
+>
 > - The `RELEASE_TAG` should be in the format of `v<major>.<minor>.<patch>`. For example, `v0.6.0`
 > - For RC releases, the `RELEASE_TAG` should be in the format of `v<major>.<minor>.<patch>-rc<rc-number>`. For example, `v0.6.0-rc1`
 > - Before creating the release, ensure that the `metadata.yaml` file is updated with the latest release information.