-
Notifications
You must be signed in to change notification settings - Fork 157
feat: introduce readiness and liveness probe feature #73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
4f33263 to
5998d13
Compare
22e03cd to
c4a0299
Compare
c4a0299 to
b16d3ea
Compare
f3e7c36 to
b00f847
Compare
|
@arttor does this version make sense now ? 😸 |
|
@RealAnna looks good. Can you please regenerate samples without using flags? Repo samples should represent default behavior. |
|
@arttor can this be merged now or should I fix something else? |
| subPath: controller_manager_config.yaml | ||
| - mountPath: /my.ca | ||
| name: secret-volume | ||
| {{- if .Values.controllerManager.manager.livenessProbe }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should Values.controllerManager.manager.livenessProbe be in values.yaml if probe is presented in source manifest?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah for consistency
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please check that it is in values.yaml if flag is enabled. values.yaml was not updated, only template
| initialDelaySeconds: 15 | ||
| periodSeconds: 20 | ||
| {{- end }} | ||
| {{- if .Values.controllerManager.manager.readinessProbe }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we template probes only if probes=true and leave it as it is by default?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok will do :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@attor I am a bit confused, so if probes= true we template and add values otherwise I would expect to have just the probe in the deployment, correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we template probes only if probes=true and probes are presented in the source manifest. if any of these conditions is false then we do nothing.
Signed-off-by: RealAnna <anna.reale@dynatrace.com> feat: introduced liveness and readiness probes Signed-off-by: RealAnna <anna.reale@dynatrace.com> feat: introduced liveness and readiness probes Signed-off-by: RealAnna <anna.reale@dynatrace.com>
Signed-off-by: RealAnna <anna.reale@dynatrace.com>
7d6451d to
8ba0e50
Compare
this PR adds configurable liveness and readiness probes
with cli -probes=true readynessprobes and livenessprobes are templated with a completely customizable probe or the copy of the probes in the input
by default the feature is disabled