Kubernetes 未能通过api删除rc?
kubernetes版本:1.02Kubernetes 未能通过api删除rc?,kubernetes,Kubernetes,kubernetes版本:1.02 RESTAPI 删除/api/v1/namespace/default/replicationcontroller/test 身体 失败 { "kind": "Status", "apiVersion": "v1", "metadata": {}, "status": "Failure", "message": "converting to : type names don't match (ReplicationController, DeleteOptio
RESTAPI
删除/api/v1/namespace/default/replicationcontroller/test
身体 失败
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Failure",
"message": "converting to : type names don't match (ReplicationController, DeleteOptions), and no conversion 'func (v1.ReplicationController, api.DeleteOptions) error' registered.",
"code": 500
}
如果设置正文为空,则删除成功,但pod存在。kubectl获取rc,rc已删除
kubectl收到吊舱,吊舱已离开 为什么?
如何通过api delete方法删除带有所有POD的rc?api请求设计为能够立即完成。收割/递归删除等任务通常由客户端通过组合多个API请求来处理。在这种情况下,您可以执行
kubectl
在运行kubectl delete rc/test
时所做的操作(您可以通过添加--v=8
看到这一点):
不要按api设置副本。无法通过api修补rc。
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Failure",
"message": "converting to : type names don't match (ReplicationController, DeleteOptions), and no conversion 'func (v1.ReplicationController, api.DeleteOptions) error' registered.",
"code": 500
}