Generate Docker images by running the following command in the blog, gateway, and store directories.

mvnw package -Pprod -DskipTests jib:dockerBuild

You will need to push your image to a registry. If you have not done so, use the following commands to tag and push the images:

$ docker image tag gateway ustcck/gateway
$ docker push ustcck/gateway
$ docker image tag blog ustcck/blog
$ docker push ustcck/blog
$ docker image tag store ustcck/store
$ docker push ustcck/store

You can deploy all your apps by running the below bash command:

./kubectl-apply.sh

Use these commands to find your application's IP addresses:

$ kubectl get svc gateway

You can scale your apps using

$ kubectl scale deployment <app-name> --replicas <replica-count>

The default way to update a running app in kubernetes, is to deploy a new image tag to your docker registry and then deploy it using

$ kubectl set image deployment/<app-name>-app <app-name>=<new-image>

Using livenessProbes and readinessProbe allow you to tell Kubernetes about the state of your applications, in order to ensure availablity of your services. You will need minimum 2 replicas for every application deployment if you want to have zero-downtime deployed. This is because the rolling upgrade strategy first kills a running replica in order to place a new. Running only one replica, will cause a short downtime during upgrades.

Your application logs can be found in JHipster console (powered by Kibana). You can find its service details by

$ kubectl get svc jhipster-console

• If you have chosen Ingress, then you should be able to access Kibana using the given ingress domain.
• If you have chosen NodePort, then point your browser to an IP of any of your nodes and use the node port described in the output.
• If you have chosen LoadBalancer, then use the IaaS provided LB IP

The registry is deployed using a headless service in kubernetes, so the primary service has no IP address, and cannot get a node port. You can create a secondary service for any type, using:

$ kubectl expose service jhipster-registry --type=NodePort --name=exposed-registry

and explore the details using

$ kubectl get svc exposed-registry

For scaling the JHipster registry, use

$ kubectl scale statefulset jhipster-registry --replicas 3

my apps doesn't get pulled, because of 'imagePullBackof'

Check the docker registry your Kubernetes cluster is accessing. If you are using a private registry, you should add it to your namespace by kubectl create secret docker-registry (check the docs for more info)

my applications get killed, before they can boot up

This can occur if your cluster has low resource (e.g. Minikube). Increase the initialDelaySeconds value of livenessProbe of your deployments

my applications are starting very slow, despite I have a cluster with many resources

The default setting are optimized for middle-scale clusters. You are free to increase the JAVA_OPTS environment variable, and resource requests and limits to improve the performance. Be careful!