build 001f4800 | content blog-content@c8490fa · 338 posts | profiles 20 · corpus 232 | 0 skipped |
Service · infrastructure

Virtualization

Server and desktop virtualization, and a route to containers over a platform your team already knows.

Topics capabilities · idf weight Virtualization virtualization 1.54 Containers containers 2.58
Vendors vendors · idf weight VMware vmware 0.91
04Solutions
02Capabilities
01Vendors
232Corpus

Virtualization

Virtualizing server and desktop infrastructure improves utilisation, raises availability and simplifies management. That has been true for twenty years and still is.

The route to containers

Containers are where many estates stall, because the obvious answer is a second platform: its own operating model, its own monitoring, its own permissions.

Through vSphere Kubernetes Service, formerly vSphere with Tanzu, the container platform runs on the virtualization that is already there. If your team knows vSphere, the way in is much shorter than it looks.

How we start

Usually with a proof of concept. Container infrastructure is an area where the requirements only surface once something runs: storage classes, networking and permissions get decided by the first real use case, and then for every one after it.

Experts for this

Focus areas are not yet confirmed, so nobody is suggested here automatically. · 0 experts in corpus (n=232)

You might also like

post 1.00

Build your own Homelab – Part 2

0.7 × caps 1 + 0.3 × vendor 1 = 1
post 0.74

Authenticate with the vSphere Supervisor API

0.7 × caps 0.63 + 0.3 × vendor 1 = 0.74
solution 0.43

Cloud Foundation

0.7 × caps 0.19 + 0.3 × vendor 1 = 0.43