Create a URL within the app for Kubernetes to validate the "liveness" of the container and prevent connections until it is verified as "live". Should only be in "live" status if there are no startup errors to the BellScheduler app, especially if it cannot connect to MySQL.
Currently the liveness probe goes to /login, but that page will still appear properly even if the app cannot connect to the database.
Create a URL within the app for Kubernetes to validate the "liveness" of the container and prevent connections until it is verified as "live". Should only be in "live" status if there are no startup errors to the BellScheduler app, especially if it cannot connect to MySQL.
Currently the liveness probe goes to ```/login```, but that page will still appear properly even if the app cannot connect to the database.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Create a URL within the app for Kubernetes to validate the "liveness" of the container and prevent connections until it is verified as "live". Should only be in "live" status if there are no startup errors to the BellScheduler app, especially if it cannot connect to MySQL.
Currently the liveness probe goes to
/login, but that page will still appear properly even if the app cannot connect to the database.done