In this chapter, we will describe different elements that interact with multiple microservices.
We will look at strategies on how to make services describe their version so that dependent microservices can discover them and be sure that they have the proper dependencies already deployed. This will allow us to define a deploying order in dependent services and will stop deployment of a service if not all dependencies are ready.
This chapter describes how to define configuration parameters that are cluster-wide, so they can be shared across multiple microservices and managed in a single place, using Kubernetes ConfigMap. We will also learn how to deal with configuration parameters that are secrets—like encryption keys—that should not be accessible to most people on the team.
The following topics will be covered...
