From f762369591a26507e55298b803b2e298f3092e02 Mon Sep 17 00:00:00 2001 From: Shubha Narayanan Date: Tue, 7 Oct 2025 11:19:38 +0530 Subject: [PATCH] removed unused modules --- modules/kubernetes-about.adoc | 16 --------- modules/oc-mirror-differential-updates.adoc | 36 --------------------- 2 files changed, 52 deletions(-) delete mode 100644 modules/kubernetes-about.adoc delete mode 100644 modules/oc-mirror-differential-updates.adoc diff --git a/modules/kubernetes-about.adoc b/modules/kubernetes-about.adoc deleted file mode 100644 index 1ed84826bda6..000000000000 --- a/modules/kubernetes-about.adoc +++ /dev/null @@ -1,16 +0,0 @@ -// Module included in the following assemblies: -// -// * osd_architecture/osd-architecture.adoc - -:_mod-docs-content-type: CONCEPT -[id="kubernetes-about_{context}"] -= About Kubernetes - -Kubernetes is an open source container orchestration engine for automating deployment, scaling, and management of containerized applications. The general concept of Kubernetes is fairly simple: - -* Start with one or more worker nodes to run the container workloads. -* Manage the deployment of those workloads from one or more control nodes. -* Wrap containers in a deployment unit called a pod. Using pods provides extra metadata with the container and offers the ability to group several containers in a single deployment entity. -* Create special kinds of assets. For example, services are represented by a set of pods and a policy that defines how they are accessed. This policy allows containers to connect to the services that they need even if they do not have the specific IP addresses for the services. Replication controllers are another special asset that indicates how many pod Replicas are required to run at a time. You can use this capability to automatically scale your application to adapt to its current demand. - -To learn more about Kubernetes, see the link:https://kubernetes.io/docs/home/?path=users&persona=app-developer&level=foundational[Kubernetes documentation]. diff --git a/modules/oc-mirror-differential-updates.adoc b/modules/oc-mirror-differential-updates.adoc deleted file mode 100644 index 7eadc85c3587..000000000000 --- a/modules/oc-mirror-differential-updates.adoc +++ /dev/null @@ -1,36 +0,0 @@ -// Module included in the following assemblies: -// -// * installing/disconnected_install/installing-mirroring-disconnected.adoc -// * updating/updating_a_cluster/updating_disconnected_cluster/mirroring-image-repository.adoc - -:_mod-docs-content-type: PROCEDURE -[id="oc-mirror-differential-updates_{context}"] -= Updating your mirror registry content - -After you publish the initial image set to the mirror registry, you can use the oc-mirror plugin to keep your disconnected clusters updated. - -Depending on your image set configuration, oc-mirror automatically detects newer releases of {product-title} and your selected Operators that have been released after you completed the initial mirror. It is recommended to run oc-mirror at regular intervals, for example in a nightly cron job, to receive product and security updates on a timely basis. - -.Prerequisites - -* You have used the oc-mirror plugin to mirror the initial image set to your mirror registry. -* You have access to the storage backend that was used for the initial execution of the oc-mirror plugin. -+ -[NOTE] -==== -You must use the same storage backend as the initial execution of oc-mirror for the same mirror registry. Do not delete or modify the metadata image that is generated by the oc-mirror plugin. -==== - -.Procedure - -. If necessary, update your image set configuration file to pick up new {product-title} and Operator versions. See _Image set configuration examples_ for example mirroring use cases. - -. Follow the same steps that you used to mirror your initial image set to the mirror registry. For instructions, see _Mirroring an image set in a partially disconnected environment_ or _Mirroring an image set in a fully disconnected environment_. -+ -[IMPORTANT] -==== -* You must provide the same storage backend so that only a differential image set is created and mirrored. -* If you specified a top-level namespace for the mirror registry during the initial image set creation, then you must use this same namespace every time you run the oc-mirror plugin for the same mirror registry. -==== - -. Configure your cluster to use the resources generated by oc-mirror.