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

Probes are defaulted on, but can be totally overriden #41

Merged
merged 1 commit into from
Sep 13, 2024

Conversation

mbirchdk
Copy link
Contributor

No description provided.

@mbirchdk mbirchdk merged commit 7920f76 into master Sep 13, 2024
1 check passed
@mbirchdk mbirchdk deleted the totallyCustomProbes branch September 13, 2024 12:55
@mbirchdk
Copy link
Contributor Author

Jeg ville gerne videre - Så jeg har merget - Jeg laver gerne ændringer på efterkrav! :-)

timeoutSeconds: 5
{{- toYaml .Values.kitcaddy.startupProbe | nindent 12 }}
{{- end }}
{{- if .Values.kitcaddy.readinessProbe }}
readinessProbe:
Copy link
Contributor

Choose a reason for hiding this comment

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

Nu vi er så godt i gang med at pille, burde vi ikke give mulighed for at definere en liveness probe også?

path: /metrics
port: 80
scheme: HTTP
initialDelaySeconds: 50
Copy link
Contributor

Choose a reason for hiding this comment

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

Jeg synes ikke jeg oplever at det er normalt at det tager så lang tid for Kitcaddy for at være klar. Normalt plejer Kitcaddy at starte op på meget kort tid (< 1sek).

Kan det være en ting i Netic miljøet der gør at det tager så lang tid? Så synes jeg default skal være lavere, så det ikke går ud over andre anvendere af Kitcaddy.

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