// Module included in the following assemblies:
//
// * architecture/understanding-development.adoc

:_mod-docs-content-type: CONCEPT
[id="applying-manifest_{context}"]
= Manifest application

[role="_abstract"]
By using Kubernetes manifests, you can create a more complete picture of the components
that make up your Kubernetes applications.

You write these manifests as YAML
files and deploy them by applying them to the cluster, for example, by running
the `oc apply` command.

After you apply the manifest, consider ways to automate your container development process.
Ideally, you have some sort of CI pipeline that builds the images and pushes them to a registry. 
In particular, a GitOps pipeline integrates your container development with the Git repositories that you use to store 
the software that is required to build your applications.

The workflow after you apply the manifest might be as follows:

* Day 1: You write some YAML. You then run the `oc apply` command to apply that
YAML to the cluster and test that it works.
* Day 2: You put your YAML container configuration file into your own Git
repository. From there, people who want to install that app, or help you improve
it, can pull down the YAML and apply it to their cluster to run the app.
* Day 3: Consider writing an Operator for your application.
