-
Notifications
You must be signed in to change notification settings - Fork 10
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
Add healthcheck page for asserting health of application #2657
Conversation
@@ -2,4 +2,10 @@ class StaticPagesController < ApplicationController | |||
|
|||
skip_after_action :verify_authorized | |||
|
|||
def about; end |
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 should be explicit about our actions in our controllers? Not sure why we removed these. Adding them back!
Generated by 🚫 Danger |
68e0216
to
64971a3
Compare
Sidekiq.configure_server do |config| | ||
config.redis = { url: Rails.application.secrets.redis_url } | ||
|
||
schedule_file = 'config/schedule.yml' | ||
Sidekiq::Cron::Job.load_from_hash YAML.load_file(schedule_file) if File.exist?(schedule_file) | ||
|
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.
This is basically extracted from official sidekiq docs: https://github.com/mperham/sidekiq/wiki/Kubernetes#health-checks
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.
https://cloud.google.com/blog/products/containers-kubernetes/kubernetes-best-practices-setting-up-health-checks-with-readiness-and-liveness-probes
Add readiness healthcheck for jupiter and sidekiq processes. This will be very useful for Operations team or for readiness checking within Kubernetes