检测到您已登录华为云国际站账号,为了您更好的体验,建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
Service,简称CTS)为您提供云服务资源的操作记录,记录内容包括您从云管理控制台或者开放API发起的云服务资源操作请求以及每次请求的结果,供您查询、审计和回溯使用。 表1 云审计服务支持的CCI操作列表 操作名称 事件名称 创建一个Service对象 createService 删除一个Service对象
service: name: custom-metrics-apiserver namespace: monitoring port: 443 version: v1beta1 versionPriority: 100 可以将该对象保存为文件,命名为metrics-apiservice
源不会立即停止服务,资源进入宽限期。您需支付按需资源在宽限期内产生的费用,相关费用可在“管理控制台 > 费用中心 > 总览”的“欠费金额”查看,华为云将在您充值时自动扣取欠费金额。 如果您在宽限期内仍未支付欠款,那么就会进入保留期,资源状态变为“已冻结”,您将无法对处于保留期的按需计费资源执行任何操作。
Deployment 查询用户所有Deployments 删除指定namespace下Deployments 查询指定namespace下的Deployments 创建Deployment 删除Deployment 查询Deployment 更新Deployment 替换Deployment
日志采集:支持根据您配置的日志输出路径,采集应用日志,请自行防爆处理。单击添加日志存储,输入容器内日志路径,调整日志存储空间。负载创建完成后,可在AOM界面查看日志,具体请参见日志管理。 环境变量:在容器中设置环境变量,支持手动输入和引用变量。环境变量为应用提供极大的灵活性,您可以在应用程序中使用
Pod 删除指定namespace下的Pods 查询指定namespace下的Pods 创建Pod 删除Pod 查询Pod 更新Pod 替换Pod 进入容器执行命令 进入容器执行命令 查询Pod日志 查询Pod状态 查询用户所有的Pods 父主题: Kubernetes API
supports a single TLS port, 443. If multiple members of this list specify different hosts, they will be multiplexed on the same port according to the
当弹性到CCI的资源调度失败时,bursting节点会被锁定半小时,期间无法调度至CCI。用户可通过CCE集群控制台,使用kubectl工具查看bursting节点状态,若节点被锁定,可手动解锁bursting。 调度策略 CCE集群工作负载弹性调度到CCI策略有如下三种: 调度策略
删除指定namespace下的StatefulSets 查询指定namespace下的StatefulSets 创建StatefulSet 删除StatefulSet 查询StatefulSet 更新StatefulSet 替换StatefulSet 查询StatefulSet状态 查询用户所有的StatefulSets
Job 查询用户所有的Jobs 删除指定namespace下的Jobs 查询指定namespace下的Jobs 创建Job 删除Job 查询Job 更新Job 替换Job 查询Job状态 父主题: Kubernetes API
Network 删除指定namespace下的Networks 查询指定namespace下的Networks 创建Network 删除Network 查询Network 查询Network状态 父主题: API
primarily informational. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default "0.0
primarily informational. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default "0.0
primarily informational. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default "0.0
primarily informational. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default "0.0
primarily informational. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default "0.0
primarily informational. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default "0.0
primarily informational. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default "0.0
primarily informational. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default "0.0
primarily informational. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default "0.0