file to /tmp/bar in a remote pod in namespace tar cf - /tmp/foo | oc exec -i -n -- tar xf - -C /tmp/bar # Copy /tmp/foo from a remote pod to /tmp/bar locally local directory to /tmp/bar_dir in a remote pod in the default namespace oc cp /tmp/foo_dir :/tmp/bar_dir # Copy /tmp/foo local file to /tmp/bar in a remote pod in a specific container oc /tmp/foo local file to /tmp/bar in a remote pod in namespace oc cp /tmp/foo /:/tmp/bar # Copy /tmp/foo from a remote pod to /tmp/bar locally oc cp

0 码力 | 120 页 | 1.04 MB | 1 年前

3

file to /tmp/bar in a remote pod in namespace tar cf - /tmp/foo | oc exec -i -n -- tar xf - -C /tmp/bar # Copy /tmp/foo from a remote pod to /tmp/bar locally local directory to /tmp/bar_dir in a remote pod in the default namespace oc cp /tmp/foo_dir :/tmp/bar_dir # Copy /tmp/foo local file to /tmp/bar in a remote pod in a specific container oc /tmp/foo local file to /tmp/bar in a remote pod in namespace oc cp /tmp/foo /:/tmp/bar # Copy /tmp/foo from a remote pod to /tmp/bar locally oc cp

0 码力 | 128 页 | 1.11 MB | 1 年前

3

file to /tmp/bar in a remote pod in namespace tar cf - /tmp/foo | oc exec -i -n -- tar xf - -C /tmp/bar # Copy /tmp/foo from a remote pod to /tmp/bar locally local directory to /tmp/bar_dir in a remote pod in the default namespace oc cp /tmp/foo_dir :/tmp/bar_dir # Copy /tmp/foo local file to /tmp/bar in a remote pod in a specific container oc /tmp/foo local file to /tmp/bar in a remote pod in namespace oc cp /tmp/foo /:/tmp/bar # Copy /tmp/foo from a remote pod to /tmp/bar locally oc cp

0 码力 | 152 页 | 1.24 MB | 1 年前

3

Container Platform。基本身份验证是一种通用后端集成机制。 请求标头 （Request header） 配置 request-header 身份提供程序，标识请求标头值中的用户，例如 X-Remote- User。它通常与设定请求标头值的身份验证代理一起使用。 Github 或 GitHub Enterprise 配置 github 身份提供程序，针对 GitHub 或 GitHub Enterprise mappingMethod: claim 2 type: BasicAuth basicAuth: url: https://www.example.com/remote-idp 3 ca: 4 name: ca-config-map tlsClientCert: 5 name: client-cert-secret oc whoami OpenShift Container Platform 4.13 认证 认证和授 和授权 权 44 echo '{"sub":"userid", "name":"'$REMOTE_USER'"}' exit 0 /var/www/cgi-bin/fail.cgi 示例 示例 #!/bin/bash echo "Content-Type: application/json"

openshift-monitoring data: config.yaml: | prometheusK8s: remoteWrite: - url: "https://remote-write.endpoint" 第 第 2 章 章 配置 配置监 监控堆 控堆栈 栈 35 对于 openshift-monitoring data: config.yaml: | prometheusK8s: remoteWrite: - url: "https://remote-write.endpoint" basicAuth: username: name: remoteWriteAuth Prometheus 实例配置远程写入，如下所示： config.yaml: | prometheusK8s: remoteWrite: - url: "https://remote-write.endpoint" tlsConfig: ca: secret: name: selfsigned-mtls-bundle

ServiceMeshPeer 对象的 .spec.remote.addresses 字段中的条目之一。 如果集群不支持 LoadBalancer 服务，则如果节点可从运行其他网格的集群访问，则可以使用 NodePort 服务。在 ServiceMeshPeer 对象中，在 .spec.remote.addresses 字段中指定节点的 IP 地址，并在 .spec.remote.discoveryPort 和 .spec.remote.servicePort 字段中指定服务的节点端口。 1.18.7.2. 在 在 IBM Power 和 和 IBM Z 上 上运 运行的集群中公开 行的集群中公开 federation ingress 如果集群在 IBM Power 或 IBM Z 基础架构上运行，且完全支持 LoadBalancer 服务，则 ingress 网关 Service 对象的 .status status.loadBalancer.ingress.ip 字段中应当指定为 ServiceMeshPeer 对象的 .spec.remote.addresses 字段中的条目之一。 如果集群不支持 LoadBalancer 服务，则如果节点可从运行其他网格的集群访问，则可以使用 NodePort 第 第 1 章 章 SERVICE MESH 2.X 117 如果集群不支持 LoadBalancer

OpenShift Container Platform 管理控制台或机器配置池更新触发裸机主机重启时，OpenShift Container Platform 日志会登录 到集成的 Dell Remote Access Controller (iDrac)，并发出删除作业队列。 要防止管理与可用 BareMetalHost 对象数量匹配的 Machine 对象数量，请在 MachineSet 对象中添加 ------------------------------ [performance] Latency Test with the hwlatdetect image should succeed /remote-source/app/vendor/github.com/openshift-kni/performance-addon- operators/functests/4_latency/latency [performance] Latency Test /remote-source/app/vendor/github.com/openshift-kni/performance-addon- operators/functests/4_latency/latency.go:60 with the hwlatdetect image /remote-source/app/vendor/github

您要置备的卷大小。集群必须满足特定要求，如 CPU 和内存要求。如果要在 OpenShift Data Foundation 配置中使用存储提供商动态调配的远程卷，请选择 OpenShift Data Foundation-remote 存储模板。 如需更多信息，请参阅 IBM Cloud Satellite 远程 OpenShift Data Foundation 存储文档 。 Red Hat OpenShift Data