Storagetype ：用于配置 registry 存储的详细信息，例如S3 bucket坐标。通常 会被默认配置。 readOnly registry 实例是否应该拒绝推送新镜像或删除现有镜像的尝试。 requests API Request Limit 详情。控制在把请求放入队列前，registry 实例可以并行处理 的请求数量。 defaultRoute 确定是否使用默认主机名定义外部路由。如果启用，该路由将会对加密进行重新 正在使用您定义的资源： 1. 验证 PVC 声明值是否与您在 PVC 定义中提供的名称相同： 输 输出示例 出示例 2. 验证 PVC 的状态是否为 Bound： resources: requests: storage: 100Gi 2 storageClassName: 3 $ oc apply -f namespace: openshift-image-registry 2 spec: accessModes: - ReadWriteOnce 3 resources: requests: storage: 100Gi 4 OpenShift Container Platform 4.12 容器 容器镜 镜像 像仓库 仓库（ （Registry） ） 24 1

dataVolumeClaimSpec: accessModes: - "ReadWriteOnce" resources: requests: storage: 1Gi backups: pgbackrest: image: registry.developers.crunchydata 配置本地环境才能测试应用程序。 流程 1. 在 shell 中运行以下命令，使用 PostgresCluster 自定义资源(CR)部署 spring-petclinic 应用程 序： requests: storage: 1Gi - name: repo2 volume: volumeClaimSpec: accessModes: - "ReadWriteOnce" resources: requests: storage: 1Gi proxy: pgBouncer: image: registry.developers.crunchydata.co

Storagetype ：用于配置 registry 存储的详细信息，例如S3 bucket坐标。通常 会被默认配置。 readOnly registry 实例是否应该拒绝推送新镜像或删除现有镜像的尝试。 requests API Request Limit 详情。控制在把请求放入队列前，registry 实例可以并行处理 的请求数量。 defaultRoute 确定是否使用默认主机名定义外部路由。如果启用，该路由将会对加密进行重新 openshift.io: "true" spec: accessModes: - ReadWriteOnce volumeMode: Filesystem resources: requests: storage: 100Gi 2 storageClassName: 3 $ oc apply -f namespace: openshift-image-registry 2 spec: accessModes: - ReadWriteOnce 3 resources: requests: storage: 100Gi 4 $ oc create -f pvc.yaml -n openshift-image-registry $ oc edit config.imageregistry

dataVolumeClaimSpec: accessModes: - "ReadWriteOnce" resources: requests: storage: 1Gi backups: pgbackrest: image: registry.developers.crunchydata volumeClaimSpec: accessModes: - "ReadWriteOnce" resources: requests: storage: 1Gi - name: repo2 volume: volumeClaimSpec: accessModes: - "ReadWriteOnce" resources: requests: storage: 1Gi proxy: pgBouncer: image: registry.developers.crunchydata.co

中的每个容器可以指定以下内容： spec.containers[].resources.limits.ephemeral-storage spec.containers[].resources.requests.ephemeral-storage 临时存储的限制和请求以字节数量来衡量。您可以使用以下后缀之一将存储表示为普通整数或固定点号： E、P、T、G、M、k。您还可以使用两的指数：Ei、Pi、Ti、Gi、Mi spec: containers: - name: app image: images.my-company.example/app:v4 resources: requests: ephemeral-storage: "2Gi" 1 limits: ephemeral-storage: "4Gi" 2 volumeMounts: name: log-aggregator image: images.my-company.example/log-aggregator:v6 resources: requests: ephemeral-storage: "2Gi" 3 volumeMounts: - name: ephemeral mountPath: "/tmp"

name: full-install spec: istio: global: proxy: resources: requests: cpu: 100m memory: 128Mi limits: cpu: 500m autoscaleEnabled: false telemetry: autoscaleEnabled: false resources: requests: cpu: 100m memory: 1G limits: cpu: 500m hub: registry.redhat.io/openshift-service-mesh/ proxy: resources: requests: cpu: 10m memory: 128Mi limits: mtls: enabled: false

storageClassName: fast volumeMode: Filesystem resources: requests: storage: 40Gi $ oc -n openshift-user-workload-monitoring edit configmap user-workload- toring data: config.yaml: | prometheus: 1 retention: 24h 2 resources: requests: cpu: 200m 3 memory: 2Gi 4  OpenShift Container Platform 4.10 监 监控 控 16 volumeClaimTemplate: spec: storageClassName: resources: requests: storage: apiVersion: v1 kind: ConfigMap metadata: name: c

6 size: 200G resources: 7 limits: memory: "16Gi" requests: memory: "16Gi" proxy: 8 resources: limits: memory: 化工具。 用于配置 Fluentd 的设置。通过使用 CR，您可以配置 Fluentd CPU 和内存限值。如需 更多信息，请参阅配置 配置 Fluentd。 注意 注意 requests: memory: 256Mi redundancyPolicy: "SingleRedundancy" visualization: type: limits: memory: "16Gi" requests: memory: "16Gi" proxy: 8 resources: limits: memory: 256Mi requests: memory: 256Mi redundancyPolicy:

6 size: 200G resources: 7 limits: memory: "16Gi" requests: memory: "16Gi" proxy: 8 resources: limits: memory: 化工具。 用于配置 Fluentd 的设置。通过使用 CR，您可以配置 Fluentd CPU 和内存限值。如需 更多信息，请参阅配置 配置 Fluentd。 注意 注意 requests: memory: 256Mi redundancyPolicy: "SingleRedundancy" visualization: type: limits: memory: "16Gi" requests: memory: "16Gi" proxy: 8 resources: limits: memory: 256Mi requests: memory: 256Mi redundancyPolicy:

apiVersion: v1 metadata: name: myclaim 1 spec: accessModes: - ReadWriteOnce 2 resources: requests: storage: 8Gi 3 storageClassName: gold 4 status: ... OpenShift Container Platform 4.8 name: block-pvc spec: accessModes: - ReadWriteOnce volumeMode: Block 1 resources: requests: storage: 10Gi 第 第 3 章 章 了解持久性存 了解持久性存储 储 19 1 1 2 3 需要把 volumeMode 设置为 Block 来代表请求一个原始块 "PersistentVolumeClaim" metadata: name: "claim1" 1 spec: accessModes: - "ReadWriteOnce" resources: requests: storage: "5Gi" 2 storageClassName: azure-file-sc 3 volumeName: "pv0001" 4 apiVersion: