2019-02-17 16:39:11 +00:00
|
|
|
---
|
2019-09-05 03:12:51 +00:00
|
|
|
title: Workload
|
2019-04-19 16:25:56 +00:00
|
|
|
id: workloads
|
|
|
|
date: 2019-02-13
|
2019-02-17 16:39:11 +00:00
|
|
|
full_link: /docs/concepts/workloads/
|
|
|
|
short_description: >
|
2019-09-05 03:12:51 +00:00
|
|
|
A workload is an application running on Kubernetes.
|
2019-02-17 16:39:11 +00:00
|
|
|
|
2019-04-19 16:25:56 +00:00
|
|
|
aka:
|
2019-02-17 16:39:11 +00:00
|
|
|
tags:
|
2019-04-19 16:25:56 +00:00
|
|
|
- fundamental
|
2019-02-17 16:39:11 +00:00
|
|
|
---
|
2019-09-05 03:12:51 +00:00
|
|
|
A workload is an application running on Kubernetes.
|
2019-02-17 16:39:11 +00:00
|
|
|
|
2019-04-19 16:25:56 +00:00
|
|
|
<!--more-->
|
2019-02-17 16:39:11 +00:00
|
|
|
|
2019-09-05 03:12:51 +00:00
|
|
|
Various core objects that represent different types or parts of a workload
|
|
|
|
include the DaemonSet, Deployment, Job, ReplicaSet, and StatefulSet objects.
|
2019-02-17 16:39:11 +00:00
|
|
|
|
2019-09-05 03:12:51 +00:00
|
|
|
For example, a workload that has a web server and a database might run the
|
|
|
|
database in one {{< glossary_tooltip term_id="StatefulSet" >}} and the web server
|
|
|
|
in a {{< glossary_tooltip term_id="Deployment" >}}.
|