VMware vSphere Integrator
- By Canonical Kubernetes
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/stable | 52 | Yesterday | |
| latest/candidate | 52 | 15 Apr 2024 | |
| latest/beta | 53 | Yesterday | |
| latest/edge | 53 | 16 Apr 2024 | |
| 1.30/edge | 53 | 16 Apr 2024 | |
| 1.29/stable | 52 | Yesterday | |
| 1.29/candidate | 52 | 15 Apr 2024 | |
| 1.29/beta | 53 | Yesterday | |
| 1.29/edge | 47 | 30 Aug 2023 | |
| 1.28/stable | 49 | 26 Sep 2023 | |
| 1.28/candidate | 49 | 22 Sep 2023 | |
| 1.28/beta | 44 | 07 Aug 2023 | |
| 1.28/edge | 45 | 09 Aug 2023 | |
| 1.27/stable | 40 | 12 Jun 2023 | |
| 1.27/candidate | 40 | 12 Jun 2023 | |
| 1.27/beta | 37 | 09 Apr 2023 | |
| 1.27/edge | 35 | 07 Apr 2023 | |
| 1.26/stable | 34 | 27 Feb 2023 | |
| 1.26/candidate | 34 | 25 Feb 2023 | |
| 1.26/beta | 28 | 09 Apr 2023 | |
| 1.26/edge | 28 | 19 Nov 2022 | |
| 1.25/stable | 27 | 30 Sep 2022 | |
| 1.25/candidate | 27 | 28 Sep 2022 | |
| 1.25/beta | 29 | 01 Dec 2022 | |
| 1.25/edge | 22 | 09 Sep 2022 | |
| 1.24/stable | 16 | 04 Aug 2022 | |
| 1.24/candidate | 16 | 01 Aug 2022 | |
| 1.24/beta | 8 | 21 Apr 2022 | |
| 1.24/edge | 15 | 27 Jul 2022 | |
| 1.23/beta | 4 | 22 Mar 2022 | |
| 1.23/edge | 2 | 24 Feb 2022 |
juju deploy vsphere-integrator
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
This charm acts as a proxy to VMware vSphere and provides an interface to provide a set of credentials for a somewhat limited project user to the applications that are related to this charm.
Usage
When on a vSphere cloud, this charm can be deployed, granted trust via Juju to access vSphere, and then related to an application that supports the interface.
For example, Charmed Kubernetes has support for this, and can be deployed with the following bundle overlay:
applications:
vsphere-integrator:
charm: cs:~containers/vsphere-integrator
num_units: 1
relations:
- ['vsphere-integrator', 'kubernetes-control-plane']
- ['vsphere-integrator', 'kubernetes-worker']
Using Juju 2.4 or later:
juju deploy charmed-kubernetes --overlay ./k8s-vsphere-overlay.yaml
juju trust vsphere-integrator
To deploy with earlier versions of Juju, you will need to provide the cloud
credentials via the credentials charm config option:
cat <<EOJ > /path/to/cloud.json
{
"vsphere_ip": "a.b.c.d",
"user": "joe",
"password": "passw0rd",
"datacenter": "dc0"
}
EOJ
juju config vsphere-integrator credentials="$(base64 /path/to/cloud.json)"
Configuration
This charm supports multiple config options that can be used to describe they vSphere environment.
The only required option is datastore, as it is not included in the Juju
credential that this charm relies on. By default, this is set to datastore1.
This can be changed with:
juju config vsphere-integrator datastore='mydatastore'
You may also configure a folder and resource pool path for this charm. Details about these options can be found in the vmware documentation:
juju config vsphere-integrator folder='juju-kubernetes' respool_path='foo'
As mentioned in the Usage section, credentials may be set with a
base64-encoded json file. When set, this data will take precedent over all
other methods of specifying credentials for this charm.
If credentials is empty, there are config options for each key that
constitute a Juju credential. These can be set with:
juju config vsphere-integrator \
vsphere_ip='a.b.c.d' \
user='joe' \
password='passw0rd' \
datacenter='dc0'
Note: If any of the credential config options are set, they must all be set.
When all of the credential config options are empty, this charm will fall
back to the credential data it received with juju trust vsphere-integrator.
Resource Usage Note
By relating to this charm, other charms can directly allocate resources, such as PersistentDisk volumes, which could lead to cloud charges and count against quotas. Because these resources are not managed by Juju, they will not be automatically deleted when the models or applications are destroyed, nor will they show up in Juju’s status or GUI. It is therefore up to the operator to manually delete these resources when they are no longer needed, using the vCenter console or API.
Examples
The following are some examples using vSphere integration with Charmed Kubernetes.
Creating a pod with a PersistentDisk-backed volume
This script creates a busybox pod with a persistent volume claim backed by vSphere’s PersistentDisk.
#!/bin/bash
# create a storage class using the `kubernetes.io/vsphere-volume` provisioner
kubectl create -f - <<EOY
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: mystorage
provisioner: kubernetes.io/vsphere-volume
parameters:
diskformat: zeroedthick
EOY
# create a persistent volume claim using that storage class
kubectl create -f - <<EOY
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
name: testclaim
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 100Mi
storageClassName: mystorage
EOY
# create the busybox pod with a volume using that PVC:
kubectl create -f - <<EOY
apiVersion: v1
kind: Pod
metadata:
name: busybox
namespace: default
spec:
containers:
- image: busybox
command:
- sleep
- "3600"
imagePullPolicy: IfNotPresent
name: busybox
volumeMounts:
- mountPath: "/pv"
name: testvolume
restartPolicy: Always
volumes:
- name: testvolume
persistentVolumeClaim:
claimName: testclaim
EOY