Remove bad references from documentation

rjeberhard · rjeberhard · commit 9bd0d9326de2 · 2025-12-18T14:58:44.000-05:00
diff --git a/documentation/site/content/base-images/custom-images.md b/documentation/site/content/base-images/custom-images.md
@@ -259,13 +259,6 @@ image that is meant for updating an already running domain, then see
 **NOTE**: The Domain in Image [domain home source type]({{< relref "/managing-domains/choosing-a-model/_index.md" >}}) is
 deprecated in WebLogic Kubernetes Operator version 4.0. Oracle recommends that you choose either Domain on PV or Model in Image, depending on your needs.
 
-For Domain in Image domains,
-you must create an image with the WebLogic domain inside the image.
-[Samples]({{< relref "/samples/domains/domain-home-in-image/_index.md" >}})
-are provided that demonstrate how to create the image using either
-WLST to define the domain
-or [WebLogic Deploy Tooling](https://oracle.github.io/weblogic-deploy-tooling/) models to define the domain.
-In these samples, you will see a reference to a "base" or `--fromImage` image.
 You should use an image with the recommended security patches installed as this base image,
 where this image could be an OCR image or a custom image.
 See
diff --git a/documentation/site/content/managing-domains/accessing-the-domain/remote-admin-console.md b/documentation/site/content/managing-domains/accessing-the-domain/remote-admin-console.md
@@ -26,7 +26,7 @@ along with the URL of the WebLogic Server Administration Server's administration
 
 **NOTES**:  
   * An Administration Server administration port typically is the same as its default port unless either an SSL port or an administration port is configured and enabled.
-  * If your domain home type is either [Domain in Image]({{< relref "/samples/domains/domain-home-in-image/_index.md" >}}) or [Model in Image]({{< relref "/samples/domains/model-in-image/_index.md" >}}), then do not use the WebLogic Remote Console to make changes to the WebLogic domain configuration because these changes are ephemeral and will be lost when servers restart. See [Choose a domain home source type]({{< relref "/managing-domains/choosing-a-model/_index.md" >}}).
+  * If your domain home type is either Domain in Image or [Model in Image]({{< relref "/samples/domains/model-in-image/_index.md" >}}), then do not use the WebLogic Remote Console to make changes to the WebLogic domain configuration because these changes are ephemeral and will be lost when servers restart. See [Choose a domain home source type]({{< relref "/managing-domains/choosing-a-model/_index.md" >}}).
 
 
 {{% notice warning %}}
diff --git a/documentation/site/content/managing-domains/accessing-the-domain/weblogic-admin-console.md b/documentation/site/content/managing-domains/accessing-the-domain/weblogic-admin-console.md
@@ -23,7 +23,7 @@ You can access the WebLogic Server Administration Console external to the Kubern
  * To verify that your load balancer, NodePort, or `kubectl port-forward` setup is working as expected, see [Test]({{< relref "#test" >}}).
 
  * Do not use the WebLogic Server Administration Console to start or stop servers, or for scaling clusters. See [Starting and stopping servers]({{< relref "/managing-domains/domain-lifecycle/startup#starting-and-stopping-servers" >}}) and [Scaling]({{< relref "/managing-domains/domain-lifecycle/scaling.md" >}}).
- * If your domain home type is either [Domain in Image]({{< relref "/samples/domains/domain-home-in-image/_index.md" >}}) or [Model in Image]({{< relref "/samples/domains/model-in-image/_index.md" >}}), then do not use the Administration Console to make changes to the WebLogic domain configuration because these changes are ephemeral and will be lost when servers restart. See [Choose a domain home source type]({{< relref "/managing-domains/choosing-a-model/_index.md" >}}).
+ * If your domain home type is either Domain in Image or [Model in Image]({{< relref "/samples/domains/model-in-image/_index.md" >}}), then do not use the Administration Console to make changes to the WebLogic domain configuration because these changes are ephemeral and will be lost when servers restart. See [Choose a domain home source type]({{< relref "/managing-domains/choosing-a-model/_index.md" >}}).
 
 {{% notice warning %}}
 Externally exposing administrative, RMI, or T3 capable WebLogic channels
diff --git a/documentation/site/content/managing-domains/accessing-the-domain/wlst.md b/documentation/site/content/managing-domains/accessing-the-domain/wlst.md
@@ -17,7 +17,7 @@ To give WLST access to a domain running in Kubernetes, you can:
 - [Use a `NodePort`](#use-a-nodeport)
 - [Use port forwarding](#use-port-forwarding)
 
-**NOTE**:  If your domain home type is either [Domain in Image]({{< relref "/samples/domains/domain-home-in-image/_index.md" >}}) or [Model in Image]({{< relref "/samples/domains/model-in-image/_index.md" >}}), then do not use the WLST to make changes to the WebLogic domain configuration because these changes are ephemeral and will be lost when servers restart. See [Choose a domain home source type]({{< relref "/managing-domains/choosing-a-model/_index.md" >}}).
+**NOTE**:  If your domain home type is either Domain in Image or [Model in Image]({{< relref "/samples/domains/model-in-image/_index.md" >}}), then do not use the WLST to make changes to the WebLogic domain configuration because these changes are ephemeral and will be lost when servers restart. See [Choose a domain home source type]({{< relref "/managing-domains/choosing-a-model/_index.md" >}}).
 
 ### Use `kubectl exec`
 
diff --git a/documentation/site/content/managing-domains/choosing-a-model/_index.md b/documentation/site/content/managing-domains/choosing-a-model/_index.md
@@ -30,7 +30,7 @@ When using the operator to start WebLogic Server instances from a domain, you ha
      or [model updates]({{< relref "/managing-domains/model-in-image/runtime-updates.md" >}})
      supplied in a Kubernetes ConfigMap.
 
- - **[Domain in Image]({{< relref "/samples/domains/domain-home-in-image/_index.md" >}})**:
+ - **Domain in Image**:
  **NOTE**: The Domain in Image domain home source type is deprecated in WebLogic Kubernetes Operator version 4.0. Oracle recommends that you choose either Domain on PV or Model in Image, depending on your needs.
    - Set the domain resource `domain.spec.domainHomeSourceType` attribute to `Image`.
    - Supply a WebLogic installation in an image and supply a WebLogic configuration as a domain home layered on this image.
diff --git a/documentation/site/content/managing-domains/domain-resource.md b/documentation/site/content/managing-domains/domain-resource.md
@@ -42,8 +42,7 @@ you may need to update the operator by running `helm upgrade` to be able to moni
 
 Domains and clusters are defined using YAML files. For each WebLogic Server domain you want to run, you should create one YAML file defining a Domain resource and, optionally, one Cluster resource for each WebLogic cluster, and apply it. In the following referenced example, the sample scripts generate a YAML file that you can use as a basis. Copy the file and override the default settings so that it matches all the WebLogic Server domain parameters that define your domain.
 
-See the WebLogic Server samples, [Domain home on a PV]({{< relref "/samples/domains/domain-home-on-pv/_index.md" >}}),
-[Domain home in Image]({{< relref "/samples/domains/domain-home-in-image/_index.md" >}}), and [Model in Image]({{< relref "/samples/domains/model-in-image/_index.md" >}}).
+See the WebLogic Server samples, [Domain home on a PV]({{< relref "/samples/domains/domain-home-on-pv/_index.md" >}}) and [Model in Image]({{< relref "/samples/domains/model-in-image/_index.md" >}}).
 
 After you have written your YAML files, you use them to create your domain artifacts using the `kubectl apply -f` command.
 
diff --git a/documentation/site/content/managing-domains/manage-domains.md b/documentation/site/content/managing-domains/manage-domains.md
@@ -27,8 +27,7 @@ For examples of each, see the [WebLogic Kubernetes Operator samples]({{< relref
 
 If you want to create your own container images, for example, to choose a specific set of patches or to create a domain
 with a specific configuration or applications deployed, then you can create the domain custom resource
-manually to deploy your domain.  This process is documented in [this
-sample]({{< relref "/samples/domains/manually-create-domain/_index.md" >}}).
+manually to deploy your domain.
 
 **NOTE**: After you are familiar with the basics, it is recommended to review
 [important considerations]({{< relref "/managing-domains/manage-domains#important-considerations-for-weblogic-domains-in-kubernetes" >}})
diff --git a/documentation/site/content/managing-domains/managing-fmw-domains.md b/documentation/site/content/managing-domains/managing-fmw-domains.md
@@ -104,7 +104,7 @@ $ ./buildDockerImage.sh -v 12.2.1.4 -s
 
 The image produced will be named `oracle/fmw-infrastructure:12.2.1.4`.
 
-You must also install the [required patch]({{< relref "/introduction/introduction/_index.md#prerequisites" >}})
+You must also install the [required patch]({{< relref "/introduction/prerequisites/introduction.md" >}})
 to use this image with the operator.  We provide a [sample](https://github.com/oracle/docker-images/tree/master/OracleFMWInfrastructure/samples/12213-patch-fmw-for-k8s)
  that demonstrates how to create an image with the necessary patch installed.
 
@@ -401,8 +401,7 @@ password will be the password you provided for regular schema users during RCU c
 ### Creating an FMW Infrastructure domain
 
 Now that you have your images and you have created your RCU schemas, you are ready
-to create your domain.  We provide a [sample]({{< relref "/samples/domains/fmw-domain/_index.md" >}})
-that demonstrates how to create an FMW Infrastructure domain.
+to create your domain.
 
 ### Patching the FMW Infrastructure image
 
diff --git a/documentation/site/content/managing-operators/using-helm.md b/documentation/site/content/managing-operators/using-helm.md
@@ -104,7 +104,7 @@ serviceAccount: "weblogic-operator"
 Specify the Kubernetes platform on which the operator is running. This setting has no default, the only valid value is OpenShift; the setting should be left unset for other platforms.
 
 When set to `OpenShift`, the operator:
-- Sets the domain home file permissions in each WebLogic Server pod to work correctly in OpenShift for [Model in Image]({{< relref "/samples/domains/model-in-image/_index.md" >}}), and [Domain home in Image]({{< relref "/samples/domains/domain-home-in-image/_index.md" >}}) domains. Specifically, it sets file group permissions so that they match file user permissions.
+- Sets the domain home file permissions in each WebLogic Server pod to work correctly in OpenShift for [Model in Image]({{< relref "/samples/domains/model-in-image/_index.md" >}}), and Domain home in Image domains. Specifically, it sets file group permissions so that they match file user permissions.
 - Sets the `weblogic.SecureMode.WarnOnInsecureFileSystem` Java system property to `false` on the command line of each WebLogic Server. This flag suppresses insecure file system warnings reported in the WebLogic Server console when the WebLogic Server is in production mode. These warnings result from setting the file permissions necessary to work with restricted security context constraints on OpenShift.
 
 For more information about the security requirements for running WebLogic in OpenShift, see the [OpenShift]({{<relref "/security/openshift.md">}}) documentation.
