OpsMx, a leader in intelligent software delivery platform, is excited to announce support for Oracle Cloud Container Engine for Kubernetes (OKE) through its OpsMx Enterprise for Spinnaker (OES) product. Enterprises are increasingly adopting multicloud strategies for lowering the risk of reliance on a single cloud provider. OES is a highly scalable multicloud deployment tool that large enterprises, such as Cisco, Standard Chartered Bank, and Bell Canada, have adopted.
OES addresses two key challenges facing the enterprises as they adopt cloud and microservices.
First, OES increases the velocity of software delivery with automated software delivery. OES uses leading, open source project Spinnaker for its underlying orchestration functionality—simple, secure, extensible, and scalable.
Second, most organizations struggle with human intervention as part of the software delivery process, which adds increasing time, costly errors, production failures, and inconsistency to the process. These challenges happen during promotion approval between different stages of software delivery, verification of new releases for risk and diagnosis, and ensuring compliance of security and enterprise policies.
OES is the industry’s first platform that addresses these challenges holistically in a single platform. OES by extending the support for Oracle Cloud Infrastructure (OCI) allows enterprises to deploy applications across all major cloud providers.
In this blog, we showcase how to connect to Oracle Cloud Container Engine for Kubernetes through OES.
We use the OpsMx Enterprise for Spinnaker agent technology to integrate with a Kubernetes cluster running in OCI. After integration, the agent allows us to target this cluster for software deployments.
After setting up my OCI account, I quickly deployed a three-node Kubernetes cluster:
We use the clean cluster as the target for our OES target running in Oracle Cloud Shell:
Next, we use our OpsMx Enterprise Spinnaker instance and generate the needed deployment manifest to deploy the needed agent to this new Kubernetes cluster.
Provide the needed information to OES, such as the account name, which identifies this target in OES, and the namespace that we want to deploy the agent in.
After we have created this account, we can download the manifest, which deploys the agent to the cluster, and allow our OpsMx Enterprise for Spinnaker instance to deploy to this cluster.
Having uploaded the agent manifest to the Kubernetes cluster running in OCI, I can now deploy the manifest:
When the agent is deployed successfully, you can expect to see the following output:
As a final confirmation that the agent has been deployed, you can look at the running pods and see that the OpsMx agent has been deployed.
Now that we have our agent deployed, we can see the occloud cluster as a deployment for our OES Spinnaker pipeline. So, we can now deploy to the Kubernetes Cluster running in OCI. No more configuration is required.
We’re running our pipeline that’s targeting the oracle cluster, and we have successfully deployed the hello-world application to that target cluster.
To further verify, let’s look at our Kubernetes cluster running in OCI:
We have successfully deployed the Hello World application to the default namespace in the OKE cluster.
As shown, we can quickly and easily make a Kubernetes cluster running on OCI a target for our OpsMx Enterprise for Spinnaker with its agent-based technology. This OES Anywhere agent-based technology was specifically designed by OpsMx to make deploying to any Kubernetes cluster simple and secure, allowing you to quickly add new clusters as deployment targets.
Now that the Oracle Cloud is enabled in OES, enterprises can accelerate deployments and use our intelligent features to further remove human intervention in the software delivery process using the following primary features:
Scalable multicloud deployments: Deploy any applications (virtual machines, containers, or functions) securely across any on-premises clusters and public cloud services.
Safe deployment strategies: Deploy applications safely through out-of-the-box support for canary, blue-green, and progress roll-out strategies.
ML-based automated risk assessment: Verify application risk through sophisticated ML-based methods using logs and metrics during application roll-out through canary, blue-green, or progress roll-out deployment strategies.
Real-time visibility and informed approval: Perform informed application approval or promotion between different stages of software delivery (QA, staging, and production) through real-time data about the release, including source code changes, build information, source code analysis, SAST/DAST tool analysis, risk verifications, and policy checks.
Automated compliance policy enforcements: Enforce comprehensive policy based on all available data, including regulatory compliance policies through an extensible policy engine.
Auditing and traceability: Perform audits of all software delivery events, including what’s getting delivered, who approved the release, and when it was approved. With comprehensive traceability, enterprises can understand with clarity how a particular release reached production and can trace back any risk introduced by this new release.
Combining Oracle Cloud Infrastructure, OKE, and OpsMX provides developers an intelligent continuous delivery platform. If you want to experience OKE for yourself, sign up for an Oracle Cloud Infrastructure account and start testing today!
To learn more, see the following resources: