Update docs and bundle for v0.3.6 release

Author: tinyzimmer

Makefile

@@ -407,4 +407,4 @@ check-release:
 		echo "You must specify a VERSION for release" ; exit 1 ; \
 	fi
 
-prep-release: check-release generate manifests api-docs kvdictl-docs
+prep-release: check-release generate manifests api-docs kvdictl-docs bundle

README.md

@@ -8,11 +8,11 @@ _Except as I've continued to work on this, I've noticed this is really just a fr
 
 ---
 
-**ATTENTION:** The `helm` chart repository has been relocated (since the repo has been relocated). To update your repository you can do the following:
+**ATTENTION:** The `helm` chart repository has been moved to a [separate repo](https://github.com/kvdi/helm-charts) to tidy things up here more. To update your repository you can do the following:
 
 ```sh
-helm repo remove tinyzimmer
-helm repo add kvdi https://kvdi.github.io/kvdi/deploy/charts
+helm repo remove kvdi
+helm repo add kvdi https://kvdi.github.io/helm-charts/charts
 helm repo update
 
 helm install kvdi kvdi/kvdi  # yes, that's a lot of kvdi
@@ -67,6 +67,7 @@ I wrote up a [`CONTRIBUTING`](CONTRIBUTING.md) doc just outlining some of the st
 
   - "App Profiles" - I have a POC implementation on `main` but it is still pretty buggy
   - DOSBox/Game profiles could be cool...same as "App Profiles"
+  - ARM64 support. Should be easy, but the build files will need some shuffling.
   - UI could use a serious makeover from someone who actually knows what they are doing
 
 ## Requirements
@@ -103,7 +104,7 @@ For more complete installation instructions see the `helm` chart docs [here](dep
 The [API Reference](doc/appv1.md) can also be used for details on `kVDI` app-level configurations.
 
 ```bash
-helm repo add kvdi https://kvdi.github.io/kvdi/deploy/charts  # Add the kvdi repo
+helm repo add kvdi https://kvdi.github.io/helm-charts/charts  # Add the kvdi charts repo
 helm repo update                                              # Sync your repositories
 
 # Install kVDI
@@ -126,7 +127,7 @@ You can then create a [VDICluster](doc/appv1.md#VDIClusterSpec) object manually
 To install the manifest:
 
 ```bash
-export KVDI_VERSION=v0.3.1
+export KVDI_VERSION=v0.3.6
 
 kubectl apply -f https://raw.githubusercontent.com/kvdi/kvdi/${KVDI_VERSION}/deploy/bundle.yaml --validate=false
 ```
@@ -141,7 +142,7 @@ They can be found in the [config](config/) directory in this repository.
 Most of the time you can just run a regular helm upgrade to update your deployment manifests to the latest images.
 
 ```bash
-helm upgrade kvdi kvdi/kvdi --version v0.3.2
+helm upgrade kvdi kvdi/kvdi --version v0.3.6
 ```
 
 However, sometimes there may be changes to the CRDs, though I will always do my best to make sure they are backwards compatible. 
@@ -151,20 +152,20 @@ You can get around this by applying the CRDs for the version you are upgrading t
 For example:
 
 ```bash
-export KVDI_VERSION=v0.3.2
+export KVDI_VERSION=v0.3.6
 
 kubectl apply \
-  -f https://raw.githubusercontent.com/kvdi/kvdi/${KVDI_VERSION}/deploy/charts/kvdi/crds/app.kvdi.io_vdiclusters.yaml \
-  -f https://raw.githubusercontent.com/kvdi/kvdi/${KVDI_VERSION}/deploy/charts/kvdi/crds/desktops.kvdi.io_sessions.yaml \
-  -f https://raw.githubusercontent.com/kvdi/kvdi/${KVDI_VERSION}/deploy/charts/kvdi/crds/desktops.kvdi.io_templates.yaml \
-  -f https://raw.githubusercontent.com/kvdi/kvdi/${KVDI_VERSION}/deploy/charts/kvdi/crds/rbac.kvdi.io_vdiroles.yaml
+  -f https://raw.githubusercontent.com/kvdi/kvdi/${KVDI_VERSION}/config/crd/bases/app.kvdi.io_vdiclusters.yaml \
+  -f https://raw.githubusercontent.com/kvdi/kvdi/${KVDI_VERSION}/config/crd/bases/desktops.kvdi.io_sessions.yaml \
+  -f https://raw.githubusercontent.com/kvdi/kvdi/${KVDI_VERSION}/config/crd/bases/crds/desktops.kvdi.io_templates.yaml \
+  -f https://raw.githubusercontent.com/kvdi/kvdi/${KVDI_VERSION}/config/crd/bases/crds/rbac.kvdi.io_vdiroles.yaml
 ```
 
 When there is a change to one or more CRDs, it will be mentioned in the notes for that release.
 
 ## Building and Running Locally
 
-The `Makefiles` contain helpers for testing the full solution locally using `kind`. Run `make help` to see all the available options.
+The `Makefile` contains helpers for testing the full solution locally using `k3d`. Run `make help` to see all the available options.
 
 _If you choose to pull the images from the registry instead of building and loading first - you probably want to set `VERSION=latest` (or a previous version) in your environment also.
 The `Makefile` is usually pointed at the next version to be released and published images may not exist yet_.

deploy/bundle.yaml

@@ -20,6 +20,7 @@ Types
 -   [ServiceMonitorConfig](#ServiceMonitorConfig)
 -   [TLSConfig](#TLSConfig)
 -   [UserdataSelector](#UserdataSelector)
+-   [UserdataSpec](#UserdataSpec)
 -   [VDICluster](#VDICluster)
 -   [VDIClusterSpec](#VDIClusterSpec)
 -   [VaultConfig](#VaultConfig)
@@ -501,6 +502,32 @@ yourself.
 </tbody>
 </table>
 
+### UserdataSpec
+
+(*Appears on:* [VDIClusterSpec](#VDIClusterSpec))
+
+UserdataSpec is an inline of the corev1 PersistentVolumeClaimSpec. It
+contains additional fields for controlling how kvdi works with volumes.
+
+<table>
+<thead>
+<tr class="header">
+<th>Field</th>
+<th>Description</th>
+</tr>
+</thead>
+<tbody>
+<tr class="odd">
+<td><code>PersistentVolumeClaimSpec</code> <em><a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.18/#persistentvolumeclaimspec-v1-core">Kubernetes core/v1.PersistentVolumeClaimSpec</a></em></td>
+<td><p>(Members of <code>PersistentVolumeClaimSpec</code> are embedded into this type.)</p></td>
+</tr>
+<tr class="even">
+<td><code>retainPVCs</code> <em>bool</em></td>
+<td><p>RetainPVCs tells the desktop controller to leave PVCs in-tact after they are allocated for a user. The default behavior is to free the volume from the PVC after each desktop session so it can be used across other namespaces. Note that if you set this value to <code>true</code> users will only be able to launch sessions in a single namespace (unless the PVC is manually removed).</p></td>
+</tr>
+</tbody>
+</table>
+
 ### VDICluster
 
 VDICluster is the Schema for the vdiclusters API
@@ -541,7 +568,7 @@ VDICluster is the Schema for the vdiclusters API
 <td><p>Pull secrets to use when pulling container images</p></td>
 </tr>
 <tr class="odd">
-<td><code>userdataSpec</code> <em><a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.18/#persistentvolumeclaimspec-v1-core">Kubernetes core/v1.PersistentVolumeClaimSpec</a></em></td>
+<td><code>userdataSpec</code> <em><a href="#UserdataSpec">UserdataSpec</a></em></td>
 <td><p>The configuration for user $HOME volumes to be managed by kVDI.</p>
 <p><strong>NOTE:</strong> Even though the controller will try to force the reclaim policy on created volumes to <code>Retain</code>, you may want to set it explicitly on your storage-class controller as an extra safeguard.</p></td>
 </tr>
@@ -606,7 +633,7 @@ VDIClusterSpec defines the desired state of VDICluster
 <td><p>Pull secrets to use when pulling container images</p></td>
 </tr>
 <tr class="odd">
-<td><code>userdataSpec</code> <em><a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.18/#persistentvolumeclaimspec-v1-core">Kubernetes core/v1.PersistentVolumeClaimSpec</a></em></td>
+<td><code>userdataSpec</code> <em><a href="#UserdataSpec">UserdataSpec</a></em></td>
 <td><p>The configuration for user $HOME volumes to be managed by kVDI.</p>
 <p><strong>NOTE:</strong> Even though the controller will try to force the reclaim policy on created volumes to <code>Retain</code>, you may want to set it explicitly on your storage-class controller as an extra safeguard.</p></td>
 </tr>
@@ -681,4 +708,4 @@ server.
 
 ------------------------------------------------------------------------
 
-*Generated with `gen-crd-api-reference-docs` on git commit `c4e330a`.*
+*Generated with `gen-crd-api-reference-docs` on git commit `c911719`.*

doc/appv1.md

@@ -430,4 +430,4 @@ TemplateSpec defines the desired state of Template
 
 ------------------------------------------------------------------------
 
-*Generated with `gen-crd-api-reference-docs` on git commit `c4e330a`.*
+*Generated with `gen-crd-api-reference-docs` on git commit `c911719`.*

doc/desktopsv1.md

@@ -64,4 +64,4 @@ Complete documentation for kvdi is available at https://github.com/kvdi/kvdi
 * [kvdictl users](kvdictl_users.md)	 - Users commands
 * [kvdictl version](kvdictl_version.md)	 - Retrieve kVDI version information
 
-###### Auto generated by spf13/cobra on 14-Aug-2021
+###### Auto generated by spf13/cobra on 24-Oct-2021

doc/kvdictl/kvdictl.md

@@ -61,4 +61,4 @@ kvdictl completion [bash|zsh|fish|powershell]
 
 * [kvdictl](kvdictl.md)	 - 
 
-###### Auto generated by spf13/cobra on 14-Aug-2021
+###### Auto generated by spf13/cobra on 24-Oct-2021

doc/kvdictl/kvdictl_completion.md

@@ -26,4 +26,4 @@ Configuration commands
 * [kvdictl config client](kvdictl_config_client.md)	 - Client configuration commands
 * [kvdictl config server](kvdictl_config_server.md)	 - Retrieve server configurations
 
-###### Auto generated by spf13/cobra on 14-Aug-2021
+###### Auto generated by spf13/cobra on 24-Oct-2021

doc/kvdictl/kvdictl_config.md

@@ -26,4 +26,4 @@ Client configuration commands
 * [kvdictl config client get](kvdictl_config_client_get.md)	 - Retrieve client configurations
 * [kvdictl config client set](kvdictl_config_client_set.md)	 - Set client configurations
 
-###### Auto generated by spf13/cobra on 14-Aug-2021
+###### Auto generated by spf13/cobra on 24-Oct-2021

doc/kvdictl/kvdictl_config_client.md

@@ -28,4 +28,4 @@ kvdictl config client get <PATH> [flags]
 
 * [kvdictl config client](kvdictl_config_client.md)	 - Client configuration commands
 
-###### Auto generated by spf13/cobra on 14-Aug-2021
+###### Auto generated by spf13/cobra on 24-Oct-2021