OpenShift is a rock solid platform engineered for the enterprise. It's built on top of Kubernetes and provides many value add features, tools, and services which help to streamline the complete end-to-end container development and deployment lifecycle.
This introductory level training course is designed to bring you quickly up to speed with the key features that OpenShift provides. You'll then get to observe first hand how to launch a new OpenShift Container Platform 4.2 cluster on AWS and then deploy a real world cloud native application into it.
We’d love to get your feedback on this course, so please give it a rating when you’re finished. If you have any queries or suggestions, please contact us at firstname.lastname@example.org.
By completing this course, you will:
- Learn and understand what OpenShift is and what it brings to the table
- Learn and understand how to provision a brand new OpenShift 4.2 cluster on AWS
- Learn and understand the basic principles of deploying a cloud native application into OpenShift
- Understand how to work with and configure many of the key OpenShift value add cluster resources
- Learn how to work with the OpenShift web administration console to manage and administer OpenShift deployments
- Learn how to work with the oc command line tool to manage and administer OpenShift deployments
- And finally, you’ll learn how to manage deployments and OpenShift resources through their full lifecycle
This course is intended for:
- Anyone interested in learning OpenShift
- Software Developers interested in OpenShift containerisation, orchestration, and scheduling
- DevOps practitioners looking to learn how to provision and manage and maintain applications on OpenShift
To get the most from this course, you should have at least:
- A basic understanding of containers and containerisation
- A basic understanding of Kubernetes - and container orchestration and scheduling
- A basic understanding of software development and the software development life cycle
- A basic understanding of networks and networking
This course references the following CloudAcademy GitHub hosted repos:
- https://github.com/cloudacademy/openshift-voteapp-demo (OpenShift VoteApp Runbook)
- https://github.com/cloudacademy/openshift-s2i-frontendbuilder (OpenShift S2I Frontend Builder)
- https://github.com/cloudacademy/openshift-voteapp-frontend-react (VoteApp Frontend UI)
- [Jeremy] Okay welcome back. In this final demonstration, I'll quickly show you how to tear down the cluster should you wish to do so yourself. Performing this action will delete the underlying AWS infrastructure, the cluster EC2 instances, the route 53 DNS records, et cetera. Additionally, I'll also show you how to archive off the respective OpenShift cluster subscription from within the cloud.redhat.com portal.
Now I must first warn you that this is a destructive one way operation. Once you begin this process there is no point of return with the end result being the cluster destroyed and gone for good. For starters, let's begin within the terminal. Here I'll issue the single step 30 command openShift-install-destroycluster. This begins the one way process of tearing down the cluster infrastructure resources. This process is fairly quick. I'll skip forward to the point where the cluster has been successfully destroyed.
As you can see now the cluster destruction process has been completed successfully. Let's jump over into the AWS console and validate this by checking that the relevant route 53 and EC2 resources have all been terminated. Which they indeed have been. And finally, let's navigate back into the cloud.redhat.com portal and archive off the respective cluster subscription. Clicking on the Clusters menu item followed by clicking on the correct cluster subscription item we can then simply archive off the cluster subscription like so.
Okay, that completes step 30, the last and final step of the demonstration. And with that we've concluded the demonstration as a whole. All cluster resources have been shut down and terminated and the respective cluster subscription archived. This will insure that all billing related to the running cluster has been stopped.
About the Author
Jeremy is the DevOps Content Lead at Cloud Academy where he specializes in developing technical training documentation for DevOps.
He has a strong background in software engineering, and has been coding with various languages, frameworks, and systems for the past 20+ years. In recent times, Jeremy has been focused on DevOps, Cloud, Security, and Machine Learning.
Jeremy holds professional certifications for both the AWS and GCP cloud platforms.