HPA, when triggered, is going to scale out a specific deployment, meaning, increase the number of running instances of an application to handle a particular workload. In a previous post, “Understanding Kubernetes HPA with KEDA and RabbitMQ” we have learned how to implement a simple, scalable application.
This article will show us how to design a Kubernetes job with all necessary objects that will fetch dependencies from Azure Storage Account and feed them to our applications before they start.
Notice that we only need to check the job status, thus, we don’t need to include create/update verbs in this Role.
Now, we are ready to write our job that will copy the dependencies from Azure Storage Account.