- PCI PASSTHROUGH
PersistenVolumeClain creating just a mapping between your actual PersistentVolume and your pod.
Using "helm.sh/resource-policy": keep annotation for PV is not the best idea, because of that remark in a documentation:
The annotation "helm.sh/resource-policy": keep instructs Tiller to skip this resource during a helm delete operation. However, this resource becomes orphaned. Helm will no longer manage it in any way. This can lead to problems if using helm install --replace on a release that has already been deleted, but has kept resources.
If you will create a PV manually after you will delete your release, Helm will remove PVC, which will be marked as "Available" and on next deployment, it will reuse it. Actually, you don't need to keep your PVC in the cluster to keep your data. But, for making it always using the same PV, you need to use labels and selectors.
abs(float) - Returns the absolute value of a given float.
abs(-1) would also return
abs(-3.14) would return
3.14. See also the
basename(path) - Returns the last element of a path.
base64decode(string) - Given a base64-encoded string, decodes it and
returns the original string.
|"2) Extract the downloaded image with ‘sudo’ to allow ‘mknod’ commands to work"|
|# get a cloud image from here|
|# based on https://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/bin/img2squashfs#L161|
|# extract a cloud image rootfs to a directory, sudo is needed for `mknod`s to work|
|# doesn't have to be .tar.gz - could well unsquashfs an existing squashfs|