AWS prescriptive-guidance low security documentation change
Summary
Updated OpenShift documentation link from version 4.7 to 4.6 and removed backticks from CLI tool names
Security assessment
The change references security guidelines for cluster administration (removing default admin) and corrects documentation versioning. While not fixing an active vulnerability, it ensures alignment with validated security practices for OpenShift 4.6, impacting secure cluster configuration.
Diff
diff --git a/prescriptive-guidance/latest/red-hat-openshift-on-aws-implementation/best-practices.md b/prescriptive-guidance/latest/red-hat-openshift-on-aws-implementation/best-practices.md index f934b8386..5de0e3175 100644 --- a//prescriptive-guidance/latest/red-hat-openshift-on-aws-implementation/best-practices.md +++ b//prescriptive-guidance/latest/red-hat-openshift-on-aws-implementation/best-practices.md @@ -13 +13 @@ Follow these best practices when you set up a Red Hat OpenShift cluster on AWS: - * Review security guidelines. For example, you might consider [removing the default cluster administrator](https://docs.openshift.com/container-platform/4.7/authentication/remove-kubeadmin.html) after installation. + * Review security guidelines. For example, you might consider [removing the default cluster administrator](https://docs.openshift.com/container-platform/4.6/authentication/remove-kubeadmin.html) after installation. @@ -15 +15 @@ Follow these best practices when you set up a Red Hat OpenShift cluster on AWS: - * Check the compatibility of all command-line tools, including OpenShift CLI (`oc`), Kubernetes command line tool (`kubectl`), AWS CLI, and `rosa` CLI. + * Check the compatibility of all command line tools, including OpenShift CLI (oc), Kubernetes command line tool (kubectl), AWS CLI, and rosa CLI.