httpGet liveness and readiness probes in helm-chart deployment #1903
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gaal-dev
force-pushed
the
helm-chart-deployment-probes
branch
2 times, most recently
from
6047a1d to
d627c34
Compare
Bumps [maven-enforcer-plugin](https://github.com/apache/maven-enforcer) from 3.1.0 to 3.2.1. - [Release notes](https://github.com/apache/maven-enforcer/releases) - [Commits](apache/maven-enforcer@enforcer-3.1.0...enforcer-3.2.1) --- updated-dependencies: - dependency-name: org.apache.maven.plugins:maven-enforcer-plugin dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
gaal-dev
force-pushed
the
helm-chart-deployment-probes
branch
from
d627c34 to
05c3e59
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please, use httpGet liveness and readiness probes in helm-chart deployment instead of radial/busyboxplus:curl
helm/mockserver/values.yaml
service:
test:
image: radial/busyboxplus:curl
The Docker image https://hub.docker.com/r/radial/busyboxplus is 9 years old
Docker complains that its format is deprecated
`$ docker pull radial/busyboxplus
Using default tag: latest
What's next:
View a summary of image vulnerabilities and recommendations → docker scout quickview radial/busyboxplus
Error response from daemon: [DEPRECATION NOTICE] Docker Image Format v1 and Docker Image manifest version 2, schema 1 support is disabled by default and will be removed in an upcoming release. Suggest the author of docker.io/radial/busyboxplus:latest to upgrade the image to the OCI Format or Docker Image manifest v2, schema 2. More information at https://docs.docker.com/go/deprecated-image-specs/`
https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
My simple change:
readinessProbe: httpGet: path: /status port: 1080 livenessProbe: httpGet: path: /status port: 1080Using service-test.yaml also has a negative side effect when MockServer starts and tests pass, but the curl container still cannot start and everything crashes after some timeout (30 minutes in my case). I had this scenario on a Jenkins server with K8S.