DE · EN
Call us
+41 44 508 80 00 Ueberlandstrasse 1, 8600 Dübendorf
build 7bbbddf7 | content blog-content@c8490fa · 338 posts | profiles 20 · corpus 267 | ● 0 skipped | | format
apiVersion: soultec.ch/v1kind: Servicemetadata: name: virtualization-container locale: en labels: group: infrastructure capability/virtualization: 1.37 capability/containers: 2.39 vendor/vmware: 0.88 annotations: source: src/content/services/en/virtualization-container.md route: /en/services/virtualization-container/ schema: /nerd/schema/services.json markdown: /en/services/virtualization-container.mdspec: title: Virtualization group: infrastructure order: 10 tags: [virtualization, containers] vendors: [vmware] summary: >- Server and desktop virtualization, and a route to containers over a platform your team already knows. photoNeed: >- Infrastructure work in progress at a customer site or in our lab: hands on hardware, a rack door open, a screen mid-configuration stub: false draft: false sections: - heading:

Virtualization

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

The route to containers

 body: | 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. - heading:

How we start

 body: | 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.status: corpus: 267 solutions: - {ref: solutions/vmware/vmware-cloud-foundation/vks, score: 1.00} - {ref: solutions/vmware/vmware-cloud-foundation/vsphere-mit-tanzu, score: 1.00} - {ref: solutions/vmware/vmware-cloud-foundation/addon/application-services, score: 0.60} - {ref: solutions/vmware/vsphere-foundation, score: 0.47} alsoLike: - {ref: posts/how-to-build-your-own-homelab-part-2, score: 1.00} - {ref: posts/how-to-authenticate-with-the-vsphere-supervisor-api, score: 0.74} - {ref: experts/marco-mattei, score: 0.62} experts: - {ref: experts/marco-mattei, score: 0.62} - {ref: experts/yannick-gerber, score: 0.62} - {ref: experts/louis-kern, score: 0.59}
{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "virtualization-container", "locale": "en", "labels": { "group": "infrastructure", "capability/virtualization": "1.37", "capability/containers": "2.39", "vendor/vmware": "0.88" }, "annotations": { "source": "src/content/services/en/virtualization-container.md", "route": "/en/services/virtualization-container/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/virtualization-container.md" } }, "spec": { "title": "Virtualization", "group": "infrastructure", "order": 10, "tags": [ "virtualization", "containers" ], "vendors": [ "vmware" ], "summary": "Server and desktop virtualization, and a route to containers over a platform your team already knows.", "photoNeed": "Infrastructure work in progress at a customer site or in our lab: hands on hardware, a rack door open, a screen mid-configuration", "stub": false, "draft": false }, "sections": [ { "heading": "

Virtualization

", "body": "Virtualizing server and desktop infrastructure improves utilisation, raises availability\nand simplifies management. That has been true for twenty years and still is." }, { "heading": "

The route to containers

", "body": "Containers are where many estates stall, because the obvious answer is a second platform:\nits own operating model, its own monitoring, its own permissions.\n\nThrough vSphere Kubernetes Service, formerly vSphere with Tanzu, the container platform runs\non the virtualization that is already there. If your team knows vSphere, the way in is much\nshorter than it looks." }, { "heading": "

How we start

", "body": "Usually with a proof of concept. Container infrastructure is an area where the requirements\nonly surface once something runs: storage classes, networking and permissions get decided by\nthe first real use case, and then for every one after it." } ], "status": { "corpus": 267, "solutions": [ { "ref": "solutions/vmware/vmware-cloud-foundation/vks", "score": "1.00" }, { "ref": "solutions/vmware/vmware-cloud-foundation/vsphere-mit-tanzu", "score": "1.00" }, { "ref": "solutions/vmware/vmware-cloud-foundation/addon/application-services", "score": "0.60" }, { "ref": "solutions/vmware/vsphere-foundation", "score": "0.47" } ], "alsoLike": [ { "ref": "posts/how-to-build-your-own-homelab-part-2", "score": "1.00" }, { "ref": "posts/how-to-authenticate-with-the-vsphere-supervisor-api", "score": "0.74" }, { "ref": "experts/marco-mattei", "score": "0.62" } ], "experts": [ { "ref": "experts/marco-mattei", "score": "0.62" }, { "ref": "experts/yannick-gerber", "score": "0.62" }, { "ref": "experts/louis-kern", "score": "0.59" } ] }}
apiVersion = "soultec.ch/v1"kind = "Service"[metadata]name = "virtualization-container"locale = "en"[metadata.labels]group = "infrastructure""capability/virtualization" = "1.37""capability/containers" = "2.39""vendor/vmware" = "0.88"[metadata.annotations]source = "src/content/services/en/virtualization-container.md"route = "/en/services/virtualization-container/"schema = "/nerd/schema/services.json"markdown = "/en/services/virtualization-container.md"[spec]title = "Virtualization"group = "infrastructure"order = 10tags = ["virtualization", "containers"]vendors = ["vmware"]summary = "Server and desktop virtualization, and a route to containers over a platform your team already knows."photoNeed = "Infrastructure work in progress at a customer site or in our lab: hands on hardware, a rack door open, a screen mid-configuration"stub = falsedraft = false[[sections]]heading = "

Virtualization

"body = '''Virtualizing server and desktop infrastructure improves utilisation, raises availabilityand simplifies management. That has been true for twenty years and still is.'''[[sections]]heading = "

The route to containers

"body = '''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 runson the virtualization that is already there. If your team knows vSphere, the way in is muchshorter than it looks.'''[[sections]]heading = "

How we start

"body = '''Usually with a proof of concept. Container infrastructure is an area where the requirementsonly surface once something runs: storage classes, networking and permissions get decided bythe first real use case, and then for every one after it.'''[status]corpus = 267[[status.solutions]]ref = "solutions/vmware/vmware-cloud-foundation/vks"score = "1.00"[[status.solutions]]ref = "solutions/vmware/vmware-cloud-foundation/vsphere-mit-tanzu"score = "1.00"[[status.solutions]]ref = "solutions/vmware/vmware-cloud-foundation/addon/application-services"score = "0.60"[[status.solutions]]ref = "solutions/vmware/vsphere-foundation"score = "0.47"[[status.alsoLike]]ref = "posts/how-to-build-your-own-homelab-part-2"score = "1.00"[[status.alsoLike]]ref = "posts/how-to-authenticate-with-the-vsphere-supervisor-api"score = "0.74"[[status.alsoLike]]ref = "experts/marco-mattei"score = "0.62"[[status.experts]]ref = "experts/marco-mattei"score = "0.62"[[status.experts]]ref = "experts/yannick-gerber"score = "0.62"[[status.experts]]ref = "experts/louis-kern"score = "0.59"
<?xml version="1.0" encoding="UTF-8"?><manifest kind="Service"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>virtualization-container</name> <locale>en</locale> <labels> <group>infrastructure</group> <entry key="capability/virtualization">1.37</entry> <entry key="capability/containers">2.39</entry> <entry key="vendor/vmware">0.88</entry> </labels> <annotations> <source>src/content/services/en/virtualization-container.md</source> <route>/en/services/virtualization-container/</route> <schema>/nerd/schema/services.json</schema> <markdown>/en/services/virtualization-container.md</markdown> </annotations> </metadata> <spec> <title>Virtualization</title> <group>infrastructure</group> <order>10</order> <tags> <item>virtualization</item> <item>containers</item> </tags> <vendors> <item>vmware</item> </vendors> <summary>Server and desktop virtualization, and a route to containers over a platform your team already knows.</summary> <photoNeed>Infrastructure work in progress at a customer site or in our lab: hands on hardware, a rack door open, a screen mid-configuration</photoNeed> <stub>false</stub> <draft>false</draft> </spec> <sections> <section> <heading>

Virtualization

</heading> <body>Virtualizing server and desktop infrastructure improves utilisation, raises availabilityand simplifies management. That has been true for twenty years and still is. </body> </section> <section> <heading>

The route to containers

</heading> <body>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 runson the virtualization that is already there. If your team knows vSphere, the way in is muchshorter than it looks. </body> </section> <section> <heading>

How we start

</heading> <body>Usually with a proof of concept. Container infrastructure is an area where the requirementsonly surface once something runs: storage classes, networking and permissions get decided bythe first real use case, and then for every one after it. </body> </section> </sections> <status> <corpus>267</corpus> <solutions> <item> <ref>solutions/vmware/vmware-cloud-foundation/vks</ref> <score>1.00</score> </item> <item> <ref>solutions/vmware/vmware-cloud-foundation/vsphere-mit-tanzu</ref> <score>1.00</score> </item> <item> <ref>solutions/vmware/vmware-cloud-foundation/addon/application-services</ref> <score>0.60</score> </item> <item> <ref>solutions/vmware/vsphere-foundation</ref> <score>0.47</score> </item> </solutions> <alsoLike> <item> <ref>posts/how-to-build-your-own-homelab-part-2</ref> <score>1.00</score> </item> <item> <ref>posts/how-to-authenticate-with-the-vsphere-supervisor-api</ref> <score>0.74</score> </item> <item> <ref>experts/marco-mattei</ref> <score>0.62</score> </item> </alsoLike> <experts> <item> <ref>experts/marco-mattei</ref> <score>0.62</score> </item> <item> <ref>experts/yannick-gerber</ref> <score>0.62</score> </item> <item> <ref>experts/louis-kern</ref> <score>0.59</score> </item> </experts> </status></manifest>
Service · infrastructure

Virtualization

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

Topics Virtualization 1.37 Containers 2.39
Vendors VMware 0.88
04Solutions
02Capabilities
01Vendors
267Corpus

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

Marco Mattei

Senior System Engineer

ContainersVirtualization
0.62

Yannick Gerber

Senior Solution Architect

ContainersVirtualization
0.62

Louis Kern

Senior System Engineer

ContainersVirtualization
0.59
Maybe you? Take a look at our open roles.

You might also like

post 1.00

Build your own Homelab – Part 2

post 0.74

Authenticate with the vSphere Supervisor API

expert 0.62

Marco Mattei