1.72. oc expose 将复制的应用程序作为服务或路由公开 用法示例 用法示例 # Edit the job 'myjob' in JSON using the v1 API format oc edit job.v1.batch/myjob -o json # Edit the deployment 'mydeployment' in YAML and save the append 向镜像添加层并将其推送到 registry 用法示例 用法示例 # List all pods in ps output format oc get pods # List all pods in ps output format with more information (such as node name) oc get pods -o wide # List single replication controller with specified NAME in ps output format oc get replicationcontroller web # List deployments in JSON output format, in the "v1" version of the "apps" API group oc get deployments

editor KUBE_EDITOR="nano" oc edit svc/registry # Edit the job 'myjob' in JSON using the v1 API format oc edit job.v1.batch/myjob -o json # Edit the deployment 'mydeployment' in YAML and save the them as they arrive. oc events --for pod/web-pod-13je7 --watch # List recent events in given format. Supported ones, apart from default, are json and yaml. oc events -oyaml # List recent only 用法示例 用法示例 2.7.1.78. oc image append # List all pods in ps output format oc get pods # List all pods in ps output format with more information (such as node name) oc get pods -o wide # List

KUBE_EDITOR="nano" oc edit svc/docker-registry # Edit the job 'myjob' in JSON using the v1 API format: oc edit job.v1.batch/myjob -o json # Edit the deployment 'mydeployment' in YAML and save the configmap/nginx --to=/tmp --keys=nginx.conf # List all pods in ps output format. oc get pods # List all pods in ps output format with more information (such as node name). oc get pods -o wide # single replication controller with specified NAME in ps output format. oc get replicationcontroller web # List deployments in JSON output format, in the "v1" version of the "apps" API group: oc get deployments

$ cat < containers.json { "Description": "rhcos-${RHCOS_VERSION}-x86_64-aws.x86_64", "Format": "vmdk", "UserBucket": { "S3Bucket": "${VMIMPORT_BUCKET_NAME}", "S3Key": "rhcos- "Description": "rhcos-4.7.0-x86_64-aws.x86_64", "DiskImageSize": 819056640.0, "Format": "VMDK", "SnapshotId": "snap-06331325870076318", "Status": "completed" 3 filesystems: - device: /dev/disk/by-partlabel/var path: /var format: xfs systemd: units: - name: var.mount 4 enabled: true contents:

Manager (OLM) 所支持的 Operator 打包格式。 2.2.1. 捆绑包格式 Operator 的 Bundle Format 是 Operator Framework 引入的新打包格式。为提高可伸缩性并为自行托管 目录的上游用户提供更好地支持，Bundle Format 规格简化了 Operator 元数据的发布。 Operator 捆绑包代表 Operator 的单一版本。磁盘上的捆绑 Framework 术语 2.3.1.1. 捆绑包（ 包（Bundle） ） 在 Bundle Format 中，捆绑包是 Operator CSV、清单和元数据的集合。它们一起构成了可在集群中安装 的 Operator 的唯一版本。 2.3.1.2. 捆绑包 包镜像 像 在 Bundle Format 中， 捆绑包镜像是一个从 Operator 清单中构建的容器镜像，其中包含一个捆绑包。捆 绑包镜像由 的所有指定版本来解决依赖关系。通过在目 录中查找并安装满足所需 CRD API 且与软件包或捆绑包不相关的 Operator，解决这个依赖关系。 2.3.1.8. 索引 索引镜像 像 在 Bundle Format 中， 索引镜像是一种数据库（数据库快照）镜像，其中包含关于 Operator 捆绑包（包 括所有版本的 CSV 和 CRD）的信息。此索引可以托管集群中 Operator 的历史记录，并可使用

$ cat < containers.json { "Description": "rhcos-${RHCOS_VERSION}-x86_64-aws.x86_64", "Format": "vmdk", "UserBucket": { "S3Bucket": "${VMIMPORT_BUCKET_NAME}", "S3Key": "rhcos- "Description": "rhcos-4.7.0-x86_64-aws.x86_64", "DiskImageSize": 819056640.0, "Format": "VMDK", "SnapshotId": "snap-06331325870076318", "Status": "completed" 3 filesystems: - device: /dev/disk/by-partlabel/var path: /var format: xfs mount_options: [defaults, prjquota] 4 with_mount_unit: true 第 第 4 章 章 在 在 AWS 上安装

$ cat < containers.json { "Description": "rhcos-${RHCOS_VERSION}-x86_64-aws.x86_64", "Format": "vmdk", "UserBucket": { "S3Bucket": "${VMIMPORT_BUCKET_NAME}", "S3Key": "rhcos- "Description": "rhcos-4.7.0-x86_64-aws.x86_64", "DiskImageSize": 819056640.0, "Format": "VMDK", "SnapshotId": "snap-06331325870076318", "Status": "completed" $ cat < containers.json { "Description": "rhcos-${RHCOS_VERSION}-x86_64-aws.x86_64", "Format": "vmdk", "UserBucket": { "S3Bucket": "${VMIMPORT_BUCKET_NAME}", "S3Key": "rhcos-

$ cat < containers.json { "Description": "rhcos-${RHCOS_VERSION}-x86_64-aws.x86_64", "Format": "vmdk", "UserBucket": { "S3Bucket": "${VMIMPORT_BUCKET_NAME}", "S3Key": "rhcos- "Description": "rhcos-4.7.0-x86_64-aws.x86_64", "DiskImageSize": 819056640.0, "Format": "VMDK", "SnapshotId": "snap-06331325870076318", "Status": "completed" $ cat < containers.json { "Description": "rhcos-${RHCOS_VERSION}-x86_64-aws.x86_64", "Format": "vmdk", "UserBucket": { "S3Bucket": "${VMIMPORT_BUCKET_NAME}", "S3Key": "rhcos-

如需更多信息，请参阅 Operator Lifecycle Manager 依赖项。 1.2.11.2. Operator 捆绑 捆绑包中支持的其他 包中支持的其他对 对象 象 Operator Bundle Format 现在支持以下额外 Kubernetes 对象： spec: logLevel: Normal operatorLogLevel: Normal 第 第 1 章 章 OPENSHIFT CONTAINER OpenShift Container Platform 次要版本的索引镜像提供。这允许 Operator 供应商针对每个集群版本发布 Operator 版本。 这些索引镜像基于 Bundle Format，用于替换基于已弃用的软件包清单格式的 App Registry 目录镜像（这 些镜像针对 OpenShift Container Platform 4 的早期版本发布）。OpenShift Container 注意 注意 虽然红帽不会为 OpenShift Container Platform 4.6 及之后的版本发布 App Registry 目录 镜像，但基于 Package Manifest Format 的自定义目录镜像仍被支持。 如需有关捆绑格式和索引镜像的更多信息，请参阅 Operator Framework 打包格式。 重要的 重要的 Operator 升 升级 级要求 要求 集群管理员必须确保之前通过

$ cat < containers.json { "Description": "rhcos-${RHCOS_VERSION}-x86_64-aws.x86_64", "Format": "vmdk", "UserBucket": { "S3Bucket": "${VMIMPORT_BUCKET_NAME}", "S3Key": "rhcos- "Description": "rhcos-4.7.0-x86_64-aws.x86_64", "DiskImageSize": 819056640.0, "Format": "VMDK", "SnapshotId": "snap-06331325870076318", "Status": "completed" $ cat < containers.json { "Description": "rhcos-${RHCOS_VERSION}-x86_64-aws.x86_64", "Format": "vmdk", "UserBucket": { "S3Bucket": "${VMIMPORT_BUCKET_NAME}", "S3Key": "rhcos-