检测到您已登录华为云国际站账号,为了您更好的体验,建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
= 实例数 - 最大无效实例数)。 替换升级:先删除旧实例,再创建新实例。升级过程中业务会中断。 客户端DNS配置:负载支持替换域名解析配置和追加域名解析配置,参数设置请参见客户端DNS配置。 配置完成后,单击“下一步:规格确认”,单击“提交”,单击“返回无状态负载列表”。 在负
建的文件系统指定挂载参数。 挂载参数可设置mount命令指定文件系统挂载的选项,当前仅支持noac,即用于禁止本地的文件和目录缓存,支持客户端实时从远端SFS读取数据。 此处设置的挂载参数仅对当前命名空间下创建的文件存储卷有效。 图1 设置SFS挂载参数 使用文件存储卷 参照无状
sleep时长,保证旧的容器停止并退出之前,新的容器已经准备就绪。 配置完成后,对应用进行升级和弹性扩缩容的打流测试。 准备一台集群外的客户端节点,预置检测脚本detection_script.sh,内容如下,其中100.85.125.90:7552为service的公网访问地址:
第三方可以直接输入镜像地址,或单击“选择容器镜像”按钮,进入镜像列表,选择镜像。 我的镜像:展示了您上传到容器镜像服务的镜像。如果您想要在容器镜像服务中上传镜像,请参考客户端上传镜像或页面上传镜像。 如您是IAM用户,您需要参考(可选)上传镜像进行权限设置后才可使用账号的私有镜像。 镜像单层解压后的实际大小不能超过20G。
"generation" : 1, "labels" : { "app" : "mysql" }, "name" : "mysql", "namespace" : "default", "resourceVersion"
云审计服务支持的CCI操作列表 CCI通过云审计服务(Cloud Trace Service,简称CTS)为您提供云服务资源的操作记录,记录内容包括您从云管理控制台或者开放API发起的云服务资源操作请求以及每次请求的结果,供您查询、审计和回溯使用。 表1 云审计服务支持的CCI操作列表
stentVolumeClaims几种Volume类型,其中Projected和DownwardAPI类型仅bursting 1.3.25版本及以上支持。 EmptyDir:不支持子路径。 PersistentVolumeClaims:只支持SFS、SFS Turbo云存储类型,
什么是云容器实例? 云容器实例(Cloud Container Instance,CCI)服务提供 Serverless Container(无服务器容器)引擎,让您无需创建和管理服务器集群即可直接运行容器。 Serverless 是一种架构理念,是指不用创建和管理服务器、不用担
"system-node-critical" and "system-cluster-critical" are two special keywords which indicate the highest priorities with the former being the highest
"system-node-critical" and "system-cluster-critical" are two special keywords which indicate the highest priorities with the former being the highest
"system-node-critical" and "system-cluster-critical" are two special keywords which indicate the highest priorities with the former being the highest
"system-node-critical" and "system-cluster-critical" are two special keywords which indicate the highest priorities with the former being the highest
"system-node-critical" and "system-cluster-critical" are two special keywords which indicate the highest priorities with the former being the highest
"system-node-critical" and "system-cluster-critical" are two special keywords which indicate the highest priorities with the former being the highest
"system-node-critical" and "system-cluster-critical" are two special keywords which indicate the highest priorities with the former being the highest
underlying cloud-provider supports specifying the loadBalancerIP when a load balancer is created. This field will be ignored if the cloud-provider
"system-node-critical" and "system-cluster-critical" are two special keywords which indicate the highest priorities with the former being the highest
"system-node-critical" and "system-cluster-critical" are two special keywords which indicate the highest priorities with the former being the highest
"system-node-critical" and "system-cluster-critical" are two special keywords which indicate the highest priorities with the former being the highest
"system-node-critical" and "system-cluster-critical" are two special keywords which indicate the highest priorities with the former being the highest