1z0-1109-23 - Oracle Cloud Infrastructure 2023 DevOps Professional

Explanation

A valid concern that needs to be further investigated in this scenario is whether the OKE cluster has a secret with credentials of the Oracle Cloud Infrastructure Registry (OCIR) repository and if that secret is being used in the Kubernetes deployment manifest. When deploying an application on OKE and pulling images from OCIR, the cluster needs to authenticate and authorize access to the OCIR repository. This is typically done by creating a Kubernetes secret that contains the credentials (authentication token or username/password) required to access the repository. The secret is then referenced in the Kubernetes deployment manifest to allow the cluster to pull the images. If the images are not getting pulled from the designated OCIR repository, it suggests that the OKE cluster might be missing the necessary secret with the OCIR credentials or the secret is not properly referenced in the deployment manifest. Further investigation should focus on ensuring the existence and correct configuration of the secret and its usage in the deployment process.

Explanation

As a developer working on the Oracle Cloud Infrastructure (OCI) DevOps service, when creating a build spec YAML file for the build pipeline, the following two actions are part of the proper creation of the file: Enter the details for binaries used in later pipeline stages into the outputArtifacts section: In the outputArtifacts section, you specify the artifacts or files generated during the build process that should be saved for future use. These artifacts can include compiled binaries, libraries, configuration files, or any other relevant files that need to be preserved. Enter the necessary vault secret variable OCIDs into the vaultVariables section: In the vaultVariables section, you define the variables that correspond to the Vault OCIDs (Oracle Cloud Infrastructure Vault service). These variables are used to securely store and retrieve sensitive information, such as API keys, passwords, or other secrets, required by the build pipeline or later stages of the deployment process. By including these actions in the build spec YAML file, you ensure that the necessary artifacts are properly saved and that the required vault secret variables are available for secure access during the build and deployment pipeline execution. Reference: https://docs.oracle.com/en-us/iaas/Content/devops/using/build_specs.htm

To create stages for an OKE deployment pipeline in OCI DevOps, you can add the following stages:

• Add a stage to deploy based on Blue-Green strategy or Canary strategy to OKE environment. A Blue-Green strategy is a deployment technique that involves creating two identical environments (blue and green) and switching traffic between them after testing. A Canary strategy is a deployment technique that involves releasing a new version of the application to a subset of users (canaries) and monitoring their feedback before rolling out to the rest of the users. You can use these strategies to reduce downtime, minimize risk, and improve user experience.
• Add a stage to apply the Kubernetes manifest to the Kubernetes cluster. A Kubernetes manifest is a YAML or JSON file that defines the desired state of your Kubernetes resources, such as pods, services, deployments, etc. You can use this stage to apply the manifest file to your OKE cluster using kubectl or helm commands. Verified References: [Deployment Strategies - Oracle Cloud Infrastructure DevOps], [Applying Kubernetes Manifests - Oracle Cloud Infrastructure DevOps]