-
创建EndpointcreateCoreV1NamespacedEndpoints
(SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after
来自：百科 -
替换EIPPoolreplaceCrdYangtseCniV1NamespacedEIPPool
(SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after
来自：百科 -
查询ConfigMapreadCoreV1NamespacedConfigMap
(SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after
来自：百科 -
查询Deployment的伸缩操作readAppsV1NamespacedDeploymentScale
(SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after
来自：百科 -
删除NetworkdeleteNetworkingCciIoV1beta1NamespacedNetwork
![]()
(SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after
来自：百科 -
替换VolcanoJobreplaceBatchVolcanoShV1alpha1NamespacedJob
![]()
(SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after
来自：百科 -
查询指定的storageclassreadStorageV1StorageClass
![]()
(SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after
来自：百科 -
查询Network状态readNetworkingCciIoV1beta1NamespacedNetworkStatus
![]()
(SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after
来自：百科 -
更新ConfigMappatchCoreV1NamespacedConfigMap
![]()
(SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after
来自：百科 -
查询NetworkreadNetworkingCciIoV1beta1NamespacedNetwork
![]()
(SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after
来自：百科 -
查询NamespacereadCoreV1Namespace
![]()
(SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after
来自：百科 -
查询指定的ClusterRolereadRbacAuthorizationV1ClusterRole
![]()
(SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after
来自：百科 -
查询VolcanoJob详情readBatchVolcanoShV1alpha1NamespacedJob
![]()
(SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after
来自：百科 -
创建PersistentVolumeClaimcreateCoreV1NamespacedPersistentVolumeClaim
![]()
(SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after
来自：百科 -
替换PersistentVolumeClaimsreplaceCoreV1NamespacedPersistentVolumeClaim
![]()
(SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after
来自：百科 -
更新指定的RoleBindingpatchRbacAuthorizationV1NamespacedRoleBinding
![]()
(SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after
来自：百科 -
查询指定的resourcequotareadCoreV1NamespacedResourceQuota
![]()
(SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after
来自：百科 -
查询指定的EIPPoolreadCrdYangtseCniV1NamespacedEIPPool
![]()
(SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after
来自：百科 -
更新Deployment的伸缩操作patchAppsV1NamespacedDeploymentScale
![]()
(SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after
来自：百科 -
查询EndpointreadCoreV1NamespacedEndpoints
![]()
(SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after
来自：百科 -
云应用引擎有什么作用
![]()
此外，云应用引擎CAE旨在帮助企业和个人快速构建和部署应用程序。它提供了一种基于云端的应用程序开发和运行环境，可以大幅简化应用程序的开发和部署流程，使应用程序更易于管理和维护。 CAE通常包括开发工具、运行环境、应用程序托管和自动扩展功能。开发者可以使用CAE提供的开发工具快速搭建应用程序，并将其部署到CAE提供
来自：百科
