Skip to content
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

feat: introduce readiness and liveness probe feature #73

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

RealAnna
Copy link
Contributor

@RealAnna RealAnna commented Feb 16, 2023

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

@RealAnna RealAnna marked this pull request as draft February 16, 2023 13:33
@RealAnna RealAnna marked this pull request as ready for review February 16, 2023 15:21
@RealAnna RealAnna force-pushed the feat/add_probes branch 2 times, most recently from 22e03cd to c4a0299 Compare February 16, 2023 19:22
cmd/helmify/flags.go Outdated Show resolved Hide resolved
pkg/processor/deployment/deployment.go Outdated Show resolved Hide resolved
pkg/processor/deployment/deployment.go Outdated Show resolved Hide resolved
pkg/processor/deployment/deployment.go Outdated Show resolved Hide resolved
@RealAnna
Copy link
Contributor Author

RealAnna commented Mar 9, 2023

@arttor does this version make sense now ? 😸

@arttor
Copy link
Owner

arttor commented Mar 9, 2023

@RealAnna looks good. Can you please regenerate samples without using flags? Repo samples should represent default behavior.

@RealAnna
Copy link
Contributor Author

@arttor can this be merged now or should I fix something else?

@@ -98,6 +85,26 @@ spec:
subPath: controller_manager_config.yaml
- mountPath: /my.ca
name: secret-volume
{{- if .Values.controllerManager.manager.livenessProbe }}
Copy link
Owner

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?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah for consistency

Copy link
Owner

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 }}
Copy link
Owner

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?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok will do :)

Copy link
Contributor Author

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?

Copy link
Owner

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 <[email protected]>

feat: introduced liveness and readiness probes

Signed-off-by: RealAnna <[email protected]>

feat: introduced liveness and readiness probes

Signed-off-by: RealAnna <[email protected]>
Signed-off-by: RealAnna <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants