You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
55
55
56
56
```
57
-
$ kubectl set image deployment/<app-name>-app <app-name>=<new-image>
57
+
$ kubectl set image deployment/<app-name>-app <app-name>=<new-image> -n demo
58
58
```
59
59
60
60
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.
@@ -65,19 +65,19 @@ This is because the rolling upgrade strategy first stops a running replica in or
65
65
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:
66
66
67
67
```
68
-
$ kubectl expose service jhipster-registry --type=NodePort --name=exposed-registry
68
+
$ kubectl expose service jhipster-registry --type=NodePort --name=exposed-registry -n demo
0 commit comments