VMware Marketplace<\/a>.<\/span><\/span><\/p>\n![](\"https:\/\/loeilduse.fr\/wp-content\/uploads\/2021\/06\/Marketplace-search-image.png\")
<\/span><\/p>\nThen click on the desired image, connect with your MyVMware account.<\/span><\/span><\/p>\n![](\"https:\/\/loeilduse.fr\/wp-content\/uploads\/2021\/06\/Marketplace-sigin.png\")
<\/p>\n
You have two options, download it then upload it to a local content library<\/span><\/span><\/p>\n![](\"https:\/\/loeilduse.fr\/wp-content\/uploads\/2021\/06\/Marketplace-download.png\")
<\/p>\n
or retrieve the subscription url to create a content library that will synchronize with the one hosted by VMware.<\/span><\/span><\/p>\n![](\"https:\/\/loeilduse.fr\/wp-content\/uploads\/2021\/06\/Marketplace-subscribe.png\")
<\/p>\n
Once the image is loaded or the link is filled in, you should have a content library like this:<\/span><\/span><\/p>\n![](\"https:\/\/loeilduse.fr\/wp-content\/uploads\/2021\/06\/content-library-list.png\")
<\/p>\n
Still from the vSphere interface, we must now create a namespace, grant the rights to the users so that they can connect to it, assign the VM class, the content library and the storage class, which should give this<\/span><\/span><\/p>\n![](\"https:\/\/loeilduse.fr\/wp-content\/uploads\/2021\/06\/namespace-cl-vmclass-perm-storage.png\")
<\/p>\n
The example above shows once the namespace has been created, how to assign a VM class, a content library, authorize the developers who can consume this namespace, which storage class to use and finally if necessary cap the resources, CPU, memory<\/span> and storage.<\/span><\/span><\/p>\n That\u2019s all there is to it on the infrastructure administrator side.<\/span> <\/span><\/p>\nRegarding the developer<\/span> <\/span><\/strong><\/span><\/p>\nYou need a YAML description for:<\/span> <\/span><\/p>\n\n- The configmap which contains the customization of the VM<\/span> <\/span><\/li>\n
- The creation of the VM<\/span> <\/span><\/li>\n
- The Network service if you want to connect to it from an outside network (optional)<\/span> PVC if you want to use persistent volumes (optional)<\/span> <\/span><\/li>\n<\/ul>\n
Via the Kubernetes command, the developer connects with his account to the Namespace provided, he will be able to list the classes of services that he can use as well as the images that he can deploy.<\/span><\/span><\/p>\nkubectl get virtualmachineclass
\n<\/strong><\/span>NAME\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 CPU\u00a0\u00a0 MEMORY\u00a0\u00a0 AGE<\/span>
\nbest-effort-2xlarge\u00a0\u00a0 8\u00a0\u00a0\u00a0\u00a0 64Gi\u00a0\u00a0\u00a0\u00a0 22d<\/span>
\nbest-effort-4xlarge\u00a0\u00a0 16\u00a0\u00a0\u00a0 128Gi\u00a0\u00a0\u00a0 22d<\/span>
\nbest-effort-8xlarge\u00a0\u00a0 32\u00a0 \u00a0\u00a0128Gi\u00a0\u00a0\u00a0 22d<\/span>
\nbest-effort-large\u00a0\u00a0\u00a0\u00a0 4\u00a0\u00a0\u00a0\u00a0 16Gi\u00a0\u00a0\u00a0\u00a0 22d<\/span>
\nbest-effort-medium\u00a0\u00a0\u00a0 2\u00a0\u00a0\u00a0\u00a0 8Gi\u00a0\u00a0\u00a0\u00a0\u00a0 31d<\/span>
\nbest-effort-small\u00a0\u00a0\u00a0\u00a0 2\u00a0\u00a0\u00a0\u00a0 4Gi\u00a0\u00a0\u00a0\u00a0\u00a0 31d<\/span>
\nbest-effort-xlarge\u00a0\u00a0\u00a0 4\u00a0\u00a0\u00a0\u00a0 32Gi\u00a0\u00a0\u00a0\u00a0 22d<\/span>
\nbest-effort-xsmall\u00a0\u00a0\u00a0 2\u00a0\u00a0\u00a0\u00a0 2Gi\u00a0\u00a0\u00a0\u00a0\u00a0 22d<\/span>
\n..<\/span>
\nguaranteed-xsmall\u00a0\u00a0\u00a0\u00a0 2\u00a0\u00a0\u00a0\u00a0 2Gi\u00a0\u00a0\u00a0\u00a0\u00a0 22d<\/span><\/p>\n <\/p>\n
kubectl get virtualmachineimage
\n<\/strong>NAME\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 VERSION\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 OSTYPE\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 FORMAT\u00a0\u00a0 AGE<\/span>
\ncentos-stream-8-vmservice-v1alpha1-1619529007339\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 centos8_64Guest\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ovf\u00a0\u00a0\u00a0\u00a0\u00a0 4h8m<\/span>
\nob-15957779-photon-3-k8s-v1.16.8\u2014vmware.1-tkg.3.60d2ffd\u00a0\u00a0\u00a0 v1.16.8+vmware.1-tkg.3.60d2ffd\u00a0\u00a0\u00a0 vmwarePhoton64Guest\u00a0\u00a0 ovf\u00a0\u00a0\u00a0\u00a0\u00a0 2d19h<\/span>
\nob-16466772-photon-3-k8s-v1.17.7\u2014vmware.1-tkg.1.154236c\u00a0\u00a0\u00a0 v1.17.7+vmware.1-tkg.1.154236c\u00a0\u00a0\u00a0 vmwarePhoton64Guest\u00a0\u00a0 ovf\u00a0\u00a0\u00a0\u00a0\u00a0 2d19h<\/span>
\nob-16545581-photon-3-k8s-v1.16.12\u2014vmware.1-tkg.1.da7afe7\u00a0\u00a0 v1.16.12+vmware.1-tkg.1.da7afe7\u00a0\u00a0 vmwarePhoton64Guest\u00a0\u00a0 ovf\u00a0\u00a0\u00a0\u00a0\u00a0 2d19h<\/span>
\n\u2026\u2026<\/span>
\nubuntu-20-1621373774638\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0ubuntu64Guest\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ovf\u00a0\u00a0\u00a0\u00a0\u00a0 4h8m<\/span><\/p>\nHe can thus create his YAML descriptive files in order to define his resource requirements for his virtual machine (s) and if they wish, he can customize it or them in order to install his tools.<\/span> <\/span><\/p>\nThe configmap descriptive file, includes the customization of the VM.<\/span> The 3 important fields to fill in for personalization are:<\/span> <\/span><\/p>\n\n- The hostname which contains the OS hostname<\/span> <\/span><\/li>\n
- The public-keys, which contains the public key of a computer from which we will connect to the OS in ssh.<\/span> <\/span><\/li>\n
- The user-data part is, if you wish, the place where we put the contents of the Cloud Init configuration file, it will have to be encrypted with the base64 command<\/span><\/span><\/li>\n<\/ul>\n
cat loeil-du-se-vm-configmap.yaml<\/strong><\/span>
\napiVersion: v1<\/span>
\nkind: ConfigMap<\/span>
\nmetadata:<\/span>
\n\u00a0\u00a0\u00a0 name: loeil-du-se-vm-configmap # The name of the ConfigMap, must be the same as in the VirtualMachine<\/span>
\n\u00a0\u00a0\u00a0 namespace: loeil-du-se<\/span>
\ndata:<\/span>
\n\u00a0 # OVF Keys values required by the VM at provision time<\/span>
\n\u00a0 hostname: loeil-du-se<\/span>
\n\u00a0 public-keys: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDC4Cclh3rN\/l70lBNlwQyK6ZtugxqT\/7HeerHZKPSO0hcl5ZWLvz2+7QG5FqvYbkPP6EomvyDhE2MPnQ0kWaIrumVxYXAbVdpBBKKdTI3xJpewWB2syxgVOXP2ZOrw4cRLFv18rnESGHfsohedyaSB1qvubPWAqBFa+PSS4xh3zKalUknwc7Bs14fci8tEwEg8cpvNsqvrPZliJ6qTYFGqKuG6Ct+y449JNW6k6itTepgSYvUdJfjBTxk5tDzBdWz28km5N7lxgUB0rIWgSDl1XLCBrmm+H6bkHtD59MxAuxwLjih4tS4PzspcVjwWiJhd0HH7u2wbsPLCrrAX7am4EP40zphu9IR+fVxk+2jp7eD2uXPS6p9sDPEWHl6wGclI7pnfuoyvcn+CIwCtMweLuUw5MPj2eIIXcBhqUffeVAXVHrx8+e7+yHvqfyhqm2J9Ay3yt3zvAcXW0VqDxfvnfmv8sc9VNUW+8fUeyoo4b4uZRLLSf2DHM8= root@fbenrejdal-z01 # the public key to be able to do ssh without password from my laptop<\/span>
\n\u00a0 user-data: | # optional, enter the base64 cloud init encodded file, the result key could be a one line key or a multiple lines key. watch out the indentation, the line should be start under the “r” of user-data<\/span>
\n\u00a0\u00a0\u00a0\u00a0 I2Nsb3VkLWNvbmZpZwojIFdBVENIT1VUIHRoZSBmaXJzdCBsaW5lIG11c3Qgc3RhcnQgd2l0aCAj<\/span>
\n\u00a0\u00a0\u00a0\u00a0 Y2xvdWQtY29uZmlnCmdyb3VwczoKICAtIGRldm9wcwp1c2VyczoKICAtIGRlZmF1bHQgIyBDcmVh<\/span>
\n\u00a0\u00a0\u00a0\u00a0 dGUgdGhlIGRlZmF1bHQgdXNlciBmb3IgdGhlIE9TCiAgLSBuYW1lOiBmYmUKICAgIHNzaC1hdXRo<\/span>
\n\u00a0\u00a0\u00a0\u00a0 b3JpemVkLWtleXM6ICMgdGhlIHB1YmxpYyBrZXkgb2YgbXkgbGFwdG9wLCBpdCBjb3VsZCBhbHNv<\/span>
\n\u00a0\u00a0\u00a0\u00a0 IGJlIGZpbGxlZCBpbiB0aGUgT1ZGIHByb3BlcnR5CiAgICAgIC0gc3NoLXJzYSBBQUFBQjNOemFD<\/span>
\n\u00a0\u00a0\u00a0\u00a0 MXljMkVBQUFBREFRQUJBQUFCZ1FEQzRDY2xoM3JOL2w3MGxCTmx3UXlLNlp0dWd4cVRHLzdIZWVy<\/span>
\n\u00a0\u00a0\u00a0\u00a0 SFpLUFNPMGhjbDVaV0x2ejIrN1FHNUZxdllia1BQNkVvbXZ5RGhFMk1QblEwa1dhSXJ1bVZ4WVhB<\/span>
\n\u00a0\u00a0\u00a0\u00a0 YlZkcEJCS0tkVEkzeEpwZXdXL0Iyc3l4Z1ZPWFAyWk9ydzRjUkxGdjE4cm5FU0dIZisvc29oZWR5<\/span>
\n\u00a0\u00a0\u00a0\u00a0 YVNCMXF2dWJQV0FxQkZhK1BTUzR4aDZELzN6S2FsVWtud2M3QnMxNGZjaTh0RXdFZzhjcHZOc3F2<\/span>
\n\u00a0\u00a0\u00a0\u00a0 clBabGlKNnFUWUZHcUt1RzZDdCt5NDQ5Sk5XNms2aXRUZXBnU1l2VWRKZmpCVHhrNXREekJkV3oy<\/span>
\n\u00a0\u00a0\u00a0\u00a0 OGttNU43bHhnVUIwcklXZ1NEbDFYTENCcm1tK0g2YmtIdEQ1OU14QXV4d0xqaWg0dFM0UHpzcGNW<\/span>
\n\u00a0\u00a0\u00a0\u00a0 dGFydCBtb25nb2QK<\/span><\/p>\nThe base64 is obtained as follows:<\/span><\/span><\/p>\nbase64\u00a0 loeil-du-se-vm-cloud-init.yaml<\/span><\/p>\nIts content in clear:<\/span><\/span><\/p>\ncat\u00a0 loeil-du-se-vm-cloud-init.yaml
\n<\/strong>#cloud-config<\/span>
\n# WATCHOUT the first line must start with #cloud-config<\/span>
\ngroups:<\/span>
\n\u00a0 \u2013 devops<\/span>
\nusers:<\/span>
\n\u00a0 \u2013 default # Create the default user for the OS<\/span>
\n\u00a0 \u2013 name: fbe<\/span>
\n\u00a0 ssh-authorized-keys: # the public key of my laptop, it could also be filled in the OVF property<\/span>
\n\u00a0\u00a0\u00a0 \u2013 ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDC4Cclh3rN\/l70lBNlwQyK6ZtugxqTG7HeerHZKPSO0hcl5ZWLvz2+7QG5FqvYbkPP6EomvyDhE2MPnQ0kWaIrumVxYXAbVdpBBKKdTI3xJpewWB2syxgVOXP2ZOrw4cRLFv18rnESGHf+sohedyaSB1qvubPWAqBFa+PSS4xh6D3zKalUknwc7Bs14fci8tEwEg8cpvNsqvrPZliJ6qTYFGqKuG6Ct+y449JNW6k6itTepgSYvUdJfjBTxk5tDzBdWz28km5N7lxgUB0rIWgSDl1XLCBrmm+H6bkHtD59MxAuxwLjih4tS4PzspcVjwWiJhd0HH7u2wbsPLCrrAX7am4EP40zphu9IR+fVxk+2jp7eD2uXPS6p9sDPEWHl6wGclI7pnfuoyvcn+CIwCtMweLuUw5MPj2eIIXcBhqUffeVAXVHrx8+e7+yHvqfyhqm2J9Ay3yt3zvAcXW0VqDxfvnfmv8sc9VNUW+8fUeyoo4b4uZRLLSf2DHM8= root@fbenrejdal-z01<\/span>
\n\u00a0\u00a0\u00a0\u00a0\u00a0 groups: sudo, devops<\/span>
\n\u00a0\u00a0\u00a0 shell: \/bin\/bash<\/span>
\n\u00a0\u00a0\u00a0 passwd: VMware1!<\/span>
\n\u00a0\u00a0\u00a0 sudo: [\u2018ALL=(ALL) NOPASSWD:ALL\u2019] # the user fbe will not need to enter password when using sudo<\/span>
\n\u00a0 ssh_pwauth: true<\/span>
\n\u00a0 chpasswd:<\/span>
\n\u00a0 list: |<\/span>
\n\u00a0\u00a0\u00a0 fbe:VMware1! # in case you want to change password of users<\/span>
\n\u00a0\u00a0\u00a0 expire: false\u00a0 # if you don’t want your password to expire<\/span>
\nruncmd: # Example of runcmd to install MongoDB. Cloud Init has also APT keyword to do installation<\/span>
\n\u00a0 \u2013 echo \u201cdeb [ arch=amd64,arm64 ] https:\/\/repo.mongodb.org\/apt\/ubuntu focal\/mongodb-org\/4.4 multiverse\u201d | tee \/etc\/apt\/sources.list.d\/mongodb-org-4.4.list<\/span>
\n\u00a0 \u2013 wget -qO \u2013 https:\/\/www.mongodb.org\/static\/pgp\/server-4.4.asc | apt-key add \u2013<\/span>
\n\u00a0 \u2013 echo \u201cdeb [ arch=amd64,arm64 ] https:\/\/repo.mongodb.org\/apt\/ubuntu focal\/mongodb-org\/4.4 multiverse\u201d | tee \/etc\/apt\/sources.list.d\/mongodb-org-4.4.list<\/span>
\n\u00a0 \u2013 apt-get update<\/span>
\n\u00a0 \u2013 apt-get install -y mongodb-org<\/span>
\n\u00a0 \u2013 echo \u201cmongodb-org hold\u201d | dpkg \u2013set-selections<\/span>
\n\u00a0 \u2013 echo \u201cmongodb-org-server hold\u201d | dpkg \u2013set-selections<\/span>
\n\u00a0 \u2013 echo \u201cmongodb-org-shell hold\u201d | dpkg \u2013set-selections<\/span>
\n\u00a0 \u2013 echo \u201cmongodb-org-mongos hold\u201d | dpkg \u2013set-selections<\/span>
\n\u00a0 \u2013 echo \u201cmongodb-org-tools hold\u201d | dpkg \u2013set-selections<\/span>
\n\u00a0 \u2013 sed -i \u2018s\/127.0.0.1\/0.0.0.0\/\u2019 \/etc\/mongod.conf<\/span>
\n\u00a0 \u2013 ufw allow from any to any port 27017 proto tcp<\/span>
\n\u00a0 \u2013 sleep 2<\/span>
\n\u00a0 \u2013 systemctl start mongod<\/span><\/p>\nVery very important, the file must absolutely start with # cloud-config and nothing else.<\/span> It’s still a classic Cloud Init file.<\/span> If you’re not too familiar with Cloud Init, I’ve put some comments there to make it a bit more readable.<\/span><\/span><\/p>\nThe VM description file<\/span><\/span><\/p>\ncat loeil-du-se-vm-deployment.yaml
\n<\/strong>apiVersion: vmoperator.vmware.com\/v1alpha1<\/span>
\nkind: VirtualMachine<\/span>
\nmetadata:<\/span>
\n\u00a0 name: loeil-du-se-vm<\/span>
\n\u00a0 namespace: loeil-du-se<\/span>
\nlabels:<\/span>
\n\u00a0 vm: loeil-du-se-vm<\/span>
\nspec:<\/span>
\n\u00a0 imageName: ubuntu-20-1621373774638 #the image must exist on the content library and must be listed with the command kubectl get virtualmachineimage<\/span>
\n\u00a0 className: best-effort-xsmall<\/span>
\n\u00a0 powerState: poweredOn<\/span>
\n\u00a0 storageClass: silver-storage-policy<\/span>
\n\u00a0 networkInterfaces:<\/span>
\n\u00a0 \u2013 networkType: nsx-t #must be nsx-t or vsphere-distributed depending on your install.<\/span>
\n\u00a0\u00a0\u00a0 # networkName: if vsphere-distributed you must specify the name of the network portgroup<\/span>
\n\u00a0 vmMetadata:<\/span>
\n\u00a0\u00a0\u00a0 configMapName: loeil-du-se-vm-configmap # The K8s configmap where personalization is stored<\/span>
\n\u00a0\u00a0\u00a0 transport: OvfEnv<\/span>
\n#<\/span>
\n#\u00a0 when writing this article, the available image ubuntu (ubuntu-20-1621373774638) is not able to use volume because is using virtual hardware version 10<\/span>
\n#\u00a0 Instead you can use the centos image (centos-stream-8-vmservice-v1alpha1-1619529007339)<\/span>
\n#\u00a0 volumes: #when writing this article, the volume mount parameter is not use, the volume is seen in the guest but should be formated and mounted manualy<\/span>
\n#\u00a0\u00a0\u00a0 \u2013 name: loeil-du-se-volume<\/span>
\n#\u00a0\u00a0\u00a0\u00a0\u00a0 persistentVolumeClaim:<\/span>
\n#\u00a0\u00a0\u00a0\u00a0\u00a0 claimName: loeil-du-se-pvc<\/span>
\n#\u00a0\u00a0\u00a0\u00a0\u00a0 readOnly: false<\/span><\/p>\nOptional, the description file of the network service<\/span> In my example, I created a service of type LoadBalancer to connect in ssh from an external network to that of the PODs.<\/span> <\/span><\/p>\nPlease note, the kind is not Service as usual but VirtualMachineService<\/span><\/span><\/p>\ncat loeil-du-se-vm-service.yaml
\n<\/strong>apiVersion: vmoperator.vmware.com\/v1alpha1<\/span>
\nkind: VirtualMachineService<\/span>
\nmetadata:<\/span>
\n\u00a0 name: loeil-du-se-vm<\/span>
\nspec:<\/span>
\n\u00a0 selector:<\/span>
\n\u00a0\u00a0\u00a0 vm: loeil-du-se-vm<\/span>
\n\u00a0 type: LoadBalancer<\/span>
\n\u00a0 ports:<\/span>
\n\u00a0\u00a0\u00a0 \u2013 name: ssh<\/span>
\n\u00a0\u00a0\u00a0\u00a0\u00a0 port: 22<\/span>
\n\u00a0\u00a0\u00a0\u00a0\u00a0 protocol: TCP<\/span>
\n\u00a0\u00a0\u00a0\u00a0\u00a0 targetPort: 22<\/span><\/p>\nOnce the YAML files are created, all that remains is to have them taken into account by Kubernetes.<\/span><\/span><\/p>\nKubectl create -f loeil-du-se-vm-configmap.yaml<\/span><\/p>\nKubectl create -f loeil-du-se-vm-deployment.yaml<\/span><\/p>\nKubectl create -f loeil-du-se-vm-service.yaml<\/span><\/p>\nTo verify the creation of the VM:<\/span> <\/span><\/p>\n
![](\"https:\/\/loeilduse.fr\/wp-content\/uploads\/2021\/06\/VM-POD-Network.png\")
<\/p>\n![](\"https:\/\/loeilduse.fr\/wp-content\/uploads\/2021\/06\/Dev-admin-vwt.png\")
<\/span><\/p>\n