CSPL-3586: Document FIPS Compliance for SOK (#1501)

* document FIPS compliance for SOK

* copilot updates

* add line space

Author: rlieberman-splunk

docs/ChangeLog.md

@@ -4,6 +4,8 @@
 
 * This is the 2.8.0 release. The Splunk Operator for Kubernetes is a supported platform for deploying Splunk Enterprise with the prerequisites and constraints laid out [here](https://github.com/splunk/splunk-operator/blob/main/docs/README.md#prerequisites-for-the-splunk-operator)
 
+* CSPL-3586 - Certify FIPS 140-3 Compliance
+
 * CSPL-3624 - Update Helm Charts for 2.8.0 Support
 
 * CSPL-3673 - Github Issue #1157: Failed to install the operator - CRD metadata.annotations too long

docs/Security.md

@@ -19,7 +19,7 @@ The procedures to secure your deployment are the same regardless of your choice
 |Splunk Web   | Gateway Termination | NO  |
 |REST API   | Gateway Termination | NO  |
 
-For more information about how to setup Ingress Controllers using the Operator visit [Ingress Documentation](https://github.com/splunk/splunk-operator/blob/develop/docs/Ingress.md).
+For more information about how to setup Ingress Controllers using the Operator visit [Ingress Documentation](https://github.com/splunk/splunk-operator/blob/main/docs/Ingress.md).
 
 ## Prerequisites
 
@@ -74,7 +74,7 @@ privKeyPath = $SPLUNK_HOME/etc/apps/myapp/mycerts/mySplunkPrivateKey.key
 serverCert =  $SPLUNK_HOME/etc/apps/myapp/mycerts/mySplunkCertificate.pem
 ```
 
-* Deploy the app to the Splunk Enterprise instance. See [Install Apps using Splunk Operator](https://github.com/splunk/splunk-operator/blob/develop/docs/Examples.md#installing-splunk-apps). 
+* Deploy the app to the Splunk Enterprise instance. See [Install Apps using Splunk Operator](https://github.com/splunk/splunk-operator/blob/main/docs/Examples.md#installing-splunk-apps). 
 
 * Create the Ingress configuration to allow access to port 8000. This configuration creates a gateway and virtual service for passing the traffic through to the Splunk Enterprise instance.
 
@@ -219,9 +219,13 @@ Learn more about APIs available here: [REST Manual](https://docs.splunk.com/Docu
 
 ## Securing Forwarders
 
-For examples on configuring the Ingress controller to accept data from Forwarders, and securing the data in Kubernetes, see: [Secure Forwarding](https://github.com/splunk/splunk-operator/blob/develop/docs/Ingress.md)
+For examples on configuring the Ingress controller to accept data from Forwarders, and securing the data in Kubernetes, see: [Secure Forwarding](https://github.com/splunk/splunk-operator/blob/main/docs/Ingress.md)
 
 
 ## Password Management 
 
-In Kubernetes, sensitive information such as passwords, OAuth tokens, and ssh keys should be stored using the Secrets objects. Learn how to manage your passwords for Splunk Enterprise deployments in: [Password Management](https://github.com/splunk/splunk-operator/blob/develop/docs/PasswordManagement.md)
+In Kubernetes, sensitive information such as passwords, OAuth tokens, and ssh keys should be stored using the Secrets objects. Learn how to manage your passwords for Splunk Enterprise deployments in: [Password Management](https://github.com/splunk/splunk-operator/blob/main/docs/PasswordManagement.md)
+
+## Using a FIPS 140-3 Enabled Cluster
+
+The Splunk Operator for Kubernetes is fully certified to run on FIPS 140-3 compliant clusters. No modifications to the provided container images are required. To get started, simply create a Kubernetes cluster with FIPS-compliant nodes and follow the standard [installation guide](https://github.com/splunk/splunk-operator/blob/main/docs/Install.md) to deploy the operator.