-
Notifications
You must be signed in to change notification settings - Fork 7
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
Readiness en live probe for admin deployment #34
Comments
You can try to use a TCP readiness check for this if the application is available when the socket is, this works fine. Example:
Ofcourse the best is to have a /healthz endpoint that returns the code expected for instance https://github.com/joelwallis/express-healthz |
yes I implemented the health checks but for some reason it kept returning a
forbidden.
Op do 25 jun. 2020 om 19:44 schreef Jaap Gorjup <[email protected]>:
… You can try to use a TCP readiness check for this if the application is
available when the socket is, this works fine.
Example:
readinessProbe:
tcpSocket:
port: 8080
initialDelaySeconds: 5
periodSeconds: 10
livenessProbe:
tcpSocket:
port: 8080
initialDelaySeconds: 15
periodSeconds: 20
Ofcourse the best is to have a /healthz endpoint that returns the code
expected for instance https://github.com/joelwallis/express-healthz
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<https://github.com/Amsterdam/openstad-kubernetes/issues/34#issuecomment-649725845>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJEFAEMEC422EEGNB6XZNDRYOEJBANCNFSM4OELRFFQ>
.
|
When forwarding the port it worked fine.
Op do 25 jun. 2020 om 22:16 schreef Tosh Koevoets <[email protected]>:
… yes I implemented the health checks but for some reason it kept returning
a forbidden.
Op do 25 jun. 2020 om 19:44 schreef Jaap Gorjup ***@***.***
>:
> You can try to use a TCP readiness check for this if the application is
> available when the socket is, this works fine.
>
> Example:
>
> readinessProbe:
> tcpSocket:
> port: 8080
> initialDelaySeconds: 5
> periodSeconds: 10
> livenessProbe:
> tcpSocket:
> port: 8080
> initialDelaySeconds: 15
> periodSeconds: 20
>
> Ofcourse the best is to have a /healthz endpoint that returns the code
> expected for instance https://github.com/joelwallis/express-healthz
>
> —
> You are receiving this because you were assigned.
> Reply to this email directly, view it on GitHub
> <https://github.com/Amsterdam/openstad-kubernetes/issues/34#issuecomment-649725845>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAJEFAEMEC422EEGNB6XZNDRYOEJBANCNFSM4OELRFFQ>
> .
>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Readiness en live probe for admin deployment is currently turned off.
Gets a forbidden warning. Probably connected to the basic auth of the container.
The text was updated successfully, but these errors were encountered: