The hands-on lab is part of this learning path
Ready for the real environment experience?
By working with Marathon pods in DC/OS you can share resources among a group of applications on a single agent and manage them as a single unit. This is often used for running a logging or analytics application alongside a primary application. Legacy applications may also fit into a pod without having to update any code. For example, if services in a legacy application communicate over the loopback network interface. In this Lab, you will deploy a couple of pods to illustrate the capabilities and limitations of working with Marathon pods in DC/OS.
Upon completion of this Lab you will be able to:
- Write Marathon pod definitions
- Manage Marathon pods from the DC/OS GUI and CLI
- Use volumes, health checks, and endpoints with pods
You should be familiar with:
- Basic DC/OS concepts including master nodes, agents, services, tasks, and Marathon
- Working at the command-line in Linux
- AWS services knowledge is useful in order to understand the architecture of the pre-created DC/OS cluster, but not required
Before completing the Lab instructions, the environment will look as follows:
After completing the Lab instructions, the environment should look similar to:
About the Author
Logan has been involved in software development and research for over eleven years, including six years in the cloud. He is an AWS Certified DevOps Engineer - Professional, MCSE: Cloud Platform and Infrastructure, Google Cloud Certified Associate Cloud Engineer, and Certified Kubernetes Administrator (CKA). He earned his Ph.D. studying design automation and enjoys all things tech.