Merge pull request #784 from cprivitere/doc-flavor

📖 Update flavor documentation to better explain EMLB and other VIP Manager options.

Author: k8s-ci-robot

docs/experiences/flavors.md

@@ -1,13 +1,23 @@
 # Flavors & Custom Templates
 
-## Kube-VIP
+The main use of flavors in the Cluster API Provider Packet project is to choose which type of VIP Management you'd like to use in your cluster.
+
+## VIP Choices
+
+The VIP Management choice affects what will manage the floating IP that points to your control plane nodes. We currently support:
+
+- EMLB managed
+- CPEM managed
+- Kube-VIP managed
 
 ### API Server VIP Management Choice
 
-By default CPEM will be used to manage the EIP that serves as the VIP for the api-server. Other flavors include kube-vip and Equinix Metal Load Balancer.
+By default CPEM will be used to manage the EIP that serves as the VIP for the api-server. This mode uses CPEM to manage an EIP address and assign it to one of the control plane nodes and move it as needed as nodes are created/destroyed.
 
 ### Choosing Equinix Metal Load Balancer
 
+This mode creates an Equinix Metal Load Balancer and adds the control plane nodes to an origin pool behind the load balancer.
+
 To use Equinix Metal Load Balancer, when generating the template with `clusterctl`, pass in the `--flavor emlb` flag. For example, your `clusterctl generate` command might look like the following:
 
 ```sh
@@ -22,6 +32,8 @@ clusterctl generate cluster capi-quickstart \
 
 ### Choosing Kube-VIP
 
+This mode lets Kube-VIP manage a floating EIP address by using BGP to update the routing table of the network.
+
 To use kube-vip, when generating the template with `clusterctl`, pass in the `--flavor kube-vip` flag. For example, your `clusterctl generate` command might look like the following:
 
 ```sh
@@ -50,7 +62,7 @@ The workflow triggered by that command summarized here:
 
 1. Based on the `--infrastructure` option it goes to the right repository and it
    looks for the `latest` release. At the time I am writing it is
-   [v0.3.0](gh-release-v030).
+   [v0.9.0](https://github.com/kubernetes-sigs/cluster-api-provider-packet/releases/tag/v0.9.0).
 2. `clusterctl` lookup a file called `cluster-template.yaml` from the release artifacts
 3. `clusterctl` uses `cluster-template.yaml` plus a set of environment variables
    that you can find described in the README.md to generate the cluster
@@ -84,5 +96,3 @@ automation. Here a few examples:
 
    If you want to change operating system you have to change the `OS` field
    for the `PacketMachineTemplate` resource.
-
-[gh-release-v030]: https://github.com/kubernetes-sigs/cluster-api-provider-packet/releases/tag/v0.3.0