Skip to content

Commit 4e35cac

Browse files
authored
Merge pull request #44395 from rohan-kapse/patch-8
Add "spec" to glossary
2 parents 05636ea + e9cd56d commit 4e35cac

File tree

1 file changed

+21
-0
lines changed
  • content/en/docs/reference/glossary

1 file changed

+21
-0
lines changed
Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
---
2+
title: Spec
3+
id: spec
4+
date: 2023-12-17
5+
full_link: /docs/concepts/overview/working-with-objects/#object-spec-and-status
6+
short_description: >
7+
This field in Kubernetes manifests defines the desired state or configuration for specific Kubernetes objects.
8+
9+
aka:
10+
tags:
11+
- fundamental
12+
- architecture
13+
---
14+
Defines how each object, like Pods or Services, should be configured and its desired state.
15+
16+
<!--more-->
17+
Almost every Kubernetes object includes two nested object fields that govern the object's configuration: the object spec and the object status. For objects that have a spec, you have to set this when you create the object, providing a description of the characteristics you want the resource to have: its desired state.
18+
19+
It varies for different objects like Pods, StatefulSets, and Services, detailing settings such as containers, volumes, replicas, ports,
20+
and other specifications unique to each object type. This field encapsulates what state Kubernetes should maintain for the defined
21+
object.

0 commit comments

Comments
 (0)