-
Notifications
You must be signed in to change notification settings - Fork 39k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CRD age does not change from <invalid> as soon as it becomes Established #57042
Comments
/sig api-machinery |
@ncdc So what are the users of kubectl advised to do with regard to new CRDs and their resources? Define CRDs first, wait several seconds and then add resources? Or just add new CRDS and their resources, and in case of failure retry? I would like this advice to be documented somewhere.
By which command can I check this? |
I'm not sure what our guidance is beyond waiting. You could also programmatically poll/watch the CRD and wait for it to be established. cc @kubernetes/sig-api-machinery-misc for increased visibility & guidance
Here is a sample I just ran:
|
https://kubernetes.io/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/ does not document this, but should. PR welcome. |
And of course there is no connnection to Minikube, but it is like that by design on every cluster. |
For the docs: kubernetes/website#6660. |
/assign |
@ncdc I have the output of |
From what I'm reading, you'll see |
I experience that adding resources fails until the age becomes 0s. I mean while the age is |
Can you share the logs from the apiserver around the time of the failures? |
We might have a race-condition between the update of the Established condition (https://github.com/sttts/kubernetes/blob/1161561ee12eea5ba28eb5efa9b384ec732def0e/staging/src/k8s.io/apiextensions-apiserver/pkg/controller/status/naming_controller.go#L253) and the HTTP handler of the API server (same process) actually picking in up (through informers, https://github.com/sttts/kubernetes/blob/b5b62c68318be79a665257c260ea9f9bbb6d6318/staging/src/k8s.io/apiextensions-apiserver/pkg/apiserver/customresource_handler.go#L116). We could synchronize these two, but this won't help in HA setups either. |
@ncdc Here is the audit log See for example Do you want me to produce any other log? |
/reopen |
Facing the same issue on 1.9.1. CRD AGE never changed from Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.1", GitCommit:"3a1c9449a956b6026f075fa3134ff92f7d55f812", GitTreeState:"clean", BuildDate:"2018-01-04T11:52:23Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"} |
Looks like the real issue here is that CRD age does not change from Can someone update the PR title to reflect the same? Thanks! |
This is still pending. I'm going to explicitly unassign myself here, since it has the help-wanted label (and could use some help for the above). Will be involved in this though. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale The issue #65517 describes similar problem, so maybe one can be closed. |
I think the underlying issue should be the same, but let's keep it open until we confirm this. Removing help because we don't have explicit directions about solving this yet. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle rotten |
#69654 is tracking the established condition transition time Age: Supported versions of kubectl (1.12+) get display text from the server and do not have this issue. /close |
@liggitt: Closing this issue. 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. |
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
When deploying https://github.com/istio/istio/blob/master/install/kubernetes/istio.yaml on minikube, I get the following errors:
unable to recognize "install/kubernetes/istio.yaml": no matches for config.istio.io/, Kind=attributemanifest
for each of the custom resources specified in https://github.com/istio/istio/blob/master/install/kubernetes/istio.yaml
Running
kubernetes get crd
returns:After several seconds,
kubernetes get crd
returns valid age for the CRDs. Then the custom resources are added successfully.What you expected to happen:
I expect that it should be explicitly documented: can custom resources be added immediately after their CRDs? Or the user should wait until
kubernetes get crd
returns valid age.How to reproduce it (as minimally and precisely as possible):
Deploy https://github.com/istio/istio/blob/master/install/kubernetes/istio.yaml on a minikube with limited resources, so it will take time for the CRDs to become valid.
Anything else we need to know?:
Environment:
kubectl version
): 1.8.0uname -a
):The text was updated successfully, but these errors were encountered: