Kubernetes Manifests: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
<font color=darkgray>'''Commonality''''. There are common elements with the same semantics for all manifests (e.g. metadata.name). Address them here in a common section, and link from individual "kinds" to here. | <font color=darkgray>'''Commonality''''. There are common elements with the same semantics for all manifests (e.g. metadata.name). Address them here in a common section, and link from individual "kinds" to here. | ||
</font> | </font> | ||
=Elements= | |||
==apiVersion== | |||
==kind== | |||
==metadata== | |||
==spec== | |||
=Manifest Operations= | =Manifest Operations= | ||
* [[Kubectl#POSTing_a_Manifest|POSTing a Manifest]] | * [[Kubectl#POSTing_a_Manifest|POSTing a Manifest]] | ||
* [[Kubectl#Get_the_Manifest_for_an_Existing_Object|Get the Manifest for an Existing Object]] | * [[Kubectl#Get_the_Manifest_for_an_Existing_Object|Get the Manifest for an Existing Object]] | ||
Revision as of 22:56, 30 August 2019
Internal
Overview
A manifest expresses the desired state of the application.
Manifest files can be generated with kubectl kustomize.
TODO
Commonality'. There are common elements with the same semantics for all manifests (e.g. metadata.name). Address them here in a common section, and link from individual "kinds" to here.