@phsiao: Reiterating the mentions to trigger a notification:
@kubernetes/sig-cli-bugs
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.![]()
@kubernetes/sig-cli-bugs
@phsiao: Reiterating the mentions to trigger a notification:
@kubernetes/sig-cli-bugs
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
—
To summarize, I think the issue is 1.8.2 client (likely 1.8.x and 1.7.x from the reports) can't delete a statefulset in 1.9.2 (likely starting from at least 1.9.1 from the report), and it generates
Error in request: no kind "GetOptions" is registered for version "apps/v1"
back to the user in CLI.
Using this yaml to reproduce, no error in controller-manager log.
I upgraded my kubernetes-cli to 1.9.3 and statefulset deletion worked fine with no issues.
It seems to be the incompatibility issue in client 1.8.2
I can also confirm that upgrading kubectl to 1.9.3 can help to delete the statefulset. But the error message remains.
Had this issue as well with 1.7.4. Upgrading to 1.9.3 eliminated the problem and the error message.
I can confirm that upgrading kubectl from 1.7.4 to 1.9.3 helped
I'm using gcloud provided kubectl version with GKE and sill facing the issue.
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.6", GitCommit:"6260bb08c46c31eea6cb538b34a9ceb3e406689c", GitTreeState:"clean", BuildDate:"2017-12-21T06:34:11Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9+", GitVersion:"v1.9.2-gke.1", GitCommit:"4ce7af72d8d343ea2f7680348852db641ff573af", GitTreeState:"clean", BuildDate:"2018-01-31T22:30:55Z", GoVersion:"go1.9.2b4", Compiler:"gc", Platform:"linux/amd64"}
$ which kubectl
....google-cloud-sdk/bin/kubectl
$ gcloud version
Google Cloud SDK 189.0.0
alpha 2017.09.15
beta 2017.09.15
bq 2.0.29
core 2018.02.12
gcloud
gsutil 4.28
kubectl
$ kubectl delete statefulset foo -v=4
I0217 06:52:26.732817 13294 request.go:606] Error in request: no kind "GetOptions" is registered for version "apps/v1"
F0217 06:52:26.733069 13294 helpers.go:120] error: no kind "GetOptions" is registered for version "apps/v1"
I can confirm that moving to 1.9.3 also works.
In our case we had to update the SDK docker container google/cloud-sdk:latest as we was using an older version. Latest version contains 1.9.3 client version and deletes the statefulsets correctly.
any one reported that we need an update to gcloud components to package the latest version? can't find any ticket
latest version is 1.8.6 in the sdk.
Anyone know where I can open a request to ask gcloud make kubectl 1.9.x available via gcloud components update?
@dhurley14 - I've asked google the same question using our support account. Will update this thread if there is anything worth sharing.
I solved by deleting it from the dashboard instead of using the CLI.
@vishwaspai Did google respond to you? I'm having the same issue. @wilk are you aware of any other way to delete the statefulset? We're not using the kubernetes dashboard.
@vishwaspai that's unfortunate.. thanks for the update. That's what I ended up doing was just doing brew install kubectl and uninstalling the command installed by gcloud. Thanks.
Probably linked to this problem: I tried to solve it using your tips (delete from kubectl 1.9x, dashboard delete...) but now some of my pods are stuck in terminating status. Does anyone faced this problem afterwards?
Had the same issue on 1.9.6, but updated my kubectl version and everything works now!
I have encountered this issue trying to delete a StatefulSet in 1.8 cluster (kops@AWS) using kubectl 1.10.2. Downgrading kubectl to 1.9.7 fixed the issue.
Same issue using kubectl 1.10.0 and 1.10.1 trying to delete a StatefulSet in 1.8.8-gke.0. Running with kubectl 1.8.6 worked.
/area stateful
reproducible with:
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.1", GitCommit:"d4ab47518836c750f9949b9e0d387f20fb92260b", GitTreeState:"clean", BuildDate:"2018-04-13T22:27:55Z", GoVersion:"go1.9.5", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.7", GitCommit:"b30876a5539f09684ff9fde266fda10b37738c9c", GitTreeState:"clean", BuildDate:"2018-01-16T21:52:38Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Reproduced:
IBMMasterMBP:~ bjxzi$ kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-27T00:13:02Z", GoVersion:"go1.9.4", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"8+", GitVersion:"v1.8.11-2+fa6873d3e386d7", GitCommit:"fa6873d3e386d7ead42923b24aea3b76e74395a3", GitTreeState:"clean", BuildDate:"2018-04-17T08:10:40Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
IBMMasterMBP:~ bjxzi$ kubectl delete sts api -n default --force -v=9
I0508 16:27:50.701625 8176 loader.go:357] Config loaded from file /Users/bjxzi/.bluemix/plugins/container-service/clusters/bcf-develop/kube-config-dal10-bcf-develop.yml
I0508 16:27:50.714521 8176 round_trippers.go:386] curl -k -v -XGET -H "Accept: application/json, */*" -H "User-Agent: kubectl/v1.10.0 (darwin/amd64) kubernetes/fc32d2f" https://169.46.7.238:28641/apis/apps/v1/namespaces/default/statefulsets/api
I0508 16:27:51.715543 8176 round_trippers.go:405] GET https://169.46.7.238:28641/apis/apps/v1/namespaces/default/statefulsets/api 404 Not Found in 1001 milliseconds
I0508 16:27:51.715580 8176 round_trippers.go:411] Response Headers:
I0508 16:27:51.715592 8176 round_trippers.go:414] Content-Type: application/json
I0508 16:27:51.715602 8176 round_trippers.go:414] Content-Length: 174
I0508 16:27:51.715611 8176 round_trippers.go:414] Date: Tue, 08 May 2018 08:27:51 GMT
I0508 16:27:51.715660 8176 request.go:874] Response Body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the server could not find the requested resource","reason":"NotFound","details":{},"code":404}
I0508 16:27:51.716699 8176 helpers.go:201] server response object: [{
"metadata": {},
"status": "Failure",
"message": "the server could not find the requested resource",
"reason": "NotFound",
"details": {},
"code": 404
}]
F0508 16:27:51.716733 8176 helpers.go:119] Error from server (NotFound): the server could not find the requested resource
This issue is similar to kubernetes/kubectl#426
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Any update on this issue? Seems to happen with v1.9.7. Is there a list of versions that work or fully delete the sts?
Seems more like an api issue then sig apps
/sig api-machinery
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
Was also hitting this problem. Upgraded my kubectl version to 1.12 and it worked. Was on 1.8 with cluster on 1.10
/close
kubectl supports skew of 1 version against the apiserver. in 1.10, it started making use of the apps/v1 API objects added in 1.9. Running commands related to apps objects (like statefulsets) against a 1.8-era API server will result in 404 errors, because the apps/v1 API does not exist in 1.8
Closed #59867.
@liggitt: Closing this issue.
In response to this:
/close
kubectl supports skew of 1 version against the apiserver. in 1.10, it started making use of the apps/v1 API objects added in 1.9. Running commands related to apps objects (like statefulsets) against a 1.8-era API server will result in 404 errors, because the apps/v1 API does not exist in 1.8
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
I have upgrade to 1.13.0 form 8, and able to delete statefulset.
kubectl delete statefulsets
I hit the same issue because of uncoptability between kubectl and kube-apiserver .. with newer version of kubectl works. e.g.
Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.4", GitCommit:"9befc2b8928a9426501d3bf62f72849d5cbcd5a3", GitTreeState:"clean", BuildDate:"2017-11-20T05:28:34Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.10", GitCommit:"8f5e38f04b88241facc4969a16b244e11085a626", GitTreeState:"clean", BuildDate:"2019-08-21T09:56:18Z", GoVersion:"go1.11.13", Compiler:"gc", Platform:"linux/amd64"}
vs
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.3", GitCommit:"2d3c76f9091b6bec110a5e63777c332469e0cba2", GitTreeState:"clean", BuildDate:"2019-08-19T11:13:54Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.10", GitCommit:"8f5e38f04b88241facc4969a16b244e11085a626", GitTreeState:"clean", BuildDate:"2019-08-21T09:56:18Z", GoVersion:"go1.11.13", Compiler:"gc", Platform:"linux/amd64"}