1.1.1 docs (#827)

* OTEL update

* Tracing update

* APISIX password update

* APISIX updates

* Sample app update

* updates for 400 auto-scaling

Signed-off-by: Mark Nelson <mark.x.nelson@oracle.com>

* general review and updates

Signed-off-by: Mark Nelson <mark.x.nelson@oracle.com>

* add soc docs

Signed-off-by: Mark Nelson <mark.x.nelson@oracle.com>

* Update _index.md

---------

Signed-off-by: Mark Nelson <mark.x.nelson@oracle.com>
Co-authored-by: Andy Tael <andy.tael@yahoo.com>

Author: markxnelson

docs-source/spring/content/platform/soc/_index.md

@@ -23,8 +23,11 @@ resources:
     title: "SOC Manage Identity screen"
 ---
 
-Oracle Backend for Spring Boot and Microservices version 1.1.1 includes a preview of a new feature called "Spring Operations Center". The Spring Operations Center provides a web user interface to manage the Oracle Backend for Spring Boot and Microservices.
 
+Oracle Backend for Spring Boot and Microservices version 1.1.1 includes a preview of a new feature called "Spring Operations Center".
+More capabilities will be added to this feature in future releases.
+
+The Spring Operations Center provides a web user interface to manage the Oracle Backend for Spring Boot and Microservices.
 This preview release includes the following capabilities:
 
 - View details about the configuration and health of the environment
@@ -45,13 +48,17 @@ ingress-nginx-controller   LoadBalancer   10.96.172.148   100.200.100.200   80:3
 
 Use the `EXTERNAL-IP` from the results and open a browser to https://100.200.100.200/soc to access the login page.
 
-**Note**: If you installed with self-signed certificates, which is the default, you will see a browser warning message and will have to click on "Accept risk" or similar. For information about replacing the self-signed certificate with a production certificate, refer to [Transport Layer Security](../../security#transport-layer-security)
+**Note**: If you installed with self-signed certificates, which is the default, you will see a browser warning message and
+will have to click on "Accept risk" or similar. For information about replacing the self-signed certificate with a
+production certicate, refer to [Transport Layer Security](../../security#transport-layer-security)
 
 <!-- spellchecker-disable -->
 {{< img name="soc-login-page" size="medium" lazy=false >}}
 <!-- spellchecker-enable -->
 
-Login using the `obaas-admin` user (or another user if you have created one) and the password that you set during installation. If you did not set a password, one was auto-generated for you and can be obtained with this command:
+Login using the `obaas-admin` user (or another user if you have created one) and the password
+that you set during installation.  If you did not set a password, one was auto-generated for you and can be
+obtain with this command: 
 
 ```bash
 $ kubectl get secret -n azn-server oractl-passwords -o jsonpath='{.data.admin}' | base64 -d
@@ -76,17 +83,22 @@ The Spring Operations Center Dashboard provides information about the overall st
 
 ### Manage Namespaces
 
-The Manage Namespaces screen is accessible from the *Workloads* menu, and allows you to view and manage the namespaces that are configured for Spring Boot application deployments.  Note that this does not show you all namespaces in the Kubernetes cluster, just those that have be specifically configured for Spring Boot workloads, meaning they have the necessary secrets for pulling images, accessing the database, and so on.
+The Manage Namespaces screen is accessible from the *Workloads* menu, and allows you to view and manage the namespaces
+that are configured for Spring Boot application deployments.  Note that this does not show you all namespaces in the
+Kubernetes cluster, just those that have be specifically configured for Spring Boot workloads, meaning they have
+the necessary secrets for pulling images, accessing the database, and so on.
 
 <!-- spellchecker-disable -->
 {{< img name="soc-manage-namespaces" size="medium" lazy=false >}}
 <!-- spellchecker-enable -->
 
-Clicking on a namespace will allow you to drill down into that namespace and see the workloads (Spring Boot applications) deployed there.
+Clicking on a namespace will allow you to drill down into that namespace and see the workloads (Spring Boot applications)
+deployed there.
 
 ### Manage Workloads
 
-The Manage Workloads screen shows the workloads (Spring Boot applications) deployed in a specific namespace, including the status of each workload, and how many replicas are currently running and desired.
+The Manage Workloads screen shows the workloads (Spring Boot applications) deployed in a specific namespace, including
+the status of each workload, and how many replicas are currently running and desired. 
 
 <!-- spellchecker-disable -->
 {{< img name="soc-manage-workloads" size="medium" lazy=false >}}
@@ -102,7 +114,8 @@ More details of this dashboard can be found [here](../../observability/metrics/#
 
 ### Manage Identity
 
-The Manage Identity screen is accessible from the Security menu and allows you to view information about the users and roles defined in the Spring Authorization Server included in the platform.
+The Manage Identity screen is accessible from the Security menu and allows you to view information
+about the users and roles defined in the Spring Authorization Server included in the platform.
 
 <!-- spellchecker-disable -->
 {{< img name="soc-manage-identity" size="medium" lazy=false >}}

docs-source/spring/content/security/_index.md

@@ -24,6 +24,7 @@ The Oracle Backend for Spring Boot and Microservices has the following security
 
 - Oracle Backend for Spring Boot and Microservices contains HashiCorp Vault to secure, store and tightly control access to tokens, passwords, certificates, encryption keys for protecting secrets, and other sensitive data. [HashiCorp Vault Documentation](../platform/vault)
 
+
 ## Transport Layer Security
 
 The Oracle Backend for Spring Boot and Microservices is deployed with a sample self-signed certificate for Transport Layer Security (TLS). This results in an "Accept Risk" message when accessing the Spring Operations Center or Grafana web user interfaces and the sample TLS certificate should not be used for production deployments.
@@ -50,3 +51,4 @@ The Oracle Backend for Spring Boot and Microservices is deployed with a sample s
         -p '{"metadata":{"annotations":{"service.beta.kubernetes.io/oci-load-balancer-tls-secret":"my-tls-cert"}}}' \
         --type=merge
     ```
+

docs-source/spring/content/setup/_index.md

@@ -110,7 +110,7 @@ Oracle Backend for Spring Boot and Microservices setup installs the following co
 | Apache APISIX                | 3.8.0         | Provides full lifecycle API management.                                                     |
 | Apache Kafka                 | 3.6.1 | Provides distributed event streaming.                                                       |
 | cert-manager                 | 1.12.3        | Automates the management of certificates.                                                   |
-| Coherence                    | 3.3.2        | Provides in-memory data grid.                                                               |
+| Coherence Operator           | 3.3.2        | Provides in-memory data grid.                                                               |
 | Conductor Server             | 3.13.8        | Provides a Microservice orchestration platform.                                             |
 | Grafana                      | 9.2.5         | Provides the tool to examine, analyze, and monitor metrics.                                 |
 | HashiCorp Vault              | 1.15.2        | Provides a way to store and tightly control access to sensitive data.                       |