Using Pod Management Resources in Kubernetes

We have a web application that needs multiple instances for reliability. These instances need to be able to scale easily, and we need to be able to roll out code changes with zero downtime. Luckily, the application itself is stateless, which should make this a bit easier.

Create an object called web in the default Namespace to manage this workload. You will need to determine the proper object type to use. Provide 3 replicas of the application. For now, you can just the nginx:stable image.

We have another web application that is a little older. Unfortunately, it was built in a stateful fashion, and we haven't had a chance to refactor it yet. This application will need to have a sticky identity, such as a fixed order and the sticky Pod names for all of its replicas.

Create an object called legacy in the default Namespace to run this workload, using whatever object type you think is appropriate given these requirements. It should have 5 replicas and use the nginx:stable image.

Our final workload is a data cleanup task. It needs to run to completion once every minute.

Create an object called data-cleanup in the default Namespace. Once again, use the object type that you feel best meets the stated requirements. Use the busybox:stable image to run the command date once every minute.