The files generated by JHipster are organized by application. That is, each application will have its own folder and the files related to that service will be present inside it.
We will start with the store gateway application. There will be three generated files: the store-service.yml, store-mysql.yml, and store-deployment.yml files.
The following is the store-service.yml file:
apiVersion: v1
kind: Service
metadata:
name: store
namespace: jhipster
labels:
app: store
spec:
selector:
app: store
type: LoadBalancer
ports:
- name: http
port: 8080
The first line defines the API version of Kubernetes we want to target, followed by the kind of template or object that this template carries. This template has a service defined in it.
Then, we have the metadata information. Kubernetes uses this metadata information to group certain services...