-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
What Is the Meaning of "Updating CRD OpenAPI spec because xxx changed" in the apiserver Log? #124611
Comments
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
/sig api-machinery |
/remove-kind feature |
The principle has been figured out. After the CRD is created, the APIServer updates the cached log records after the change. |
@kangzhiqin We are also seeing this also but still don't understand why... The CRDs haven't changed? Or at least not to my knowledge so confused why we see hundreds of log lines every 5 mins that strikes me as kube-apiserver doing lots of work with the OpenAPI Spec that it doesn't need too? |
When the CRD informer is created, the full synchronization mechanism is set to be performed every 5 minutes. The log is the evidence of full synchronization. I want you to focus on line 175 here. kubernetes/staging/src/k8s.io/apiextensions-apiserver/pkg/apiserver/apiserver.go Lines 162 to 185 in 5bf1e95
|
What would you like to be added?
The apiserver prints a crd update log every 5 minutes. What does this mean? What is the triggering process?
Why is this needed?
kubernetes/staging/src/k8s.io/apiextensions-apiserver/pkg/controller/openapi/controller.go
Line 228 in bac1a0c
The text was updated successfully, but these errors were encountered: