Skip to content
No description, website, or topics provided.
Java TypeScript HTML JavaScript CSS Shell
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.jhipster
.mvn/wrapper
console
pizzastore
src
webpack
.editorconfig
.eslintignore
.eslintrc.json
.gitattributes
.gitignore
.huskyrc
.lintstagedrc.js
.prettierignore
.prettierrc
.yo-rc.json
README.md
angular.json
checkstyle.xml
kubectl-apply.sh
mvnw
mvnw.cmd
namespace.yml
package-lock.json
package.json
pizza-store.jdl
pom.xml
postcss.config.js
proxy.conf.json
sonar-project.properties
tsconfig-aot.json
tsconfig.json
tslint.json

README.md

JHipster-generated Kubernetes configuration

Preparation

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 pizzastore gcr.io/ody-offer-letter/pizzastore
$ docker push gcr.io/ody-offer-letter/pizzastore

Deployment

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

./kubectl-apply.sh

Exploring your services

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

$ kubectl get svc pizzastore -n pizza-store

Scaling your deployments

You can scale your apps using

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

zero-downtime deployments

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>  -n pizza-store

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 stops a running replica in order to place a new. Running only one replica, will cause a short downtime during upgrades.

Troubleshooting

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 are stopped, 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!

You can’t perform that action at this time.