diff --git a/index-upstream-162.html b/index-upstream-162.html index b4e3f070..b83e5b64 100644 --- a/index-upstream-162.html +++ b/index-upstream-162.html @@ -467,6 +467,7 @@

Service Telemetry Framework 1.5

  • Persistent volumes
  • Resource allocation
  • Network considerations for Service Telemetry Framework
    • +
  • Deploying STF on OpenShift-disconnected environments
  • Installing the core components of Service Telemetry Framework @@ -928,9 +929,6 @@

    Preparing your

  • Ensure that enough resources are available to run the Operators and the application containers. For more information, see Resource allocation.

    • -
  • -

    Ensure that you have a fully connected network environment. For more information, see Network considerations for Service Telemetry Framework.

    -
    • @@ -1038,7 +1036,136 @@

    Res

    Network considerations for Service Telemetry Framework

    -

    You can only deploy Service Telemetry Framework (STF) in a fully connected network environment. You cannot deploy STF in OpenShift-disconnected environments or network proxy environments.

    +

    You can deploy Service Telemetry Framework (STF) in fully connected network environments or in OpenShift-disconnected environments. You cannot deploy STF in network proxy environments.

    +
    +
    +
    +

    Deploying STF on OpenShift-disconnected environments

    +
    +

    Since Service Telemetry Framework (STF) version 1.5.4, you can deploy STF in OpenShift-disconnected environments.

    +
    +
    +
    Prerequisites
    +
      +
    • +

      OpenShift Extended Update Support (EUS) version 4.12 or 4.14 deployed in a restricted network.

      +
      • +
    • +

      A mirror registry so that the OpenShift cluster can access the required images. For more information about mirror registries, see Disconnected installation mirroring in the OpenShift Installing guide.

      +
      • +
    • +

      All the STF dependencies are available in the OpenShift cluster mirror registry.

      +
      • +
    +
    +
    +
    Adding STF dependencies to the mirror registry
    +

    You can use the oc-mirror plugin to fetch the STF dependencies and add them to the OpenShift cluster mirror registry. For more information about installing the oc-mirror plugin, see Mirroring images for a disconnected installation using the oc-mirror plugin in the OpenShift Installing guide.

    +
    +
    +
    Procedure
    +
      +
    1. +

      Create an imagesetconfig.yaml file in your local working directory:

      +
      +
      imagesetconfig.yaml
      +
      +
      apiVersion: mirror.openshift.io/v1alpha2
+kind: ImageSetConfiguration
+storageConfig:
+  local:
+    path: ./
+mirror:
+  operators:
+  - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.14
+    packages:
+      - name: service-telemetry-operator
+        channels:
+          - name: stable-1.5
+      - name: openshift-cert-manager-operator
+        channels:
+          - name: stable-v1
+      - name: amq7-interconnect-operator
+        channels:
+          - name: 1.10.x
+      - name: smart-gateway-operator
+        channels:
+          - name: stable-1.5
+      - name: cluster-observability-operator
+        channels:
+          - name: development
      +
      +
      +
      2. +
    2. +

      (Optional) If your mirror registry is not reachable, you can save the manifests and images that you fetched with oc-mirror and physically transfer them to the mirror registry and OpenShift cluster. Otherwise you can run oc-mirror and point to the mirror registry.

      +
      +

      You can use the oc-mirror plugin differently, depending on your environment, such as:

      +
      +
      + +
      +
      3. +
    3. +

      Push the STF operators and their dependencies from the mirror registry and generate the manifest for the OpenShift cluster.

      +
      +
      +
      $ oc-mirror --config imagesetconfig.yaml <mirror_registry_location>
      +
      +
      +
      +
        +
      • +

        Replace <mirror_registry_location> with the filepath to the mirror registry that you want to use.

        +
        • +
      +
      +
      4. +
    4. +

      Locate the generated manifests and apply them to the target OpenShift cluster. For more information, see Configuring your cluster to use the resources generated by oc-mirror in the OpenShift Installing guide.

      +
      + + + + + +
      + + +The manifests that you generate with oc-mirror produce catalogs with the full index name, such as redhat-operator-index instead of redhat-operators for CatalogSource. Ensure that you use the correct index name for the STF subscriptions. For more information, see Deploying Service Telemetry Framework to the OpenShift environment. For more information about customizing Operators with oc mirror, see the Red Hat Knowledgebase solution How to customize the catalog name and tags of Operators mirrored to the mirror registry using the oc mirror plugin. +
      +
      +
      5. +
    +
    +
    +
    Verification
    +
      +
    • +

      Check that the catalog sources are applied. You can return the entries for new catalogs that reference the STF operators and their dependencies:

      +
      +
      +
      $ oc get catalogsources
      +
      +
      +
      • +
    • +

      You have deployed STF in a disconnected OpenShift cluster and therefore cannot access external networks.

      +
      • +

    @@ -1078,7 +1205,7 @@

    Installing the

    You have prepared your OpenShift environment and ensured that there is persistent storage and enough resources to run the STF components on top of the OpenShift environment. For more information about STF performance, see the Red Hat Knowledge Base article Service Telemetry Framework Performance and Scaling.

  • -

    Your environment is fully connected. STF does not work in a OpenShift-disconnected environments or network proxy environments.

    +

    You have deployed STF in a fully connected or OpenShift-disconnected environments. STF is unavailable in network proxy environments.

    • @@ -4946,7 +5073,7 @@

    -Last updated 2024-03-01 15:44:42 UTC +Last updated 2024-03-05 19:34:22 UTC
    diff --git a/index-upstream-171.html b/index-upstream-171.html index 0629b6bf..b8d88306 100644 --- a/index-upstream-171.html +++ b/index-upstream-171.html @@ -467,6 +467,7 @@

    Service Telemetry Framework 1.5

  • Persistent volumes
  • Resource allocation
  • Network considerations for Service Telemetry Framework
    • +
  • Deploying STF on OpenShift-disconnected environments
  • Installing the core components of Service Telemetry Framework @@ -941,9 +942,6 @@

    Preparing your

  • Ensure that enough resources are available to run the Operators and the application containers. For more information, see Resource allocation.

    • -
  • -

    Ensure that you have a fully connected network environment. For more information, see Network considerations for Service Telemetry Framework.

    -
    • @@ -1051,7 +1049,136 @@

    Res

    Network considerations for Service Telemetry Framework

    -

    You can only deploy Service Telemetry Framework (STF) in a fully connected network environment. You cannot deploy STF in OpenShift-disconnected environments or network proxy environments.

    +

    You can deploy Service Telemetry Framework (STF) in fully connected network environments or in OpenShift-disconnected environments. You cannot deploy STF in network proxy environments.

    +
    +
    +
    +

    Deploying STF on OpenShift-disconnected environments

    +
    +

    Since Service Telemetry Framework (STF) version 1.5.4, you can deploy STF in OpenShift-disconnected environments.

    +
    +
    +
    Prerequisites
    +
      +
    • +

      OpenShift Extended Update Support (EUS) version 4.12 or 4.14 deployed in a restricted network.

      +
      • +
    • +

      A mirror registry so that the OpenShift cluster can access the required images. For more information about mirror registries, see Disconnected installation mirroring in the OpenShift Installing guide.

      +
      • +
    • +

      All the STF dependencies are available in the OpenShift cluster mirror registry.

      +
      • +
    +
    +
    +
    Adding STF dependencies to the mirror registry
    +

    You can use the oc-mirror plugin to fetch the STF dependencies and add them to the OpenShift cluster mirror registry. For more information about installing the oc-mirror plugin, see Mirroring images for a disconnected installation using the oc-mirror plugin in the OpenShift Installing guide.

    +
    +
    +
    Procedure
    +
      +
    1. +

      Create an imagesetconfig.yaml file in your local working directory:

      +
      +
      imagesetconfig.yaml
      +
      +
      apiVersion: mirror.openshift.io/v1alpha2
+kind: ImageSetConfiguration
+storageConfig:
+  local:
+    path: ./
+mirror:
+  operators:
+  - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.14
+    packages:
+      - name: service-telemetry-operator
+        channels:
+          - name: stable-1.5
+      - name: openshift-cert-manager-operator
+        channels:
+          - name: stable-v1
+      - name: amq7-interconnect-operator
+        channels:
+          - name: 1.10.x
+      - name: smart-gateway-operator
+        channels:
+          - name: stable-1.5
+      - name: cluster-observability-operator
+        channels:
+          - name: development
      +
      +
      +
      2. +
    2. +

      (Optional) If your mirror registry is not reachable, you can save the manifests and images that you fetched with oc-mirror and physically transfer them to the mirror registry and OpenShift cluster. Otherwise you can run oc-mirror and point to the mirror registry.

      +
      +

      You can use the oc-mirror plugin differently, depending on your environment, such as:

      +
      +
      + +
      +
      3. +
    3. +

      Push the STF operators and their dependencies from the mirror registry and generate the manifest for the OpenShift cluster.

      +
      +
      +
      $ oc-mirror --config imagesetconfig.yaml <mirror_registry_location>
      +
      +
      +
      +
        +
      • +

        Replace <mirror_registry_location> with the filepath to the mirror registry that you want to use.

        +
        • +
      +
      +
      4. +
    4. +

      Locate the generated manifests and apply them to the target OpenShift cluster. For more information, see Configuring your cluster to use the resources generated by oc-mirror in the OpenShift Installing guide.

      +
      + + + + + +
      + + +The manifests that you generate with oc-mirror produce catalogs with the full index name, such as redhat-operator-index instead of redhat-operators for CatalogSource. Ensure that you use the correct index name for the STF subscriptions. For more information, see Deploying Service Telemetry Framework to the OpenShift environment. For more information about customizing Operators with oc mirror, see the Red Hat Knowledgebase solution How to customize the catalog name and tags of Operators mirrored to the mirror registry using the oc mirror plugin. +
      +
      +
      5. +
    +
    +
    +
    Verification
    +
      +
    • +

      Check that the catalog sources are applied. You can return the entries for new catalogs that reference the STF operators and their dependencies:

      +
      +
      +
      $ oc get catalogsources
      +
      +
      +
      • +
    • +

      You have deployed STF in a disconnected OpenShift cluster and therefore cannot access external networks.

      +
      • +

    @@ -1091,7 +1218,7 @@

    Installing the

    You have prepared your OpenShift environment and ensured that there is persistent storage and enough resources to run the STF components on top of the OpenShift environment. For more information about STF performance, see the Red Hat Knowledge Base article Service Telemetry Framework Performance and Scaling.

  • -

    Your environment is fully connected. STF does not work in a OpenShift-disconnected environments or network proxy environments.

    +

    You have deployed STF in a fully connected or OpenShift-disconnected environments. STF is unavailable in network proxy environments.

    • @@ -5280,7 +5407,7 @@

    -Last updated 2024-03-01 15:44:42 UTC +Last updated 2024-03-05 19:34:22 UTC
    diff --git a/index.html b/index.html index 0629b6bf..b8d88306 100644 --- a/index.html +++ b/index.html @@ -467,6 +467,7 @@

    Service Telemetry Framework 1.5

  • Persistent volumes
  • Resource allocation
  • Network considerations for Service Telemetry Framework
    • +
  • Deploying STF on OpenShift-disconnected environments
  • Installing the core components of Service Telemetry Framework @@ -941,9 +942,6 @@

    Preparing your

  • Ensure that enough resources are available to run the Operators and the application containers. For more information, see Resource allocation.

    • -
  • -

    Ensure that you have a fully connected network environment. For more information, see Network considerations for Service Telemetry Framework.

    -
    • @@ -1051,7 +1049,136 @@

    Res

    Network considerations for Service Telemetry Framework

    -

    You can only deploy Service Telemetry Framework (STF) in a fully connected network environment. You cannot deploy STF in OpenShift-disconnected environments or network proxy environments.

    +

    You can deploy Service Telemetry Framework (STF) in fully connected network environments or in OpenShift-disconnected environments. You cannot deploy STF in network proxy environments.

    +
    +
    +
    +

    Deploying STF on OpenShift-disconnected environments

    +
    +

    Since Service Telemetry Framework (STF) version 1.5.4, you can deploy STF in OpenShift-disconnected environments.

    +
    +
    +
    Prerequisites
    +
      +
    • +

      OpenShift Extended Update Support (EUS) version 4.12 or 4.14 deployed in a restricted network.

      +
      • +
    • +

      A mirror registry so that the OpenShift cluster can access the required images. For more information about mirror registries, see Disconnected installation mirroring in the OpenShift Installing guide.

      +
      • +
    • +

      All the STF dependencies are available in the OpenShift cluster mirror registry.

      +
      • +
    +
    +
    +
    Adding STF dependencies to the mirror registry
    +

    You can use the oc-mirror plugin to fetch the STF dependencies and add them to the OpenShift cluster mirror registry. For more information about installing the oc-mirror plugin, see Mirroring images for a disconnected installation using the oc-mirror plugin in the OpenShift Installing guide.

    +
    +
    +
    Procedure
    +
      +
    1. +

      Create an imagesetconfig.yaml file in your local working directory:

      +
      +
      imagesetconfig.yaml
      +
      +
      apiVersion: mirror.openshift.io/v1alpha2
+kind: ImageSetConfiguration
+storageConfig:
+  local:
+    path: ./
+mirror:
+  operators:
+  - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.14
+    packages:
+      - name: service-telemetry-operator
+        channels:
+          - name: stable-1.5
+      - name: openshift-cert-manager-operator
+        channels:
+          - name: stable-v1
+      - name: amq7-interconnect-operator
+        channels:
+          - name: 1.10.x
+      - name: smart-gateway-operator
+        channels:
+          - name: stable-1.5
+      - name: cluster-observability-operator
+        channels:
+          - name: development
      +
      +
      +
      2. +
    2. +

      (Optional) If your mirror registry is not reachable, you can save the manifests and images that you fetched with oc-mirror and physically transfer them to the mirror registry and OpenShift cluster. Otherwise you can run oc-mirror and point to the mirror registry.

      +
      +

      You can use the oc-mirror plugin differently, depending on your environment, such as:

      +
      +
      + +
      +
      3. +
    3. +

      Push the STF operators and their dependencies from the mirror registry and generate the manifest for the OpenShift cluster.

      +
      +
      +
      $ oc-mirror --config imagesetconfig.yaml <mirror_registry_location>
      +
      +
      +
      +
        +
      • +

        Replace <mirror_registry_location> with the filepath to the mirror registry that you want to use.

        +
        • +
      +
      +
      4. +
    4. +

      Locate the generated manifests and apply them to the target OpenShift cluster. For more information, see Configuring your cluster to use the resources generated by oc-mirror in the OpenShift Installing guide.

      +
      + + + + + +
      + + +The manifests that you generate with oc-mirror produce catalogs with the full index name, such as redhat-operator-index instead of redhat-operators for CatalogSource. Ensure that you use the correct index name for the STF subscriptions. For more information, see Deploying Service Telemetry Framework to the OpenShift environment. For more information about customizing Operators with oc mirror, see the Red Hat Knowledgebase solution How to customize the catalog name and tags of Operators mirrored to the mirror registry using the oc mirror plugin. +
      +
      +
      5. +
    +
    +
    +
    Verification
    +
      +
    • +

      Check that the catalog sources are applied. You can return the entries for new catalogs that reference the STF operators and their dependencies:

      +
      +
      +
      $ oc get catalogsources
      +
      +
      +
      • +
    • +

      You have deployed STF in a disconnected OpenShift cluster and therefore cannot access external networks.

      +
      • +

    @@ -1091,7 +1218,7 @@

    Installing the

    You have prepared your OpenShift environment and ensured that there is persistent storage and enough resources to run the STF components on top of the OpenShift environment. For more information about STF performance, see the Red Hat Knowledge Base article Service Telemetry Framework Performance and Scaling.

  • -

    Your environment is fully connected. STF does not work in a OpenShift-disconnected environments or network proxy environments.

    +

    You have deployed STF in a fully connected or OpenShift-disconnected environments. STF is unavailable in network proxy environments.

    • @@ -5280,7 +5407,7 @@

    -Last updated 2024-03-01 15:44:42 UTC +Last updated 2024-03-05 19:34:22 UTC