////
Purpose
-------
Capture information about how to use the deployed and related systems.

Recommended to primarily be workflow diagrams, possible with labeled and annotated steps.

Examples
--------
* Continues Integration and Continues Deployment/Delivery processes
* DeclarativeOps / GitOps processes
* Update/Upgrade processes
* Self service processes,
  - EX: create a CR for a custom operator to create a new namespace and attach it to the correct team RBAC.

////
[id="processes_{context}"]
= Processes

== Cluster Lifecycle

=== Install
ROSA cli, scripts

=== Upgrades
2 minor version (e.g. 4.14 => 4.16) upgrades per year with weekly patches

== Secure Software Development Lifecycle

GitHub Enterprise

=== Ordering a Namespace

To order a namespace, users need a LeanIX number, which is an asset inventory tracking system akin to a configuration management database [CMDB].

The LeanIX number is entered into a ServiceNow ticket along with the target stage (non-prod or prod), and a name. Naming of namespaces follows a `<country>-<name>-<stage>` convention.

image::order-ns.png[Process of ordering a namespace visualised. Adapted from workshop notes.] 

=== Releasing and deploying Software

image::release.png[Process of releasing, and deploying software to a cluster visualised. Adapted from workshop notes.]

=== Ordering managed services

=== Managing vulnerabilities

CVEs

ACS, gatekeeper, RBAC admission

ACS default policy set + a few custom ones

No security quality gates

File integrity & compliance operators decomissioned.

=== Debugging

#TODO# describe how users debug their applications