mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
OCPBUGS-15887: xrefs containing 'html' instead of 'adoc'
This commit is contained in:
Alexandra Molnar
committed by
openshift-cherrypick-robot
openshift-cherrypick-robot
parent
f56a51237d
commit
ac740e23ab
@@ -14,9 +14,9 @@ include::modules/service-accounts-default.adoc[leveloffset=+1]
|
||||
|
||||
.Additional resources
|
||||
|
||||
* For information about requesting bound service account tokens, see xref:../authentication/bound-service-account-tokens.html#bound-sa-tokens-configuring_bound-service-account-tokens[Configuring bound service account tokens using volume projection]
|
||||
* For information about requesting bound service account tokens, see xref:../authentication/bound-service-account-tokens.adoc#bound-sa-tokens-configuring_bound-service-account-tokens[Configuring bound service account tokens using volume projection]
|
||||
|
||||
* For information about creating a service account token secret, see xref:../nodes/pods/nodes-pods-secrets.html#nodes-pods-secrets-creating-sa_nodes-pods-secrets[Creating a service account token secret].
|
||||
* For information about creating a service account token secret, see xref:../nodes/pods/nodes-pods-secrets.adoc#nodes-pods-secrets-creating-sa_nodes-pods-secrets[Creating a service account token secret].
|
||||
|
||||
include::modules/service-accounts-creating.adoc[leveloffset=+1]
|
||||
|
||||
|
||||
@@ -19,7 +19,7 @@ You can enable and disable the setting for monitoring Argo CD custom resource wo
|
||||
* {gitops-title} is installed in your cluster.
|
||||
* The monitoring stack is configured in your cluster in the `openshift-monitoring` project. In addition, the Argo CD instance is in a namespace that you can monitor through Prometheus.
|
||||
* The `kube-state-metrics` service is running in your cluster.
|
||||
* Optional: If you are enabling monitoring for an Argo CD instance already present in a user-defined project, ensure that the monitoring is xref:../../monitoring/enabling-monitoring-for-user-defined-projects.html#enabling-monitoring-for-user-defined-projects_enabling-monitoring-for-user-defined-projects[enabled for user-defined projects] in your cluster.
|
||||
* Optional: If you are enabling monitoring for an Argo CD instance already present in a user-defined project, ensure that the monitoring is xref:../../monitoring/enabling-monitoring-for-user-defined-projects.adoc#enabling-monitoring-for-user-defined-projects_enabling-monitoring-for-user-defined-projects[enabled for user-defined projects] in your cluster.
|
||||
+
|
||||
[NOTE]
|
||||
====
|
||||
|
||||
@@ -50,7 +50,7 @@ include::modules/op-performance-tuning-using-tektonconfig-cr.adoc[leveloffset=+1
|
||||
|
||||
* For more information on using pipelines in a restricted environment, see:
|
||||
|
||||
** xref:../../cicd/pipelines/creating-applications-with-cicd-pipelines.html#op-mirroring-images-to-run-pipelines-in-restricted-environment_creating-applications-with-cicd-pipelines[Mirroring images to run pipelines in a restricted environment]
|
||||
** xref:../../cicd/pipelines/creating-applications-with-cicd-pipelines.adoc#op-mirroring-images-to-run-pipelines-in-restricted-environment_creating-applications-with-cicd-pipelines[Mirroring images to run pipelines in a restricted environment]
|
||||
|
||||
** xref:../../openshift_images/configuring-samples-operator.adoc#samples-operator-restricted-network-install[Configuring Samples Operator for a restricted cluster]
|
||||
|
||||
|
||||
@@ -12,8 +12,8 @@ To define the final resource limits that are set on the resulting pods, {pipelin
|
||||
|
||||
To restrict resource consumption in your project, you can:
|
||||
|
||||
* xref:../../applications/quotas/quotas-setting-per-project.html[Set and manage resource quotas] to limit the aggregate resource consumption.
|
||||
* Use xref:../../nodes/clusters/nodes-cluster-limit-ranges.html[limit ranges to restrict resource consumption] for specific objects, such as pods, images, image streams, and persistent volume claims.
|
||||
* xref:../../applications/quotas/quotas-setting-per-project.adoc[Set and manage resource quotas] to limit the aggregate resource consumption.
|
||||
* Use xref:../../nodes/clusters/nodes-cluster-limit-ranges.adoc[limit ranges to restrict resource consumption] for specific objects, such as pods, images, image streams, and persistent volume claims.
|
||||
|
||||
include::modules/op-understanding-pipelines-resource-consumption.adoc[leveloffset=+1]
|
||||
|
||||
|
||||
@@ -46,7 +46,7 @@ The streaming deployment strategy is currently unsupported on {ibmzProductName}.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
There are two ways to install and use {DTProductName}, as part of a service mesh or as a stand alone component. If you have installed {DTShortName} as part of {SMProductName}, you can perform basic configuration as part of the xref:../../service_mesh/v2x/installing-ossm.adoc#installing-ossm[ServiceMeshControlPlane] but for completely control you should configure a Jaeger CR and then xref:../../service_mesh/v2x/ossm-observability.html#ossm-config-external-jaeger_observability[reference your distributed tracing configuration file in the ServiceMeshControlPlane].
|
||||
There are two ways to install and use {DTProductName}, as part of a service mesh or as a stand alone component. If you have installed {DTShortName} as part of {SMProductName}, you can perform basic configuration as part of the xref:../../service_mesh/v2x/installing-ossm.adoc#installing-ossm[ServiceMeshControlPlane] but for completely control you should configure a Jaeger CR and then xref:../../service_mesh/v2x/ossm-observability.adoc#ossm-config-external-jaeger_observability[reference your distributed tracing configuration file in the ServiceMeshControlPlane].
|
||||
|
||||
====
|
||||
|
||||
|
||||
@@ -131,7 +131,7 @@ include::modules/oc-mirror-oci-format.adoc[leveloffset=+1]
|
||||
.Additional resources
|
||||
|
||||
// TODO: This title might need to update per sebastian's PR
|
||||
* xref:../../installing/disconnected_install/installing-mirroring-disconnected.html#oc-mirror-updating-cluster-manifests_installing-mirroring-disconnected[Configuring your cluster to use the resources generated by oc-mirror]
|
||||
* xref:../../installing/disconnected_install/installing-mirroring-disconnected.adoc#oc-mirror-updating-cluster-manifests_installing-mirroring-disconnected[Configuring your cluster to use the resources generated by oc-mirror]
|
||||
|
||||
// Image set configuration parameters
|
||||
include::modules/oc-mirror-imageset-config-params.adoc[leveloffset=+1]
|
||||
|
||||
@@ -65,7 +65,7 @@ include::modules/cluster-limitations-local-zone.adoc[leveloffset=+1]
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
|
||||
* xref:../../storage/understanding-persistent-storage.html#pvc-storage-class_understanding-persistent-storage[Storage classes]
|
||||
* xref:../../storage/understanding-persistent-storage.adoc#pvc-storage-class_understanding-persistent-storage[Storage classes]
|
||||
|
||||
include::modules/cluster-entitlements.adoc[leveloffset=+1]
|
||||
|
||||
|
||||
@@ -163,7 +163,7 @@ include::modules/installation-aws-user-infra-bootstrap.adoc[leveloffset=+1]
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
|
||||
* See xref:../../support/troubleshooting/troubleshooting-installations.html#monitoring-installation-progress_troubleshooting-installations[Monitoring installation progress] for details about monitoring the installation, bootstrap, and control plane logs as an {product-title} installation progresses.
|
||||
* See xref:../../support/troubleshooting/troubleshooting-installations.adoc#monitoring-installation-progress_troubleshooting-installations[Monitoring installation progress] for details about monitoring the installation, bootstrap, and control plane logs as an {product-title} installation progresses.
|
||||
|
||||
* See xref:../../support/troubleshooting/troubleshooting-installations.adoc#gathering-bootstrap-diagnostic-data_troubleshooting-installations[Gathering bootstrap node diagnostic data] for information about troubleshooting issues related to the bootstrap process.
|
||||
|
||||
|
||||
@@ -146,7 +146,7 @@ include::modules/installation-aws-user-infra-bootstrap.adoc[leveloffset=+1]
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
|
||||
* See xref:../../support/troubleshooting/troubleshooting-installations.html#monitoring-installation-progress_troubleshooting-installations[Monitoring installation progress] for details about monitoring the installation, bootstrap, and control plane logs as an {product-title} installation progresses.
|
||||
* See xref:../../support/troubleshooting/troubleshooting-installations.adoc#monitoring-installation-progress_troubleshooting-installations[Monitoring installation progress] for details about monitoring the installation, bootstrap, and control plane logs as an {product-title} installation progresses.
|
||||
|
||||
* See xref:../../support/troubleshooting/troubleshooting-installations.adoc#gathering-bootstrap-diagnostic-data_troubleshooting-installations[Gathering bootstrap node diagnostic data] for information about troubleshooting issues related to the bootstrap process.
|
||||
|
||||
|
||||
@@ -114,7 +114,7 @@ include::modules/installation-bare-metal-config-yaml.adoc[leveloffset=+2]
|
||||
|
||||
* See xref:../../installing/installing_bare_metal/installing-bare-metal.adoc#installation-load-balancing-user-infra_installing-bare-metal[Load balancing requirements for user-provisioned infrastructure] for more information on the API and application ingress load balancing requirements.
|
||||
* See xref:../../post_installation_configuration/enabling-cluster-capabilities.adoc[Enabling cluster capabilities] for more information on enabling cluster capabilities that were disabled prior to installation.
|
||||
* See xref:../../installing/cluster-capabilities.html#explanation_of_capabilities_cluster-capabilities[Optional cluster capabilities in {product-title} {product-version}] for more information about the features provided by each capability.
|
||||
* See xref:../../installing/cluster-capabilities.adoc#explanation_of_capabilities_cluster-capabilities[Optional cluster capabilities in {product-title} {product-version}] for more information about the features provided by each capability.
|
||||
|
||||
|
||||
include::modules/installation-configure-proxy.adoc[leveloffset=+2]
|
||||
|
||||
@@ -23,4 +23,4 @@ include::modules/assisted-installer-assisted-installer-prerequisites.adoc[levelo
|
||||
|
||||
* xref:../installing_bare_metal_ipi/ipi-install-prerequisites.adoc#ipi-install-firmware-requirements-for-installing-with-virtual-media_ipi-install-prerequisites[Firmware requirements for installing with virtual media]
|
||||
|
||||
* xref:../installing_bare_metal_ipi/ipi-install-prerequisites.html#network-requirements-increase-mtu_ipi-install-prerequisites[Increase the network MTU]
|
||||
* xref:../installing_bare_metal_ipi/ipi-install-prerequisites.adoc#network-requirements-increase-mtu_ipi-install-prerequisites[Increase the network MTU]
|
||||
|
||||
@@ -32,10 +32,10 @@ After you perform pre-installation tasks, install your cluster by following the
|
||||
== Next steps
|
||||
|
||||
* For either type of deployment:
|
||||
** xref:../../scalability_and_performance/what-huge-pages-do-and-how-they-are-consumed-by-apps.html#what-huge-pages-do_huge-pages[Configure the Node Tuning Operator with huge pages support].
|
||||
** xref:../../scalability_and_performance/what-huge-pages-do-and-how-they-are-consumed-by-apps.adoc#what-huge-pages-do_huge-pages[Configure the Node Tuning Operator with huge pages support].
|
||||
* To complete SR-IOV configuration after you deploy your cluster:
|
||||
** xref:../../networking/hardware_networks/installing-sriov-operator.html#installing-sr-iov-operator_installing-sriov-operator[Install the SR-IOV Operator].
|
||||
** xref:../../networking/hardware_networks/configuring-sriov-device.html#nw-sriov-networknodepolicy-object_configuring-sriov-device[Configure your SR-IOV network device].
|
||||
** xref:../../networking/hardware_networks/installing-sriov-operator.adoc#installing-sr-iov-operator_installing-sriov-operator[Install the SR-IOV Operator].
|
||||
** xref:../../networking/hardware_networks/configuring-sriov-device.adoc#nw-sriov-networknodepolicy-object_configuring-sriov-device[Configure your SR-IOV network device].
|
||||
** xref:../../machine_management/creating_machinesets/creating-machineset-osp.adoc#machineset-yaml-osp-sr-iov_creating-machineset-osp[Create SR-IOV compute machines].
|
||||
* Consult the following references after you deploy your cluster to improve its performance:
|
||||
** xref:../../networking/hardware_networks/using-dpdk-and-rdma.adoc#nw-openstack-ovs-dpdk-testpmd-pod_using-dpdk-and-rdma[A test pod template for clusters that use OVS-DPDK on OpenStack].
|
||||
|
||||
@@ -75,9 +75,9 @@ include::modules/cluster-telemetry.adoc[leveloffset=+1]
|
||||
== Next steps
|
||||
|
||||
* To complete SR-IOV configuration for your cluster:
|
||||
** xref:../../post_installation_configuration/network-configuration.html#networking-osp-preparing-for-sr-iov_post-install-network-configuration[Prepare the cluster for SR-IOV].
|
||||
** xref:../../scalability_and_performance/what-huge-pages-do-and-how-they-are-consumed-by-apps.html#what-huge-pages-do_huge-pages[Install the performance operator with huge pages support].
|
||||
** xref:../../networking/hardware_networks/installing-sriov-operator.html#installing-sr-iov-operator_installing-sriov-operator[Install the SR-IOV Operator].
|
||||
** xref:../../post_installation_configuration/network-configuration.adoc#networking-osp-preparing-for-sr-iov_post-install-network-configuration[Prepare the cluster for SR-IOV].
|
||||
** xref:../../scalability_and_performance/what-huge-pages-do-and-how-they-are-consumed-by-apps.adoc#what-huge-pages-do_huge-pages[Install the performance operator with huge pages support].
|
||||
** xref:../../networking/hardware_networks/installing-sriov-operator.adoc#installing-sr-iov-operator_installing-sriov-operator[Install the SR-IOV Operator].
|
||||
* xref:../../post_installation_configuration/cluster-tasks.adoc#available_cluster_customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
xref:../../support/remote_health_monitoring/opting-out-of-remote-health-reporting.adoc#opting-out-remote-health-reporting_opting-out-remote-health-reporting[opt out of remote health reporting].
|
||||
|
||||
@@ -66,7 +66,7 @@ include::modules/networking-osp-enabling-vfio-noiommu.adoc[leveloffset=+2]
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
After you apply the machine config to the machine pool, you can xref:../../post_installation_configuration/machine-configuration-tasks.html#checking-mco-status_post-install-machine-configuration-tasks[watch the machine config pool status] to see when the machines are available.
|
||||
After you apply the machine config to the machine pool, you can xref:../../post_installation_configuration/machine-configuration-tasks.adoc#checking-mco-status_post-install-machine-configuration-tasks[watch the machine config pool status] to see when the machines are available.
|
||||
====
|
||||
|
||||
// TODO: If bullet one of Next steps is truly required for this flow, these topics (in full or in part) could be added here rather than linked to.
|
||||
@@ -85,15 +85,15 @@ include::modules/cluster-telemetry.adoc[leveloffset=+1]
|
||||
[role="_additional-resources"]
|
||||
[id="additional-resources_installing-openstack-user-sr-iov"]
|
||||
== Additional resources
|
||||
* xref:../../scalability_and_performance/cnf-low-latency-tuning.html#cnf-understanding-low-latency_cnf-master[Low latency tuning of OpenShift Container Platform nodes]
|
||||
* xref:../../scalability_and_performance/cnf-low-latency-tuning.adoc#cnf-understanding-low-latency_cnf-master[Low latency tuning of OpenShift Container Platform nodes]
|
||||
|
||||
[id="next-steps_installing-user-sr-iov"]
|
||||
== Next steps
|
||||
|
||||
* To complete SR-IOV configuration for your cluster:
|
||||
** xref:../../scalability_and_performance/what-huge-pages-do-and-how-they-are-consumed-by-apps.html#what-huge-pages-do_huge-pages[Configure huge pages support].
|
||||
** xref:../../networking/hardware_networks/installing-sriov-operator.html#installing-sr-iov-operator_installing-sriov-operator[Install the SR-IOV Operator].
|
||||
** xref:../../networking/hardware_networks/configuring-sriov-device.html#nw-sriov-networknodepolicy-object_configuring-sriov-device[Configure your SR-IOV network device].
|
||||
** xref:../../scalability_and_performance/what-huge-pages-do-and-how-they-are-consumed-by-apps.adoc#what-huge-pages-do_huge-pages[Configure huge pages support].
|
||||
** xref:../../networking/hardware_networks/installing-sriov-operator.adoc#installing-sr-iov-operator_installing-sriov-operator[Install the SR-IOV Operator].
|
||||
** xref:../../networking/hardware_networks/configuring-sriov-device.adoc#nw-sriov-networknodepolicy-object_configuring-sriov-device[Configure your SR-IOV network device].
|
||||
* xref:../../post_installation_configuration/cluster-tasks.adoc#available_cluster_customizations[Customize your cluster].
|
||||
* If necessary, you can
|
||||
xref:../../support/remote_health_monitoring/opting-out-of-remote-health-reporting.adoc#opting-out-remote-health-reporting_opting-out-remote-health-reporting[opt out of remote health reporting].
|
||||
|
||||
@@ -46,7 +46,7 @@ include::modules/install-sno-generating-the-install-iso-manually.adoc[leveloffse
|
||||
.Additional resources
|
||||
|
||||
* See xref:../../post_installation_configuration/enabling-cluster-capabilities.adoc[Enabling cluster capabilities] for more information about enabling cluster capabilities that were disabled prior to installation.
|
||||
* See xref:../../installing/cluster-capabilities.html#explanation_of_capabilities_cluster-capabilities[Optional cluster capabilities in OpenShift Container Platform {product-title} {product-version}] for more information about the features provided by each capability.
|
||||
* See xref:../../installing/cluster-capabilities.adoc#explanation_of_capabilities_cluster-capabilities[Optional cluster capabilities in {product-title} {product-version}] for more information about the features provided by each capability.
|
||||
|
||||
include::modules/install-sno-monitoring-the-installation-manually.adoc[leveloffset=+2]
|
||||
|
||||
|
||||
@@ -66,7 +66,7 @@ include::modules/installation-vsphere-regions-zones.adoc[leveloffset=+1]
|
||||
|
||||
* xref:../../storage/container_storage_interface/persistent-storage-csi-migration.adoc#persistent-storage-csi-migration-sc-vsphere_persistent-storage-csi-migration[vSphere automatic migration]
|
||||
|
||||
* xref:../../storage/container_storage_interface/persistent-storage-csi-vsphere.html#persistent-storage-csi-vsphere-top-aware_persistent-storage-csi-vsphere[VMware vSphere CSI Driver Operator]
|
||||
* xref:../../storage/container_storage_interface/persistent-storage-csi-vsphere.adoc#persistent-storage-csi-vsphere-top-aware_persistent-storage-csi-vsphere[VMware vSphere CSI Driver Operator]
|
||||
|
||||
include::modules/installation-initializing.adoc[leveloffset=+1]
|
||||
|
||||
|
||||
@@ -106,7 +106,7 @@ include::modules/installation-vsphere-regions-zones.adoc[leveloffset=+1]
|
||||
|
||||
* xref:../../storage/container_storage_interface/persistent-storage-csi-migration.adoc#persistent-storage-csi-migration-sc-vsphere_persistent-storage-csi-migration[vSphere automatic migration]
|
||||
|
||||
* xref:../../storage/container_storage_interface/persistent-storage-csi-vsphere.html#persistent-storage-csi-vsphere-top-aware_persistent-storage-csi-vsphere[VMware vSphere CSI Driver Operator]
|
||||
* xref:../../storage/container_storage_interface/persistent-storage-csi-vsphere.adoc#persistent-storage-csi-vsphere-top-aware_persistent-storage-csi-vsphere[VMware vSphere CSI Driver Operator]
|
||||
|
||||
include::modules/installation-initializing-manual.adoc[leveloffset=+1]
|
||||
|
||||
|
||||
@@ -59,7 +59,7 @@ include::modules/installation-vsphere-regions-zones.adoc[leveloffset=+1]
|
||||
|
||||
* xref:../../storage/container_storage_interface/persistent-storage-csi-migration.adoc#persistent-storage-csi-migration-sc-vsphere_persistent-storage-csi-migration[vSphere automatic migration]
|
||||
|
||||
* xref:../../storage/container_storage_interface/persistent-storage-csi-vsphere.html#persistent-storage-csi-vsphere-top-aware_persistent-storage-csi-vsphere[VMware vSphere CSI Driver Operator]
|
||||
* xref:../../storage/container_storage_interface/persistent-storage-csi-vsphere.adoc#persistent-storage-csi-vsphere-top-aware_persistent-storage-csi-vsphere[VMware vSphere CSI Driver Operator]
|
||||
|
||||
include::modules/installation-initializing.adoc[leveloffset=+1]
|
||||
|
||||
|
||||
@@ -61,7 +61,7 @@ include::modules/installation-vsphere-regions-zones.adoc[leveloffset=+1]
|
||||
|
||||
* xref:../../storage/container_storage_interface/persistent-storage-csi-migration.adoc#persistent-storage-csi-migration-sc-vsphere_persistent-storage-csi-migration[vSphere automatic migration]
|
||||
|
||||
* xref:../../storage/container_storage_interface/persistent-storage-csi-vsphere.html#persistent-storage-csi-vsphere-top-aware_persistent-storage-csi-vsphere[VMware vSphere CSI Driver Operator]
|
||||
* xref:../../storage/container_storage_interface/persistent-storage-csi-vsphere.adoc#persistent-storage-csi-vsphere-top-aware_persistent-storage-csi-vsphere[VMware vSphere CSI Driver Operator]
|
||||
|
||||
include::modules/installation-initializing.adoc[leveloffset=+1]
|
||||
|
||||
|
||||
@@ -94,7 +94,7 @@ include::modules/installation-vsphere-regions-zones.adoc[leveloffset=+1]
|
||||
|
||||
* xref:../../storage/container_storage_interface/persistent-storage-csi-migration.adoc#persistent-storage-csi-migration-sc-vsphere_persistent-storage-csi-migration[vSphere automatic migration]
|
||||
|
||||
* xref:../../storage/container_storage_interface/persistent-storage-csi-vsphere.html#persistent-storage-csi-vsphere-top-aware_persistent-storage-csi-vsphere[VMware vSphere CSI Driver Operator]
|
||||
* xref:../../storage/container_storage_interface/persistent-storage-csi-vsphere.adoc#persistent-storage-csi-vsphere-top-aware_persistent-storage-csi-vsphere[VMware vSphere CSI Driver Operator]
|
||||
|
||||
include::modules/installation-obtaining-installer.adoc[leveloffset=+1]
|
||||
|
||||
|
||||
@@ -94,7 +94,7 @@ include::modules/installation-vsphere-regions-zones.adoc[leveloffset=+1]
|
||||
|
||||
* xref:../../storage/container_storage_interface/persistent-storage-csi-migration.adoc#persistent-storage-csi-migration-sc-vsphere_persistent-storage-csi-migration[vSphere automatic migration]
|
||||
|
||||
* xref:../../storage/container_storage_interface/persistent-storage-csi-vsphere.html#persistent-storage-csi-vsphere-top-aware_persistent-storage-csi-vsphere[VMware vSphere CSI Driver Operator]
|
||||
* xref:../../storage/container_storage_interface/persistent-storage-csi-vsphere.adoc#persistent-storage-csi-vsphere-top-aware_persistent-storage-csi-vsphere[VMware vSphere CSI Driver Operator]
|
||||
|
||||
include::modules/installation-obtaining-installer.adoc[leveloffset=+1]
|
||||
|
||||
|
||||
@@ -26,7 +26,7 @@ You can install {product-title} with the link:https://access.redhat.com/document
|
||||
|
||||
You can also install {product-title} on vSphere by using installer-provisioned or user-provisioned infrastructure. Installer-provisioned infrastructure is ideal for installing in environments with air-gapped/restricted networks, where the installation program provisions the underlying infrastructure for the cluster. You can also install {product-title} on infrastructure that you provide. If you do not use infrastructure that the installation program provisions, you must manage and maintain the cluster resources yourself.
|
||||
|
||||
See the xref:../../architecture/architecture-installation.html#installation-process_architecture-installation[Installation process] for more information about installer-provisioned and user-provisioned installation processes.
|
||||
See the xref:../../architecture/architecture-installation.adoc#installation-process_architecture-installation[Installation process] for more information about installer-provisioned and user-provisioned installation processes.
|
||||
|
||||
[IMPORTANT]
|
||||
====
|
||||
|
||||
@@ -27,7 +27,7 @@ The *Logging/Elasticsearch Nodes* dashboard contains charts that show details ab
|
||||
|
||||
include::modules/cluster-logging-dashboards-access.adoc[leveloffset=+1]
|
||||
|
||||
For information on the dashboard charts, see xref:../logging/cluster-logging-dashboards.html#cluster-logging-dashboards-logging_cluster-logging-dashboards[About the OpenShift Logging dashboard] and xref:../logging/cluster-logging-dashboards.html#cluster-logging-dashboards-es_cluster-logging-dashboards[About the Logging/Elastisearch Nodes dashboard].
|
||||
For information on the dashboard charts, see xref:../logging/cluster-logging-dashboards.adoc#cluster-logging-dashboards-logging_cluster-logging-dashboards[About the OpenShift Logging dashboard] and xref:../logging/cluster-logging-dashboards.adoc#cluster-logging-dashboards-es_cluster-logging-dashboards[About the Logging/Elastisearch Nodes dashboard].
|
||||
|
||||
include::modules/cluster-logging-dashboards-logging.adoc[leveloffset=+1]
|
||||
include::modules/cluster-logging-dashboards-es.adoc[leveloffset=+1]
|
||||
|
||||
@@ -966,11 +966,11 @@ This release includes link:https://access.redhat.com/errata/RHBA-2021:3393[RHBA-
|
||||
[id="openshift-logging-5-2-0-new-features-and-enhancements_{context}"]
|
||||
=== New features and enhancements
|
||||
|
||||
* With this update, you can forward log data to Amazon CloudWatch, which provides application and infrastructure monitoring. For more information, see xref:../logging/cluster-logging-external.html#cluster-logging-collector-log-forward-cloudwatch_cluster-logging-external[Forwarding logs to Amazon CloudWatch]. (link:https://issues.redhat.com/browse/LOG-1173[LOG-1173])
|
||||
* With this update, you can forward log data to Amazon CloudWatch, which provides application and infrastructure monitoring. For more information, see xref:../logging/cluster-logging-external.adoc#cluster-logging-collector-log-forward-cloudwatch_cluster-logging-external[Forwarding logs to Amazon CloudWatch]. (link:https://issues.redhat.com/browse/LOG-1173[LOG-1173])
|
||||
|
||||
* With this update, you can forward log data to Loki, a horizontally scalable, highly available, multi-tenant log aggregation system. For more information, see xref:../logging/cluster-logging-external.html#cluster-logging-collector-log-forward-loki_cluster-logging-external[Forwarding logs to Loki]. (link:https://issues.redhat.com/browse/LOG-684[LOG-684])
|
||||
* With this update, you can forward log data to Loki, a horizontally scalable, highly available, multi-tenant log aggregation system. For more information, see xref:../logging/cluster-logging-external.adoc#cluster-logging-collector-log-forward-loki_cluster-logging-external[Forwarding logs to Loki]. (link:https://issues.redhat.com/browse/LOG-684[LOG-684])
|
||||
|
||||
* With this update, if you use the Fluentd forward protocol to forward log data over a TLS-encrypted connection, now you can use a password-encrypted private key file and specify the passphrase in the Cluster Log Forwarder configuration. For more information, see xref:../logging/cluster-logging-external.html#cluster-logging-collector-log-forward-fluentd_cluster-logging-external[Forwarding logs using the Fluentd forward protocol]. (link:https://issues.redhat.com/browse/LOG-1525[LOG-1525])
|
||||
* With this update, if you use the Fluentd forward protocol to forward log data over a TLS-encrypted connection, now you can use a password-encrypted private key file and specify the passphrase in the Cluster Log Forwarder configuration. For more information, see xref:../logging/cluster-logging-external.adoc#cluster-logging-collector-log-forward-fluentd_cluster-logging-external[Forwarding logs using the Fluentd forward protocol]. (link:https://issues.redhat.com/browse/LOG-1525[LOG-1525])
|
||||
|
||||
* This enhancement enables you to use a username and password to authenticate a log forwarding connection to an external Elasticsearch instance. For example, if you cannot use mutual TLS (mTLS) because a third-party operates the Elasticsearch instance, you can use HTTP or HTTPS and set a secret that contains the username and password. For more information, see xref:../logging/cluster-logging-external.adoc#cluster-logging-collector-log-forward-es_cluster-logging-external[Forwarding logs to an external Elasticsearch instance]. (link:https://issues.redhat.com/browse/LOG-1022[LOG-1022])
|
||||
|
||||
|
||||
@@ -32,7 +32,7 @@ include::modules/logging-support-considerations.adoc[leveloffset=+1]
|
||||
ifdef::openshift-rosa,openshift-dedicated[]
|
||||
include::modules/cluster-logging-cloudwatch.adoc[leveloffset=+1]
|
||||
.Next steps
|
||||
* See xref:../logging/cluster-logging-external.html#cluster-logging-collector-log-forward-cloudwatch_cluster-logging-external[Forwarding logs to Amazon CloudWatch] for instructions.
|
||||
* See xref:../logging/cluster-logging-external.adoc#cluster-logging-collector-log-forward-cloudwatch_cluster-logging-external[Forwarding logs to Amazon CloudWatch] for instructions.
|
||||
endif::[]
|
||||
|
||||
include::modules/logging-common-terms.adoc[leveloffset=+1]
|
||||
|
||||
@@ -30,5 +30,5 @@ CMD ["/bin/sh", "-c", "/input_report.sh"]
|
||||
====
|
||||
Users normally remove their input secrets from the final application image so that the secrets are not present in the container running from that image. However, the secrets still exist in the image itself in the layer where they were added. This removal is part of the Dockerfile itself.
|
||||
|
||||
To prevent the contents of input secrets and config maps from appearing in the build output container images and avoid this removal process altogether, xref:../../cicd/builds/build-strategies.html#builds-using-build-volumes_build-strategies-docker[use build volumes] in your Docker build strategy instead.
|
||||
To prevent the contents of input secrets and config maps from appearing in the build output container images and avoid this removal process altogether, xref:../../cicd/builds/build-strategies.adoc#builds-using-build-volumes_build-strategies-docker[use build volumes] in your Docker build strategy instead.
|
||||
====
|
||||
|
||||
@@ -7,7 +7,7 @@
|
||||
|
||||
[IMPORTANT]
|
||||
====
|
||||
To prevent the contents of input secrets and config maps from appearing in build output container images, use build volumes in your xref:../../cicd/builds/build-strategies.html#builds-using-build-volumes_build-strategies-docker[Docker build] and xref:../../cicd/builds/build-strategies.html#builds-using-build-volumes_build-strategies-s2i[source-to-image build] strategies.
|
||||
To prevent the contents of input secrets and config maps from appearing in build output container images, use build volumes in your xref:../../cicd/builds/build-strategies.adoc#builds-using-build-volumes_build-strategies-docker[Docker build] and xref:../../cicd/builds/build-strategies.adoc#builds-using-build-volumes_build-strategies-s2i[source-to-image build] strategies.
|
||||
====
|
||||
|
||||
In some scenarios, build operations require credentials or other configuration data to access dependent resources, but it is undesirable for that information to be placed in source control. You can define input secrets and input config maps for this purpose.
|
||||
|
||||
@@ -9,7 +9,7 @@ The _mirror registry for Red Hat OpenShift_ is a small and streamlined container
|
||||
|
||||
These release notes track the development of the _mirror registry for Red Hat OpenShift_ in {product-title}.
|
||||
|
||||
For an overview of the _mirror registry for Red Hat OpenShift_, see xref:../../installing/disconnected_install/installing-mirroring-creating-registry.html#mirror-registry-flags_installing-mirroring-creating-registry[Creating a mirror registry with mirror registry for Red Hat OpenShift].
|
||||
For an overview of the _mirror registry for Red Hat OpenShift_, see xref:../../installing/disconnected_install/installing-mirroring-creating-registry.adoc#mirror-registry-flags_installing-mirroring-creating-registry[Creating a mirror registry with mirror registry for Red Hat OpenShift].
|
||||
|
||||
[id="mirror-registry-for-openshift-1-3-6"]
|
||||
== Mirror registry for Red Hat OpenShift 1.3.6
|
||||
|
||||
@@ -25,7 +25,7 @@ Configuring the WebAssembly extension is currently a manual process. Support for
|
||||
|
||||
* Identify a Kubernetes workload and namespace on your {SMProductShortName} deployment that you will apply this module.
|
||||
* You must have a 3scale tenant account. See link:https://www.3scale.net/signup[SaaS] or link:https://access.redhat.com/documentation/en-us/red_hat_3scale_api_management/2.11/html-single/installing_3scale/index#install-threescale-on-openshift-guide[3scale 2.11 On-Premises] with a matching service and relevant applications and metrics defined.
|
||||
* If you apply the module to the `<product_page>` microservice in the `bookinfo` namespace, see the xref:../../service_mesh/v1x/prepare-to-deploy-applications-ossm.html#ossm-tutorial-bookinfo-overview_deploying-applications-ossm-v1x[Bookinfo sample application].
|
||||
* If you apply the module to the `<product_page>` microservice in the `bookinfo` namespace, see the xref:../../service_mesh/v1x/prepare-to-deploy-applications-ossm.adoc#ossm-tutorial-bookinfo-overview_deploying-applications-ossm-v1x[Bookinfo sample application].
|
||||
** The following example is the YAML format for the custom resource for `threescale-wasm-auth` module.
|
||||
This example refers to the upstream Maistra version of {SMProductShortName}, `WasmPlugin` API. You must declare the namespace where the `threescale-wasm-auth` module is deployed, alongside a `selector` to identify the set of applications the module will apply to:
|
||||
+
|
||||
|
||||
@@ -210,7 +210,7 @@ When using mTLS with workload specific PeerAuthentication policies, a correspond
|
||||
|
||||
Auto mTLS is enabled by default, but can be disabled by setting `spec.security.dataPlane.automtls` to false in the `ServiceMeshControlPlane` resource. When disabling auto mTLS, DestinationRules may be required for proper communication between services. For example, setting PeerAuthentication to `STRICT` for one namespace may prevent services in other namespaces from accessing them, unless a DestinationRule configures TLS mode for the services in the namespace.
|
||||
|
||||
For information about mTLS, see xref:../../service_mesh/v2x/ossm-security.html#ossm-security-mtls_ossm-security[Enabling mutual Transport Layer Security (mTLS)]
|
||||
For information about mTLS, see xref:../../service_mesh/v2x/ossm-security.adoc#ossm-security-mtls_ossm-security[Enabling mutual Transport Layer Security (mTLS)]
|
||||
|
||||
==== Other mTLS Examples
|
||||
|
||||
|
||||
@@ -52,7 +52,7 @@ Certain circumstances result in the Cluster Samples Operator bootstrapping itsel
|
||||
|
||||
* If the Cluster Samples Operator cannot reach link:https://registry.redhat.io[registry.redhat.io] after three minutes on initial startup after a clean installation.
|
||||
* If the Cluster Samples Operator detects it is on an IPv6 network.
|
||||
* If the xref:../openshift_images/image-configuration.html#images-configuration-parameters_image-configuration[image controller configuration parameters] prevent the creation of image streams by using the default image registry, or by using the image registry specified by the xref:../openshift_images/configuring-samples-operator.html#samples-operator-configuration_configuring-samples-operator[`samplesRegistry` setting].
|
||||
* If the xref:../openshift_images/image-configuration.adoc#images-configuration-parameters_image-configuration[image controller configuration parameters] prevent the creation of image streams by using the default image registry, or by using the image registry specified by the xref:../openshift_images/configuring-samples-operator.adoc#samples-operator-configuration_configuring-samples-operator[`samplesRegistry` setting].
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
|
||||
@@ -196,7 +196,7 @@ include::modules/monitoring-creating-scrape-sample-alerts.adoc[leveloffset=+2]
|
||||
|
||||
* xref:../monitoring/configuring-the-monitoring-stack.adoc#creating-user-defined-workload-monitoring-configmap_configuring-the-monitoring-stack[Creating a user-defined workload monitoring config map]
|
||||
* xref:../monitoring/enabling-monitoring-for-user-defined-projects.adoc#enabling-monitoring-for-user-defined-projects[Enabling monitoring for user-defined projects]
|
||||
* See xref:../monitoring/troubleshooting-monitoring-issues.html#determining-why-prometheus-is-consuming-disk-space_troubleshooting-monitoring-issues[Determining why Prometheus is consuming a lot of disk space] for steps to query which metrics have the highest number of scrape samples.
|
||||
* See xref:../monitoring/troubleshooting-monitoring-issues.adoc#determining-why-prometheus-is-consuming-disk-space_troubleshooting-monitoring-issues[Determining why Prometheus is consuming a lot of disk space] for steps to query which metrics have the highest number of scrape samples.
|
||||
endif::openshift-dedicated,openshift-rosa[]
|
||||
|
||||
//Configuring external alertmanagers
|
||||
|
||||
@@ -18,7 +18,7 @@ include::modules/monitoring-enabling-monitoring-for-user-defined-projects.adoc[l
|
||||
|
||||
* xref:../monitoring/configuring-the-monitoring-stack.adoc#creating-cluster-monitoring-configmap_configuring-the-monitoring-stack[Creating a cluster monitoring config map]
|
||||
* xref:../monitoring/configuring-the-monitoring-stack.adoc#configuring-the-monitoring-stack[Configuring the monitoring stack]
|
||||
* xref:../monitoring/enabling-monitoring-for-user-defined-projects.html#granting-users-permission-to-configure-monitoring-for-user-defined-projects_enabling-monitoring-for-user-defined-projects[Granting users permission to configure monitoring for user-defined projects]
|
||||
* xref:../monitoring/enabling-monitoring-for-user-defined-projects.adoc#granting-users-permission-to-configure-monitoring-for-user-defined-projects_enabling-monitoring-for-user-defined-projects[Granting users permission to configure monitoring for user-defined projects]
|
||||
|
||||
// Granting users permission to monitor user-defined projects
|
||||
include::modules/monitoring-granting-users-permission-to-monitor-user-defined-projects.adoc[leveloffset=+1]
|
||||
|
||||
@@ -38,7 +38,7 @@ include::modules/monitoring-determining-why-prometheus-is-consuming-disk-space.a
|
||||
|
||||
* See xref:../monitoring/configuring-the-monitoring-stack.adoc#setting-scrape-sample-and-label-limits-for-user-defined-projects_configuring-the-monitoring-stack[Setting a scrape sample limit for user-defined projects] for details on how to set a scrape sample limit and create related alerting rules
|
||||
ifndef::openshift-dedicated,openshift-rosa[]
|
||||
* xref:../support/getting-support.html#support-submitting-a-case_getting-support[Submitting a support case]
|
||||
* xref:../support/getting-support.adoc#support-submitting-a-case_getting-support[Submitting a support case]
|
||||
endif::openshift-dedicated,openshift-rosa[]
|
||||
ifdef::openshift-rosa[]
|
||||
* xref:../rosa_architecture/rosa-getting-support.adoc#rosa-getting-support_rosa-getting-support[Submitting a support case]
|
||||
|
||||
@@ -69,5 +69,5 @@ runC has some benefits over crun, including:
|
||||
|
||||
You can move between the two container runtimes as needed.
|
||||
|
||||
For information on setting which container runtime to use, see xref:../../post_installation_configuration/machine-configuration-tasks.html#create-a-containerruntimeconfig_post-install-machine-configuration-tasks[Creating a `ContainerRuntimeConfig` CR to edit CRI-O parameters].
|
||||
For information on setting which container runtime to use, see xref:../../post_installation_configuration/machine-configuration-tasks.adoc#create-a-containerruntimeconfig_post-install-machine-configuration-tasks[Creating a `ContainerRuntimeConfig` CR to edit CRI-O parameters].
|
||||
|
||||
|
||||
@@ -42,11 +42,11 @@ include::modules/nodes-rwn_con_adding-remote-worker-nodes.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/nodes-edge-remote-workers-network.adoc[leveloffset=+1]
|
||||
|
||||
For more information on using these objects in a cluster with remote worker nodes, see xref:../../nodes/edge/nodes-edge-remote-workers.html#nodes-edge-remote-workers-strategies_nodes-edge-remote-workers[About remote worker node strategies].
|
||||
For more information on using these objects in a cluster with remote worker nodes, see xref:../../nodes/edge/nodes-edge-remote-workers.adoc#nodes-edge-remote-workers-strategies_nodes-edge-remote-workers[About remote worker node strategies].
|
||||
|
||||
include::modules/nodes-edge-remote-workers-power.adoc[leveloffset=+1]
|
||||
|
||||
For more information on using these objects in a cluster with remote worker nodes, see xref:../../nodes/edge/nodes-edge-remote-workers.html#nodes-edge-remote-workers-strategies_nodes-edge-remote-workers[About remote worker node strategies].
|
||||
For more information on using these objects in a cluster with remote worker nodes, see xref:../../nodes/edge/nodes-edge-remote-workers.adoc#nodes-edge-remote-workers-strategies_nodes-edge-remote-workers[About remote worker node strategies].
|
||||
|
||||
[id="nodes-edge-remote-workers-latency"]
|
||||
== Latency spikes or temporary reduction in throughput to remote workers
|
||||
@@ -68,11 +68,11 @@ include::modules/nodes-edge-remote-workers-strategies.adoc[leveloffset=+1]
|
||||
|
||||
* For more information on configuring `KubeletConfig` objects, see xref:../../post_installation_configuration/node-tasks.adoc#create-a-kubeletconfig-crd-to-edit-kubelet-parameters_post-install-node-tasks[Creating a KubeletConfig CRD].
|
||||
|
||||
* For more information on replica sets, see xref:../../applications/deployments/what-deployments-are.html#deployments-repliasets_what-deployments-are[ReplicaSets].
|
||||
* For more information on replica sets, see xref:../../applications/deployments/what-deployments-are.adoc#deployments-repliasets_what-deployments-are[ReplicaSets].
|
||||
|
||||
* For more information on deployments, see xref:../../applications/deployments/what-deployments-are.html#deployments-kube-deployments_what-deployments-are[Deployments].
|
||||
* For more information on deployments, see xref:../../applications/deployments/what-deployments-are.adoc#deployments-kube-deployments_what-deployments-are[Deployments].
|
||||
|
||||
* For more information on replication controllers, see xref:../../applications/deployments/what-deployments-are.html#deployments-replicationcontrollers_what-deployments-are[Replication controllers].
|
||||
* For more information on replication controllers, see xref:../../applications/deployments/what-deployments-are.adoc#deployments-replicationcontrollers_what-deployments-are[Replication controllers].
|
||||
|
||||
* For more information on the controller manager, see xref:../../operators/operator-reference.adoc#kube-controller-manager-operator_cluster-operators-ref[Kubernetes Controller Manager Operator].
|
||||
|
||||
|
||||
@@ -19,4 +19,4 @@ include::modules/nodes-nodes-resources-cpus-reserve.adoc[leveloffset=+1]
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
|
||||
* For more information on the `systemReserved` and `kubeReserved` parameters, see xref:../../nodes/nodes/nodes-nodes-resources-configuring.html#nodes-nodes-resources-configuring-about_nodes-nodes-resources-configuring[Allocating resources for nodes in an {product-title} cluster].
|
||||
* For more information on the `systemReserved` and `kubeReserved` parameters, see xref:../../nodes/nodes/nodes-nodes-resources-configuring.adoc#nodes-nodes-resources-configuring-about_nodes-nodes-resources-configuring[Allocating resources for nodes in an {product-title} cluster].
|
||||
|
||||
@@ -21,9 +21,9 @@ include::modules/nodes-pods-secrets-about.adoc[leveloffset=+1]
|
||||
|
||||
.Additional resources
|
||||
|
||||
* For information about requesting bound service account tokens, see xref:../../authentication/bound-service-account-tokens.html#bound-sa-tokens-configuring_bound-service-account-tokens[Using bound service account tokens]
|
||||
* For information about requesting bound service account tokens, see xref:../../authentication/bound-service-account-tokens.adoc#bound-sa-tokens-configuring_bound-service-account-tokens[Using bound service account tokens]
|
||||
|
||||
* For information about creating a service account token secret, see xref:../../nodes/pods/nodes-pods-secrets.html#nodes-pods-secrets-creating-sa_nodes-pods-secrets[Creating a service account token secret].
|
||||
* For information about creating a service account token secret, see xref:../../nodes/pods/nodes-pods-secrets.adoc#nodes-pods-secrets-creating-sa_nodes-pods-secrets[Creating a service account token secret].
|
||||
|
||||
include::modules/nodes-pods-secrets-creating.adoc[leveloffset=+1]
|
||||
|
||||
@@ -41,7 +41,7 @@ include::modules/nodes-pods-secrets-creating-sa.adoc[leveloffset=+2]
|
||||
|
||||
* For more information on using secrets in pods, see xref:../../nodes/pods/nodes-pods-secrets.adoc#nodes-pods-secrets-creating_nodes-pods-secrets[Understanding how to create secrets].
|
||||
|
||||
* For information on requesting bound service account tokens, see xref:../../authentication/bound-service-account-tokens.html#bound-sa-tokens-configuring_bound-service-account-tokens[Using bound service account tokens]
|
||||
* For information on requesting bound service account tokens, see xref:../../authentication/bound-service-account-tokens.adoc#bound-sa-tokens-configuring_bound-service-account-tokens[Using bound service account tokens]
|
||||
|
||||
* For information on creating service accounts, see xref:../../authentication/understanding-and-creating-service-accounts.adoc#understanding-and-creating-service-accounts[Understanding and creating service accounts].
|
||||
|
||||
|
||||
@@ -29,7 +29,7 @@ include::modules/images-configuration-registry-mirror.adoc[leveloffset=+2]
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
|
||||
* For more information about global pull secrets, see xref:../openshift_images/managing_images/using-image-pull-secrets.html#images-update-global-pull-secret_using-image-pull-secrets[Updating the global cluster pull secret].
|
||||
* For more information about global pull secrets, see xref:../openshift_images/managing_images/using-image-pull-secrets.adoc#images-update-global-pull-secret_using-image-pull-secrets[Updating the global cluster pull secret].
|
||||
|
||||
include::modules/images-configuration-registry-mirror-convert.adoc[leveloffset=+2]
|
||||
|
||||
|
||||
@@ -17,7 +17,7 @@ include::modules/installation-about-mirror-registry.adoc[leveloffset=+1]
|
||||
|
||||
.Additional information
|
||||
|
||||
For information on viewing the CRI-O logs to view the image source, see xref:../installing/validating-an-installation.html#viewing-the-image-pull-source_validating-an-installation[Viewing the image pull source].
|
||||
For information on viewing the CRI-O logs to view the image source, see xref:../installing/validating-an-installation.adoc#viewing-the-image-pull-source_validating-an-installation[Viewing the image pull source].
|
||||
|
||||
[id="samples-preparing-bastion"]
|
||||
=== Preparing the mirror host
|
||||
|
||||
@@ -94,6 +94,6 @@ include::modules/olm-overriding-operator-pod-affinity.adoc[leveloffset=+1]
|
||||
.Additional resources
|
||||
|
||||
* xref:../../nodes/scheduling/nodes-scheduler-pod-affinity.adoc#nodes-scheduler-pod-affinity-about_nodes-scheduler-pod-affinity[Understanding pod affinity]
|
||||
* xref:../../nodes/scheduling/nodes-scheduler-node-affinity.html#nodes-scheduler-node-affinity-about_nodes-scheduler-node-affinity[Understanding node affinity]
|
||||
* xref:../../nodes/scheduling/nodes-scheduler-node-affinity.adoc#nodes-scheduler-node-affinity-about_nodes-scheduler-node-affinity[Understanding node affinity]
|
||||
* xref:../../nodes/nodes/nodes-nodes-working.adoc#nodes-nodes-working-updating_nodes-nodes-working[Understanding how to update labels on nodes].
|
||||
|
||||
|
||||
@@ -553,7 +553,7 @@ include::modules/installation-extend-edge-nodes-aws-local-zones.adoc[leveloffset
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
|
||||
* xref:../installing/installing_aws/installing-aws-localzone.html[Installing a cluster using AWS Local Zones]
|
||||
* xref:../installing/installing_aws/installing-aws-localzone.adoc[Installing a cluster using AWS Local Zones]
|
||||
|
||||
* xref:../nodes/scheduling/nodes-scheduler-taints-tolerations.adoc[Understanding taints and tolerations]
|
||||
|
||||
|
||||
@@ -84,4 +84,4 @@ include::modules/deploy-red-hat-openshift-container-storage.adoc[leveloffset=+1]
|
||||
[id="admission-plug-ins-additional-resources"]
|
||||
== Additional resources
|
||||
|
||||
* xref:../logging/config/cluster-logging-log-store.html#cluster-logging-elasticsearch-storage_cluster-logging-store[Configuring persistent storage for the log store]
|
||||
* xref:../logging/config/cluster-logging-log-store.adoc#cluster-logging-elasticsearch-storage_cluster-logging-store[Configuring persistent storage for the log store]
|
||||
|
||||
@@ -25,9 +25,9 @@ include::modules/rosa-update-cli-tool.adoc[]
|
||||
[id="rosa-q2-2023_{context}"]
|
||||
=== Q2 2023
|
||||
|
||||
* **ROSA CLI update:** The ROSA CLI (`rosa`) was updated to a new version. For information about what's changed in this release, see the link:https://github.com/openshift/rosa/releases/tag/v1.2.23[release notes]. For more information about the ROSA CLI (`rosa`), see xref:../rosa_cli/rosa-get-started-cli.html[Getting started with the rosa CLI].
|
||||
* **ROSA CLI update:** The ROSA CLI (`rosa`) was updated to a new version. For information about what's changed in this release, see the link:https://github.com/openshift/rosa/releases/tag/v1.2.23[release notes]. For more information about the ROSA CLI (`rosa`), see xref:../rosa_cli/rosa-get-started-cli.adoc[Getting started with the rosa CLI].
|
||||
|
||||
* **ROSA regional availability update:** {product-title} (ROSA) is now available in the United Arab Emirates (`me-central-1`) region. For more information on region availability, see xref:../rosa_architecture/rosa_policy_service_definition/rosa-service-definition.html#rosa-sdpolicy-regions-az_rosa-service-definition[Regions and availability zones].
|
||||
* **ROSA regional availability update:** {product-title} (ROSA) is now available in the United Arab Emirates (`me-central-1`) region. For more information on region availability, see xref:../rosa_architecture/rosa_policy_service_definition/rosa-service-definition.adoc#rosa-sdpolicy-regions-az_rosa-service-definition[Regions and availability zones].
|
||||
|
||||
include::snippets/rosa-hcp-rn.adoc[leveloffset=+1]
|
||||
:featureName: ROSA with HCP
|
||||
|
||||
@@ -36,4 +36,4 @@ include::modules/optimizing-storage-azure.adoc[leveloffset=+1]
|
||||
[id="admission-plug-ins-additional-resources"]
|
||||
== Additional resources
|
||||
|
||||
* xref:../../logging/config/cluster-logging-log-store.html#cluster-logging-elasticsearch-storage_cluster-logging-store[Configuring persistent storage for the log store]
|
||||
* xref:../../logging/config/cluster-logging-log-store.adoc#cluster-logging-elasticsearch-storage_cluster-logging-store[Configuring persistent storage for the log store]
|
||||
|
||||
@@ -21,7 +21,7 @@ If the control plane machines in an Amazon Web Services (AWS) cluster require mo
|
||||
====
|
||||
The procedure for clusters that use a control plane machine set is different from the procedure for clusters that do not use a control plane machine set.
|
||||
|
||||
If you are uncertain about the state of the `ControlPlaneMachineSet` CR in your cluster, you can xref:../../machine_management/control_plane_machine_management/cpmso-getting-started.html#cpmso-checking-status_cpmso-getting-started[verify the CR status].
|
||||
If you are uncertain about the state of the `ControlPlaneMachineSet` CR in your cluster, you can xref:../../machine_management/control_plane_machine_management/cpmso-getting-started.adoc#cpmso-checking-status_cpmso-getting-started[verify the CR status].
|
||||
====
|
||||
|
||||
//Changing the Amazon Web Services instance type by using a control plane machine set
|
||||
|
||||
@@ -17,7 +17,7 @@ include::modules/ztp-acm-installing-disconnected-rhacm.adoc[leveloffset=+1]
|
||||
|
||||
* xref:../../cicd/gitops/installing-openshift-gitops.adoc#getting-started-with-openshift-gitops[Installing OpenShift GitOps]
|
||||
|
||||
* xref:../../scalability_and_performance/cnf-talm-for-cluster-upgrades.html#installing-topology-aware-lifecycle-manager-using-cli_cnf-topology-aware-lifecycle-manager[Installing {cgu-operator}]
|
||||
* xref:../../scalability_and_performance/cnf-talm-for-cluster-upgrades.adoc#installing-topology-aware-lifecycle-manager-using-cli_cnf-topology-aware-lifecycle-manager[Installing {cgu-operator}]
|
||||
|
||||
* xref:../../operators/admin/olm-restricted-networks.adoc#olm-mirror-catalog_olm-restricted-networks[Mirroring an Operator catalog]
|
||||
|
||||
|
||||
@@ -76,7 +76,7 @@ include::modules/insights-operator-what-information-is-collected.adoc[leveloffse
|
||||
.Additional resources
|
||||
|
||||
ifndef::openshift-dedicated,openshift-rosa[]
|
||||
* See xref:../../sd_support/remote_health_monitoring/showing-data-collected-by-remote-health-monitoring.html#insights-operator-showing-data-collected-from-the-cluster_showing-data-collected-by-remote-health-monitoring[Showing data collected by the Insights Operator] for details about how to review the data that is collected by the Insights Operator.
|
||||
* See xref:../../sd_support/remote_health_monitoring/showing-data-collected-by-remote-health-monitoring.adoc#insights-operator-showing-data-collected-from-the-cluster_showing-data-collected-by-remote-health-monitoring[Showing data collected by the Insights Operator] for details about how to review the data that is collected by the Insights Operator.
|
||||
endif::[]
|
||||
|
||||
* The Insights Operator source code is available for review and contribution. See the link:https://github.com/openshift/insights-operator/blob/master/docs/gathered-data.md[Insights Operator upstream project] for a list of the items collected by the Insights Operator.
|
||||
|
||||
@@ -19,4 +19,4 @@ include::modules/compliance-profiles.adoc[leveloffset=+1]
|
||||
[role="_additional-resources"]
|
||||
== Additional resources
|
||||
|
||||
* xref:../../security/compliance_operator/compliance-operator-supported-profiles.html#compliance-operator-supported-profiles[Supported compliance profiles]
|
||||
* xref:../../security/compliance_operator/compliance-operator-supported-profiles.adoc#compliance-operator-supported-profiles[Supported compliance profiles]
|
||||
|
||||
@@ -36,7 +36,7 @@ The following advisory is available for the OpenShift File Integrity Operator 1.
|
||||
|
||||
* The File Integrity Operator Custom Resource (CR) now contains an `initialDelay` feature that specifies the number of seconds to wait before starting the first AIDE integrity check. For more information, see xref:../../security/file_integrity_operator/file-integrity-operator-understanding.adoc#understanding-file-integrity-custom-resource_file-integrity-operator[Creating the FileIntegrity custom resource].
|
||||
|
||||
* The File Integrity Operator is now stable and the release channel is upgraded to `stable`. Future releases will follow link:https://semver.org/[Semantic Versioning]. To access the latest release, see xref:../../security/file_integrity_operator/file-integrity-operator-updating.html#olm-preparing-upgrade_file-integrity-operator-updating[Updating the File Integrity Operator].
|
||||
* The File Integrity Operator is now stable and the release channel is upgraded to `stable`. Future releases will follow link:https://semver.org/[Semantic Versioning]. To access the latest release, see xref:../../security/file_integrity_operator/file-integrity-operator-updating.adoc#olm-preparing-upgrade_file-integrity-operator-updating[Updating the File Integrity Operator].
|
||||
|
||||
[id="file-integrity-operator-release-notes-1-0-0"]
|
||||
== OpenShift File Integrity Operator 1.0.0
|
||||
|
||||
@@ -30,5 +30,5 @@ include::modules/spo-container-profile-instances.adoc[leveloffset=+2]
|
||||
|
||||
* xref:../../authentication/managing-security-context-constraints.adoc[Managing security context constraints]
|
||||
* link:https://cloud.redhat.com/blog/managing-sccs-in-openshift[Managing SCCs in OpenShift]
|
||||
* xref:../../security/security_profiles_operator/spo-advanced.html#spo-log-enricher_spo-advanced[Using the log enricher]
|
||||
* xref:../../security/security_profiles_operator/spo-understanding.html#spo-about_spo-understanding[About security profiles]
|
||||
* xref:../../security/security_profiles_operator/spo-advanced.adoc#spo-log-enricher_spo-advanced[Using the log enricher]
|
||||
* xref:../../security/security_profiles_operator/spo-understanding.adoc#spo-about_spo-understanding[About security profiles]
|
||||
@@ -36,5 +36,5 @@ include::modules/spo-selinux-runasany.adoc[leveloffset=+2]
|
||||
|
||||
* xref:../../authentication/managing-security-context-constraints.adoc[Managing security context constraints]
|
||||
* link:https://cloud.redhat.com/blog/managing-sccs-in-openshift[Managing SCCs in OpenShift]
|
||||
* xref:../../security/security_profiles_operator/spo-advanced.html#spo-log-enricher_spo-advanced[Using the log enricher]
|
||||
* xref:../../security/security_profiles_operator/spo-understanding.html#spo-about_spo-understanding[About security profiles]
|
||||
* xref:../../security/security_profiles_operator/spo-advanced.adoc#spo-log-enricher_spo-advanced[Using the log enricher]
|
||||
* xref:../../security/security_profiles_operator/spo-understanding.adoc#spo-about_spo-understanding[About security profiles]
|
||||
@@ -24,7 +24,7 @@ include::modules/ossm-cr-istio-global.adoc[leveloffset=+2]
|
||||
include::modules/ossm-cr-gateway.adoc[leveloffset=+2]
|
||||
|
||||
ifdef::openshift-enterprise[]
|
||||
Cluster administrators can refer to xref:../../networking/ingress-operator.html#using-wildcard-routes_configuring-ingress[Using wildcard routes] for instructions on how to enable subdomains.
|
||||
Cluster administrators can refer to xref:../../networking/ingress-operator.adoc#using-wildcard-routes_configuring-ingress[Using wildcard routes] for instructions on how to enable subdomains.
|
||||
endif::[]
|
||||
|
||||
include::modules/ossm-cr-mixer.adoc[leveloffset=+2]
|
||||
|
||||
@@ -11,7 +11,7 @@ After adding the namespaces that contain your services to your mesh, the next st
|
||||
If you have installed the Bookinfo sample application, the application was deployed and the sidecars were injected as part of the installation procedure. If you are using your own project and service, deploy your applications on {product-title}.
|
||||
|
||||
ifdef::openshift-enterprise[]
|
||||
For more information, see the {product-title} documentation, xref:../../applications/deployments/what-deployments-are.html[Understanding Deployment and DeploymentConfig objects].
|
||||
For more information, see the {product-title} documentation, xref:../../applications/deployments/what-deployments-are.adoc[Understanding Deployment and DeploymentConfig objects].
|
||||
endif::[]
|
||||
|
||||
== Prerequisites
|
||||
|
||||
@@ -3,4 +3,4 @@
|
||||
// * rosa_release_notes/rosa-release-notes.adoc
|
||||
|
||||
:_content-type: SNIPPET
|
||||
* **Hosted control planes:** {hcp-title-first} clusters are now available as a link:https://access.redhat.com/support/offerings/techpreview[Technology Preview] feature. This new architecture provides a lower-cost, more resilient ROSA architecture. For more information, see xref:../rosa_hcp/rosa-hcp-sts-creating-a-cluster-quickly.html[Creating {hcp-title} clusters using the default options].
|
||||
* **Hosted control planes:** {hcp-title-first} clusters are now available as a link:https://access.redhat.com/support/offerings/techpreview[Technology Preview] feature. This new architecture provides a lower-cost, more resilient ROSA architecture. For more information, see xref:../rosa_hcp/rosa-hcp-sts-creating-a-cluster-quickly.adoc[Creating {hcp-title} clusters using the default options].
|
||||
@@ -40,4 +40,4 @@ include::modules/ephemeral-storage-integration-between-shared-resources-insights
|
||||
.Additional resources
|
||||
|
||||
* xref:../../support/remote_health_monitoring/insights-operator-simple-access.adoc#insights-operator-simple-access[Importing simple content access certificates with Insights Operator]
|
||||
* xref:../../cicd/builds/running-entitled-builds.html#builds-source-secrets-entitlements_running-entitled-builds[Adding subscription entitlements as a build secret]
|
||||
* xref:../../cicd/builds/running-entitled-builds.adoc#builds-source-secrets-entitlements_running-entitled-builds[Adding subscription entitlements as a build secret]
|
||||
|
||||
@@ -78,7 +78,7 @@ include::modules/insights-operator-what-information-is-collected.adoc[leveloffse
|
||||
.Additional resources
|
||||
|
||||
ifndef::openshift-dedicated[]
|
||||
* See xref:../../support/remote_health_monitoring/showing-data-collected-by-remote-health-monitoring.html#insights-operator-showing-data-collected-from-the-cluster_showing-data-collected-by-remote-health-monitoring[Showing data collected by the Insights Operator] for details about how to review the data that is collected by the Insights Operator.
|
||||
* See xref:../../support/remote_health_monitoring/showing-data-collected-by-remote-health-monitoring.adoc#insights-operator-showing-data-collected-from-the-cluster_showing-data-collected-by-remote-health-monitoring[Showing data collected by the Insights Operator] for details about how to review the data that is collected by the Insights Operator.
|
||||
endif::[]
|
||||
|
||||
* The Insights Operator source code is available for review and contribution. See the link:https://github.com/openshift/insights-operator/blob/master/docs/gathered-data.md[Insights Operator upstream project] for a list of the items collected by the Insights Operator.
|
||||
|
||||
@@ -50,4 +50,4 @@ include::modules/understanding-update-channels.adoc[leveloffset=+1]
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
* xref:../../updating/updating_a_cluster/updating-cluster-cli.adoc#update-conditional-upgrade-pathupdating-cluster-cli[Updating along a conditional upgrade path]
|
||||
* xref:../../updating/understanding_updates/understanding-update-channels-release.html#fast-stable-channel-strategies_understanding-update-channels-releases[Choosing the correct channel for your cluster]
|
||||
* xref:../../updating/understanding_updates/understanding-update-channels-release.adoc#fast-stable-channel-strategies_understanding-update-channels-releases[Choosing the correct channel for your cluster]
|
||||
|
||||
@@ -6,6 +6,6 @@ include::_attributes/common-attributes.adoc[]
|
||||
|
||||
toc::[]
|
||||
|
||||
To get started using the dynamic plugin, you must set up your environment to write a new {product-title} dynamic plugin. For an example of how to write a new plugin, see xref:../../web_console/dynamic-plugin/dynamic-plugin-example.html#adding-tab-to-pods-page_dynamic-plugin-example[Adding a tab to the pods page].
|
||||
To get started using the dynamic plugin, you must set up your environment to write a new {product-title} dynamic plugin. For an example of how to write a new plugin, see xref:../../web_console/dynamic-plugin/dynamic-plugin-example.adoc#adding-tab-to-pods-page_dynamic-plugin-example[Adding a tab to the pods page].
|
||||
|
||||
include::modules/dynamic-plug-in-development.adoc[leveloffset=+1]
|
||||
|
||||
@@ -265,7 +265,7 @@ You can xref:../storage/expanding-persistent-volumes.adoc#expanding-persistent-v
|
||||
|
||||
- **xref:../operators/understanding/olm-understanding-operatorhub.adoc#olm-understanding-operatorhub[Manage Operators]**: Lists of Red Hat, ISV, and community Operators can be reviewed by cluster administrators and xref:../operators/admin/olm-adding-operators-to-cluster.adoc#olm-adding-operators-to-a-cluster[installed on their clusters]. After you install them, you can xref:../operators/user/olm-creating-apps-from-installed-operators.adoc#olm-creating-apps-from-installed-operators[run], xref:../operators/admin/olm-upgrading-operators.adoc#olm-upgrading-operators[upgrade], back up, or otherwise manage the Operator on your cluster.
|
||||
|
||||
- **xref:../windows_containers/understanding-windows-container-workloads.html#understanding-windows-container-workloads_understanding-windows-container-workloads[Understanding Windows container workloads]**. You can use the {productwinc} feature to run Windows compute nodes in an {product-title} cluster. This is possible by using the Red Hat Windows Machine Config Operator (WMCO) to install and manage Windows nodes.
|
||||
- **xref:../windows_containers/understanding-windows-container-workloads.adoc#understanding-windows-container-workloads_understanding-windows-container-workloads[Understanding Windows container workloads]**. You can use the {productwinc} feature to run Windows compute nodes in an {product-title} cluster. This is possible by using the Red Hat Windows Machine Config Operator (WMCO) to install and manage Windows nodes.
|
||||
|
||||
=== Change cluster components
|
||||
|
||||
|
||||
Reference in New Issue
Block a user