Add Vpc image docs (#613)

* Writing howto build and upload VPC images

* Fixing links

* Moved image docs into uploading-an-image.md, put references in index.md and prerequisites.md

* Adding link into summary.md

Author: FischerLGLN

docs/book/src/SUMMARY.md

@@ -8,6 +8,7 @@
 - [Topics](./topics/index.md)
   - [VPC Cluster](./topics/vpc/index.md)
     - [Prerequisites](./topics/vpc/prerequisites.md)
+    - [Uploading an image](topics/vpc/uploading-an-image.md)
     - [Creating a cluster](./topics/vpc/creating-a-cluster.md)
   - [Power VS Cluster](./topics/powervs/index.md)
     - [Prerequisites](./topics/powervs/prerequisites.md)
@@ -19,4 +20,4 @@
   - [Release Process](./developer/release.md)
 - [Troubleshooting](./user/troubleshooting.md)
 - [Reference](./reference/reference.md)
-  - [Regions-Zones Mapping](./reference/regions-zones-mapping.md)
+  - [Regions-Zones Mapping](./reference/regions-zones-mapping.md)

docs/book/src/topics/vpc/index.md

@@ -2,4 +2,5 @@
 
 ## Contents
 - [Prerequisites](/topics/vpc/prerequisites.html)
-- [Creating a cluster](/topics/vpc/creating-a-cluster.html)
+- [Uploading an image](/topics/vpc/uploading-an-image.html)
+- [Creating a cluster](/topics/vpc/creating-a-cluster.html)

docs/book/src/topics/vpc/prerequisites.md

@@ -15,5 +15,4 @@
 
     **Note:** Rename the output image to add the `.qcow2` extension. This is required by the next step.
 
-
-2. Create a VPC Gen2 custom image based on the qcow2 image built in the previous step as detailed in the VPC [documentation](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images).
+2. Upload the VPC Gen2 custom image to IBM Cloud following [this section](uploading-an-image.md) or the detailed explainations in the VPC [documentation](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images).

docs/book/src/topics/vpc/uploading-an-image.md

@@ -0,0 +1,62 @@
+# Uploading an image to the IBM Cloud
+
+Build the Ubuntu image as described in the previous [VPC section](prerequisites.md).
+Make sure to build the qcow2 version by following the instructions for [raw image build](https://image-builder.sigs.k8s.io/capi/providers/raw.html).
+
+Since the IBM Cloud does not support dots before the qcow2 extension, rename the file as follows:
+```console
+ubuntu-2004-ibmcloud-kube-v1-23-4.qcow2
+```
+
+## Upload VM image:
+
+1) Create an IBM COS instance
+2) Create a bucket in the COS instance.
+3) Upload the image
+   1) Upload via aspera
+        * Install the browser extension for Aspera
+        * Downloading the Aspera tool
+        * Selecting the image via Aspera dialog
+        * Upload the image via aspera
+   2) Using minio cli
+        * Install minio cli
+        *  Creating a service credential with hmac=true for the bucket
+        * Example upload for eu-de:
+            ```sh
+            mc alias set uploadcos https://s3.eu-de.cloud-object-storage.appdomain.cloud <hmac access id> <hmac secret key>
+            ```
+            ```sh
+            mc cp <image-name>.qcow2 uploadcos/<my-bucket-name>
+            ```
+
+## Add VM image to VPC
+
+1) Make sure you have editor rights for all/most VPC services
+2) Add additional read rights for:
+```console
+src: service VPC Infrastructure Services resourceType equals image
+target: serviceInstance string equals <your-Cloud-Object Storage-VM-plain-name>
+```
+
+Add write rights for:
+```console
+Service VPC Infrastructure Services in Resource_group <your_resource_group_or_account> resourceType equals image
+target: service Cloud object storage in resource_group <your_resource_group_or_account>
+```
+
+3) Go to https://cloud.ibm.com/vpc-ext/provision/customImage
+  * Fill in imagename, resource group or account
+  * Choice box: Cloud Object Storage
+  * Set Filter: <your_cos_plain_name> <eu-de_or_other> <your_vm_bucket>
+  * Choice box: Select your image
+  * Select base os (ubuntu-20-04-amd64 for example)
+  * Click Create Image
+
+Now you can provision a VM with your own VM image.
+Then please continue with
+[creating a cluster](creating-a-cluster.md).
+
+Make sure you take the ImageID from your VM image. The ImageID can be determined using ibmcloud cli. In addition, the Kubernetes version must be set to match the image. In this example:
+```console
+v1.23.4
+```