This image shows the architecture underlying the deployment of a sample Hello World application by using OCI DevOps service.

An end user access an artifact repository within an Oracle Cloud Infrastructure region that contains a DevOps project. The artifact repository accesses the DevOps project and connects to a DevOps artifact through a Deployment Pipeline by communicating with three artifacts within this parent artifact.

The three component artifacts are:

• Kubernetes Manifest; this component connects, through an Oracle Kuberentes Engine (OKE) development environment, within the project, to an OKE Development Cluster outside the project but within the region. It also connects, through an Oracle Kuberentes Engine (OKE) production environment, within the project, to an OKE Production Cluster outside the project but within the region.
• YAML Deployment Config; this component connects, through an Instance Group development environment, within the project, to an Instance development component outside the project but within the region. It also connects, through an Instance Group production environment, within the project, to an Instance Production component outside the project but within the region.
• Container Image Repo Location; this component connects, through a Functions Development environment, within the project, to a Function Development component outside the project but within the region. It also connects, through a Functions Production Environment, within the project, to an Function Production component outside the project but within the region.

Outside the project but within the region, logs are stored by the Oracle Cloud Infrastructure Logging Service while the Oracle Cloud Infrastructure Notification Service provides visibility into the latest state of the deployment project and its resources and takes any necessary action.