revise term WebLogic operator (#1292)

rosemarymarano · markxnelson · commit 743e1a1064c1 · 2019-10-07T21:02:52.000-04:00
diff --git a/docs-source/content/samples/simple/domains/domain-home-on-pv/_index.md b/docs-source/content/samples/simple/domains/domain-home-on-pv/_index.md
@@ -14,7 +14,7 @@ Before you begin, read this document, [Domain resource]({{< relref "/userguide/m
 
 The following prerequisites must be handled prior to running the create domain script:
 
-* Make sure the WebLogic operator is running.
+* Make sure the WebLogic Kubernetes Operator is running.
 * The operator requires WebLogic Server 12.2.1.3.0 with patch 29135930 applied. The existing WebLogic Docker image, `container-registry.oracle.com/middleware/weblogic:12.2.1.3`, has all the necessary patches applied. Refer to [WebLogic Docker images]({{< relref "/userguide/managing-domains/domain-in-image/base-images/_index.md" >}}) for details on how to obtain or create the image.
 * Create a Kubernetes namespace for the domain unless you intend to use the default namespace.
 * In the same Kubernetes namespace, create the Kubernetes persistent volume (PV) where the domain home will be hosted, and the Kubernetes persistent volume claim (PVC) for the domain. For samples to create a PV and PVC, see [Create sample PV and PVC]({{< relref "/samples/simple/storage/_index.md" >}}). By default, the `create-domain.sh` script creates a domain with the `domainUID` set to `domain1` and expects the PVC `domain1-weblogic-sample-pvc` to be present. You can create `domain1-weblogic-sample-pvc` using [create-pv-pvc.sh](https://github.com/oracle/weblogic-kubernetes-operator/blob/master/kubernetes/samples/scripts/create-weblogic-domain-pv-pvc/create-pv-pvc.sh) with an inputs file that has the `domainUID` set to `domain1`.
diff --git a/docs-source/content/samples/simple/domains/fmw-domain/_index.md b/docs-source/content/samples/simple/domains/fmw-domain/_index.md
@@ -19,7 +19,7 @@ Before you begin, read this document, [Domain resource]({{< relref "/userguide/m
 
 The following prerequisites must be handled prior to running the create domain script:
 
-* Make sure the WebLogic operator is running.
+* Make sure the WebLogic Kubernetes Operator is running.
 * The operator requires FMW Infrastructure 12.2.1.3.0 with patch 29135930 applied. For details on how to obtain or create the image, refer to [FMW Infrastructure domains]({{< relref "/userguide/managing-domains/fmw-infra/_index.md#obtaining-the-fmw-infrastructure-docker-image" >}}).
 * Create a Kubernetes namespace for the domain unless you intend to use the default namespace.
 * In the same Kubernetes namespace, create the Kubernetes persistent volume (PV) where the domain
diff --git a/docs-source/content/samples/simple/elastic-stack/operator/_index.md b/docs-source/content/samples/simple/elastic-stack/operator/_index.md
@@ -6,7 +6,7 @@ description: "Sample for configuring the Elasticsearch and Kibana deployments an
 ---
 
 
-When you install the WebLogic operator Helm chart, you can set
+When you install the WebLogic Kubernetes Operator Helm chart, you can set
 `elkIntegrationEnabled` to `true` in your `values.yaml` file to tell the operator to send the contents of the operator's logs to Elasticsearch.
 
 Typically, you would have already configured Elasticsearch and Kibana in the
diff --git a/docs-source/content/samples/simple/rest/_index.md b/docs-source/content/samples/simple/rest/_index.md
@@ -26,7 +26,7 @@ $ kubernetes/samples/scripts/rest/generate-external-rest-identity.sh \
 ```
 
 Where `<SANs>` lists the subject alternative names to put into the generated self-signed
-certificate for the external WebLogic Operator REST HTTPS interface, `<operator-namespace>` should match
+certificate for the external WebLogic Kubernetes Operator REST HTTPS interface, `<operator-namespace>` should match
 the namespace where the operator will be installed, and optionally the secret name, which defaults
 to `weblogic-operator-external-rest-identity`.
 
diff --git a/docs-source/content/security/domain-security/_index.md b/docs-source/content/security/domain-security/_index.md
@@ -2,7 +2,7 @@
 title: "Domain security"
 date: 2019-03-08T19:17:42-05:00
 weight: 2
-description: "WebLogic domain security and the WebLogic operator"
+description: "WebLogic domain security and the operator"
 ---
 
 {{% children style="h4" description="true" %}}
diff --git a/docs-source/content/security/encryption.md b/docs-source/content/security/encryption.md
@@ -2,17 +2,17 @@
 title: "Encryption"
 date: 2019-02-23T17:36:29-05:00
 weight: 3
-description: "WebLogic domain encryption and the WebLogic operator"
+description: "WebLogic domain encryption and the operator"
 ---
 #### Contents
 
-* [WebLogic operator introspector encryption](#weblogic-operator-introspector-encryption")
+* [WebLogic Kubernetes Operator introspector encryption](#weblogic-kubernetes-operator-introspector-encryption")
 * [Encryption of Kubernetes secrets](#encryption-of-kubernetes-secrets")
 * [Additional reading](#additional-reading)
 
-#### WebLogic operator introspector encryption
+#### WebLogic Kubernetes Operator introspector encryption
 
-The WebLogic operator has an introspection job that handles WebLogic domain encryption.
+The WebLogic Kubernetes Operator has an introspection job that handles WebLogic domain encryption.
 The introspection also addresses use of Kubernetes secrets for use with configuration overrides.
 For additional information on the configuration handling, see the
 [configuration overrides]({{<relref "/userguide/managing-domains/configoverrides/_index.md">}})
diff --git a/docs-source/content/security/rbac.md b/docs-source/content/security/rbac.md
@@ -39,7 +39,7 @@ For more information about Kubernetes roles, see the
 #### Operator RBAC definitions
 
 To display the Kubernetes roles and related bindings used by
-the WebLogic operator where the operator was installed using the
+the operator where the operator was installed using the
 Helm release name `weblogic-operator`, look for the Kubernetes objects:
 
 - `Role`
@@ -112,7 +112,7 @@ A complete name for an operator created Kubernetes `ClusterRoleBinding` would be
 
 #### Role bindings
 
-Assuming that the WebLogic operator was installed into the Kubernetes namespace `weblogic-operator-ns`,
+Assuming that the operator was installed into the Kubernetes namespace `weblogic-operator-ns`,
 and a target namespace for the operator is `domain1-ns`, the following `RoleBinding` entries are mapped
 to a `Role` or `ClusterRole` granting permission to the operator.
 
@@ -125,7 +125,7 @@ to a `Role` or `ClusterRole` granting permission to the operator.
 
 #### Cluster role bindings
 
-Assuming that the WebLogic operator was installed into the Kubernetes namespace `weblogic-operator-ns`,
+Assuming that the operator was installed into the Kubernetes namespace `weblogic-operator-ns`,
 the following `ClusterRoleBinding` entries are mapped to a `ClusterRole` granting permission to the operator.
 
 **Note**: The Operator names in table below represent the `<role-name>` from [cluster names](#kubernetes-cluster-role-and-cluster-role-binding-naming-convention) section.
diff --git a/docs-source/content/security/secrets.md b/docs-source/content/security/secrets.md
@@ -8,10 +8,10 @@ description: "Kubernetes secrets for the WebLogic Kubernetes Operator"
 #### Contents
 * [WebLogic domain credentials secret](#weblogic-domain-credentials-secret)
 * [WebLogic domain image pull secret](#weblogic-domain-image-pull-secret)
-* [WebLogic operator image pull secret](#weblogic-operator-image-pull-secret)
-* [WebLogic operator configuration override secrets](#weblogic-operator-configuration-override-secrets)
-* [WebLogic operator external REST interface secret](#weblogic-operator-external-rest-interface-secret)
-* [WebLogic operator internal REST interface secret](#weblogic-operator-internal-rest-interface-secret)
+* [WebLogic Kubernetes Operator image pull secret](#weblogic-kubernetes-operator-image-pull-secret)
+* [WebLogic Kubernetes Operator configuration override secrets](#weblogic-kubernetes-operator-configuration-override-secrets)
+* [WebLogic Kubernetes Operator external REST interface secret](#weblogic-kubernetes-operator-external-rest-interface-secret)
+* [WebLogic Kubernetes Operator internal REST interface secret](#weblogic-kubernetes-operator-internal-rest-interface-secret)
 
 #### WebLogic domain credentials secret
 
@@ -24,7 +24,7 @@ For an example of a WebLogic domain resource using `webLogicCredentialsSecret`,
 see [Docker Image Protection]({{<relref "/security/domain-security/image-protection.md#1-use-imagepullsecrets-with-the-domain-resource">}}).
 {{% /notice %}}
 
-The samples supplied with the WebLogic operator use a naming convention that follows
+The samples supplied with the operator use a naming convention that follows
 the pattern `<domainUID>-weblogic-credentials`, where `<domainUID>` is
 the unique identifier of the domain, for example, `domain1-weblogic-credentials`.
 
@@ -47,7 +47,7 @@ tooling. For more information about creating Kubernetes secrets, see the Kuberne
 documentation.
 {{% /notice %}}
 
-The WebLogic operator's introspector job will expect the secret key names to be:
+The operator's introspector job will expect the secret key names to be:
 
 - `username`
 - `password`
@@ -80,7 +80,7 @@ For more information, see [Docker Image Protection]({{<relref "/security/domain-
 under **Domain security**.
 {{% /notice %}}
 
-#### WebLogic operator image pull secret
+#### WebLogic Kubernetes Operator image pull secret
 
 The Helm chart for installing the operator has an option to specify the
 image pull secret used for the operator's image when using a private registry.
@@ -102,9 +102,9 @@ For more information, see
 under **User Guide**.
 {{% /notice %}}
 
-#### WebLogic operator configuration override secrets
+#### WebLogic Kubernetes Operator configuration override secrets
 
-The WebLogic operator supports embedding macros within configuration override templates
+The operator supports embedding macros within configuration override templates
 that reference Kubernetes secrets. These Kubernetes secrets can be created with any name in the
 namespace where the `Domain` will be running. The Kubernetes secret names are
 specified using `configOverrideSecrets` in the WebLogic `Domain` resource.
@@ -115,7 +115,7 @@ For more information, see
 under **User Guide**.
 {{% /notice %}}
 
-#### WebLogic operator external REST interface secret
+#### WebLogic Kubernetes Operator external REST interface secret
 
 The operator can expose an external REST HTTPS interface which can be
 accessed from outside the Kubernetes cluster. A Kubernetes `tls secret`
@@ -126,13 +126,13 @@ For more information, see [Certificates]({{<relref "/security/certificates.md#re
 under **Securty**.
 {{% /notice %}}
 
-#### WebLogic operator internal REST interface secret
+#### WebLogic Kubernetes Operator internal REST interface secret
 
 The operator exposes an internal REST HTTPS interface with a self-signed certificate.
 The certificate is kept in a Kubernetes `ConfigMap` with the name `weblogic-operator-cm` using the key `internalOperatorCert`.
 The private key is kept in a Kubernetes `Secret` with the name `weblogic-operator-secrets` using the key `internalOperatorKey`.
 These Kubernetes objects are managed by the operator's Helm chart and are part of the
-namespace where the WebLogic operator is installed.
+namespace where the operator is installed.
 
 For example, to see all the operator's config maps and secrets when installed into
 the Kubernetes namespace `weblogic-operator-ns`, use:
diff --git a/docs-source/content/security/service-accounts.md b/docs-source/content/security/service-accounts.md
@@ -6,23 +6,23 @@ description: "Kubernetes service accounts for the WebLogic Kubernetes Operator"
 ---
 
 
-#### WebLogic operator service account
+#### WebLogic Kubernetes Operator service account
 
-When the WebLogic operator is installed, the Helm chart property, `serviceAccount`, can
+When the operator is installed, the Helm chart property, `serviceAccount`, can
 be specified where the value contains the name of the Kubernetes `ServiceAccount`
-in the namespace in which the WebLogic operator will be installed.
+in the namespace in which the operator will be installed.
 For more information about the Helm chart, see the
 [operator Helm configuration values]({{<relref "/userguide/managing-operators/using-the-operator/using-helm/_index.md#operator-helm-configuration-values">}}).
 
-The WebLogic operator will use this `ServiceAccount` when calling the Kubernetes API server
+The operator will use this `ServiceAccount` when calling the Kubernetes API server
 and the appropriate access controls will be created for this `ServiceAccount` by
 the operator's Helm chart.
 
 {{% notice info %}}
 For more information about access controls, see [RBAC]({{<relref "/security/rbac.md">}}) under **Security**.
 {{% /notice %}}
 
-In order to display the `ServiceAccount` used by the WebLogic operator,
+In order to display the `ServiceAccount` used by the operator,
 where the operator was installed using the Helm release name `weblogic-operator`,
 look for the `serviceAccount` value using the Helm command:
 ```bash
diff --git a/docs-source/content/userguide/managing-domains/_index.md b/docs-source/content/userguide/managing-domains/_index.md
@@ -80,7 +80,7 @@ Please consult My Oracle Support Doc ID 2349228.1 for up-to-date information abo
 ### Creating and managing WebLogic domains
 
 You can locate a WebLogic domain either in a persistent volume (PV) or in a Docker image.
-For examples of each, see the [WebLogic operator samples]({{< relref "/samples/simple/domains/_index.md" >}}).
+For examples of each, see the [WebLogic Kubernetes Operator samples]({{< relref "/samples/simple/domains/_index.md" >}}).
 
 If you want to create your own Docker images, for example, to choose a specific set of patches or to create a domain
 with a specific configuration and/or applications deployed, then you can create the domain custom resource
diff --git a/docs-source/content/userguide/managing-domains/domain-lifecycle/scaling.md b/docs-source/content/userguide/managing-domains/domain-lifecycle/scaling.md
@@ -170,11 +170,11 @@ Set this to https://${KUBERNETES_SERVICE_HOST}:${KUBERNETES_SERVICE_PORT} when i
 
 * `wls_domain_namespace` - Kubernetes namespace in which the WebLogic domain is defined, default=`default`
 
-* `operator_service_name` - WebLogic Operator Service name of the REST endpoint, default=`internal-weblogic-operator-service`
+* `operator_service_name` - WebLogic Kubernetes Operator Service name of the REST endpoint, default=`internal-weblogic-operator-service`
 
-* `operator_service_account` - Kubernetes Service Account name for the WebLogic Operator, default=`weblogic-operator`
+* `operator_service_account` - Kubernetes Service Account name for the operator, default=`weblogic-operator`
 
-* `operator_namespace` – Namespace in which the WebLogic Operator is deployed, default=`weblogic-operator`
+* `operator_namespace` – Namespace in which the operator is deployed, default=`weblogic-operator`
 
 * `scaling_size` – Incremental number of WebLogic Server instances by which to scale up or down, default=`1`
 
diff --git a/docs-source/content/userguide/managing-domains/domain-resource.md b/docs-source/content/userguide/managing-domains/domain-resource.md
@@ -10,15 +10,15 @@ pre = "<b> </b>"
 
 Use this document to set up and configure your own [domain resource](https://github.com/oracle/weblogic-kubernetes-operator/blob/master/docs/domains/Domain.md) which can be used to configure the operation of your WebLogic domain. The domain resource does not replace the traditional configuration of WebLogic domains found in the domain configuration files, but instead cooperates with those files to describe the Kubernetes artifacts of the corresponding domain.  For instance, the WebLogic domain configuration will still specify deployed applications, data sources, and most other details about the domain while the domain resource will specify the number of cluster members currently running or the persistent volumes that will be mounted into the containers running WebLogic Server instances.
 
-Many of the samples accompanying the operator project include scripts to generate an initial domain resource from a set of simplified inputs; however, the domain resource is the actual source of truth for how the WebLogic operator will manage each WebLogic domain.  You are encouraged to either start with the domain resource YAML files generated by the various samples or create domain resources manually or by using other tools based on the schema referenced here or this documentation.
+Many of the samples accompanying the operator project include scripts to generate an initial domain resource from a set of simplified inputs; however, the domain resource is the actual source of truth for how the operator will manage each WebLogic domain.  You are encouraged to either start with the domain resource YAML files generated by the various samples or create domain resources manually or by using other tools based on the schema referenced here or this documentation.
 
 Swagger documentation is available [here](https://oracle.github.io/weblogic-kubernetes-operator/swagger/index.html).
 
 #### Prerequisites
 
 The following prerequisites must be fulfilled before proceeding with the creation of the resource:
 
-* Make sure the WebLogic operator is running.
+* Make sure the WebLogic Kubernetes Operator is running.
 * Create a Kubernetes namespace for the domain resource unless the intention is to use the default namespace.
 * Create the Kubernetes secrets containing the `username` and `password` of the administrative account in the same Kubernetes namespace as the domain resource.
 
diff --git a/docs-source/content/userguide/managing-domains/ingress/_index.md b/docs-source/content/userguide/managing-domains/ingress/_index.md
@@ -15,7 +15,7 @@ for more information about Ingresses.
 In an Ingress object, a list of backends are provided for each target that will be load balanced.  Each backend is typically
 [a Kubernetes service](https://kubernetes.io/docs/concepts/services-networking/service/), more specifically, a combination of a `serviceName` and a `servicePort`.
 
-When the WebLogic operator creates a WebLogic domain, it also creates a service for each WebLogic cluster in the domain.
+When the operator creates a WebLogic domain, it also creates a service for each WebLogic cluster in the domain.
 The operator defines the service such that its selector will match all WebLogic server pods within the WebLogic cluster
 which are in the "ready" state.
 
diff --git a/docs-source/content/userguide/managing-operators/installation/_index.md b/docs-source/content/userguide/managing-operators/installation/_index.md
@@ -42,7 +42,7 @@ You can verify the operator installation by examining the output from the `helm
 
 {{% notice note %}}
 When the operator image is stored in a private registry, see
-[WebLogic operator image pull secret]({{<relref "/security/secrets.md#weblogic-operator-image-pull-secret">}})
+[WebLogic Kubernetes Operator image pull secret]({{<relref "/security/secrets.md#weblogic-kubernetes-operator-image-pull-secret">}})
 for more information on specifying the registry credentials.
 {{% /notice %}}
 
diff --git a/docs-source/content/userguide/managing-operators/using-the-operator/using-helm.md b/docs-source/content/userguide/managing-operators/using-the-operator/using-helm.md
@@ -237,7 +237,7 @@ externalRestHttpsPort: 32009
 
 ##### `externalRestIdentitySecret`
 
-Specifies the user supplied secret that contains the SSL/TLS certificate and private key for the external operator REST HTTPS interface. The value must be the name of the Kubernetes tls secret previously created in the namespace where the WebLogic operator is deployed. This parameter is required if `externalRestEnabled` is `true`, otherwise, it is ignored. In order to create the Kubernetes tls secret you can use the following command:
+Specifies the user supplied secret that contains the SSL/TLS certificate and private key for the external operator REST HTTPS interface. The value must be the name of the Kubernetes `tls` secret previously created in the namespace where the operator is deployed. This parameter is required if `externalRestEnabled` is `true`, otherwise, it is ignored. In order to create the Kubernetes `tls` secret you can use the following command:
 
 ```
 $ kubectl create secret tls <secret-name> \
diff --git a/docs-source/content/userguide/overview/prepare.md b/docs-source/content/userguide/overview/prepare.md
@@ -18,7 +18,7 @@ After creating Kubernetes clusters, you can optionally:
 
 #### Load balance with an Ingress controller or a web server
 
-You can choose a load balancer provider for your WebLogic domains running in a Kubernetes cluster. Please refer to the [WebLogic Operator Load Balancer Samples](https://github.com/oracle/weblogic-kubernetes-operator/blob/master/kubernetes/samples/charts/README.md) for information about the current capabilities and setup instructions for each of the supported load balancers.
+You can choose a load balancer provider for your WebLogic domains running in a Kubernetes cluster. Please refer to the [WebLogic Kubernetes Operator Load Balancer Samples](https://github.com/oracle/weblogic-kubernetes-operator/blob/master/kubernetes/samples/charts/README.md) for information about the current capabilities and setup instructions for each of the supported load balancers.
 
 
 #### Configure Kibana and Elasticsearch
