# Upgrade Policy ## General Sysadmins should be aware of the effects of failures to critical production services. Therefore, it is recommended (and highly highly encouraged) to restrict updates to these services to a minimum. Depending on the criticality of the service and the extent of the updates, these updates should be: * restricted to periods of low usage * restricted in scope as to not obstruct normal operation * minimized as to not cause wide-scale damage should the upgrade fail Additionally, for upgrades to highly critical production systems, a consultation should be made with the Lead Sysadmins and other Sysadmins relying on such systems. Examples of critical production services include underlying systems that provide infrastructure for other services like Ceph, networking, and DNS. ## The Gist Be careful upgrading production services. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://documentation.tjhsst.edu/policies/upgrade-policy.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.