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

Readiness en live probe for admin deployment #34

Open
ToshKoevoets opened this issue Jun 22, 2020 · 3 comments
Open

Readiness en live probe for admin deployment #34

ToshKoevoets opened this issue Jun 22, 2020 · 3 comments
Assignees

Comments

@ToshKoevoets
Copy link
Collaborator

Readiness en live probe for admin deployment is currently turned off.

Gets a forbidden warning. Probably connected to the basic auth of the container.

@ToshKoevoets ToshKoevoets self-assigned this Jun 22, 2020
@jaapgorjup
Copy link
Collaborator

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

@ToshKoevoets
Copy link
Collaborator Author

ToshKoevoets commented Jun 25, 2020 via email

@ToshKoevoets
Copy link
Collaborator Author

ToshKoevoets commented Jun 25, 2020 via email

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

No branches or pull requests

2 participants