检测到您已登录华为云国际站账号,为了您更好的体验,建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
md#resources containers Array of io.k8s.metrics.pkg.apis.metrics.v1beta1.ContainerMetrics objects Metrics for all containers are collected within
to a container within a pod, this would take on a value like: "spec.containers{name}" (where "name" refers to the name of the container that triggered
删除namespace下的所有TFJob 功能介绍 删除命名空间下的所有TFJob。 URI DELETE /apis/kubeflow.org/v1/namespaces/{namespace}/tfjobs 表1 Path参数 参数 是否必选 描述 namespace Yes
whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is
删除指定namespace下的Volcano Jobs 功能介绍 删除命名空间下的所有Volcano Job。 调用方法 请参见如何调用API。 URI DELETE /apis/batch.volcano.sh/v1alpha1/namespaces/{namespace}/jobs
initialization containers belonging to the pod. Init containers are executed in order prior to containers being started. If any init container fails, the
to a container within a pod, this would take on a value like: "spec.containers{name}" (where "name" refers to the name of the container that triggered
查询指定namespace下的Networks 功能介绍 查询指定namespace下的所有Network对象。 调用方法 请参见如何调用API。 URI GET /apis/networking.cci.io/v1beta1/namespaces/{namespace}/networks
within the container at which the volume should be mounted. Must not contain ':'. volumeClaim io.k8s.api.core.v1.PersistentVolumeClaim object VolumeClaim
云审计服务支持的CCI操作列表 CCI通过云审计服务(Cloud Trace Service,简称CTS)为您提供云服务资源的操作记录,记录内容包括您从云管理控制台或者开放API发起的云服务资源操作请求以及每次请求的结果,供您查询、审计和回溯使用。 表1 云审计服务支持的CCI操作列表
whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is
whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is
删除namespace下的所有PyTorchJob 功能介绍 删除命名空间下的所有PyTorchJob。 URI DELETE /apis/kubeflow.org/v1/namespaces/{namespace}/pytorchjobs 表1 Path参数 参数 是否必选 描述
initialization containers belonging to the pod. Init containers are executed in order prior to containers being started. If any init container fails, the
job的pod已经执行完成的情况下,为什么依然有实例在挂卷等事件,并且事件信息是失败的? 问题现象: job的Pod已经执行完成的情况下,依然有实例在挂卷等事件,并且事件信息是失败的。 图1 问题截图 问题原因: 各种类型的Pod(Deployment/StatefulSet/J
md#resources containers Array of io.k8s.metrics.pkg.apis.metrics.v1beta1.ContainerMetrics objects Metrics for all containers are collected within
whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is
the network is available NetworkActive = "Active" // NetworkFailed means the network is not available NetworkFailed = "Failed" // NetworkTerminating
查询Deployment的伸缩操作 功能介绍 查询Deployment的伸缩操作 调用方法 请参见如何调用API。 URI GET /apis/apps/v1/namespaces/{namespace}/deployments/{name}/scale 表1 路径参数 参数 是否必选
application/merge-patch+json 在RFC7386协议的定义中,Merge Patch必须包含对一个资源对象的部分描述,即为JSON对象。该JSON对象被提交到服务端后与服务端的当前对象合并,即替换当前资源对象中的列表域,从而创建一个新的对象。 Strategic Merge Patch