Now that we have docker images for each individual application and we have deployment topology figured out, it is time to write actual kubernetes configurations.
The exercise in the previous section helped us plan the number of containers per service to handle our traffic.
Before we start writing our configurations, it is always good to come up with naming conventions. We will realize that soon, as there will be too many things to name. Certain conventions that we will adopt in this example are as follows:
- Any resource created in k8s will have a name prefixed with shorthand for scalamicroservices (sm-). This is essential to distinguish between your resources and system-generated resources and also resources from other users of the cluster.
- Decide on a tool to apply changes to kubernetes, and stick to it for consistency-- Kubectl or REST API, not both. We will...