| copyright |
|
||
|---|---|---|---|
| lastupdated | 2026-03-05 | ||
| keywords | openshift, {{site.data.keyword.openshiftlong_notm}}, best practices | ||
| subcollection | openshift |
{{site.data.keyword.attribute-definition-list}}
{: #best-practices-service} {: support}
{: #bp-1}
Check monthly for available security and operating system patches to update your worker nodes.
Make sure to update your cluster regularly to remain on a supported version {{site.data.keyword.redhat_openshift_notm}}.
{: #bp-2}
In the command line, you are notified when updates to the ibmcloud CLI and plug-ins are available. Be sure to keep your CLI up-to-date so that you can use all available commands and options.
Make sure that your oc CLI client matches the same Kubernetes version as your cluster server. Kubernetes does not support{: external} oc client versions that are 2 or more versions apart from the server version (n +/- 2).
{: #bp-ca}
Regular rotation of certificate authority (CA) certificates is recommended for security purposes. The steps for CA rotation include reloading or replacing worker nodes, so consider rotating CA certificates whenever you update your worker nodes. For more information, see Rotating CA certificates in your cluster.
{: #bp-3}
Maintaining up-to-date documentation and diagrams can help when debugging issues. For more information, see Documenting your environment architecture.
{: #bp-4}
You can receive documentation release notes for {{site.data.keyword.openshiftlong_notm}} via RSS. For more information, see Subscribing to an RSS feed.