-
Notifications
You must be signed in to change notification settings - Fork 160
OCPBUGS-15366: [release-4.13] OCPBUGS-15365: operator: use a partial metadata watch for Namespaces #548
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
Conversation
We only watch namespaces to react to their creation, and the only information we need about a namespace is its' name, so we can use a partial metadata watch to winnow down the size of our cache. Namespaces don't really store much in spec and status, so this effect is likely to not be enormous, but every bit helps. Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
|
@openshift-cherrypick-robot: An error was encountered cloning bug for cherrypick for bug PORTENABLE-526 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details. Full error message.
request failed. Please analyze the request body for more details. Status code: 400: {"errorMessages":[],"errors":{"customfield_12318341":"Operation value must be a string"}}
Please contact an administrator to resolve this issue, then request a bug refresh with DetailsIn 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. |
|
/jira cherrypick PORTENABLE-526 |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## release-4.13 #548 +/- ##
================================================
- Coverage 47.63% 47.60% -0.03%
================================================
Files 94 94
Lines 10113 10118 +5
================================================
Hits 4817 4817
- Misses 4721 4726 +5
Partials 575 575
|
|
/jira cherrypick PORTENABLE-528 |
1 similar comment
|
/jira cherrypick PORTENABLE-528 |
|
/retitle [release-4.13] OCPBUGS-15365: operator: use a partial metadata watch for Namespaces |
|
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-15365, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn 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. |
|
/jira cherrypick OCPBUGS-15365 |
|
@stevekuznetsov: Detected clone of Jira Issue OCPBUGS-15365 with correct target version. Will retitle the PR to link to the clone. DetailsIn 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. |
|
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-15366, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn 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. |
|
/jira refresh |
|
@stevekuznetsov: This pull request references Jira Issue OCPBUGS-15366, which is invalid:
Comment DetailsIn 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. |
|
/approve |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abutcher, openshift-cherrypick-robot The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@openshift-cherrypick-robot: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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 understand the commands that are listed here. |
|
/jira refresh |
|
@sjenning: This pull request references Jira Issue OCPBUGS-15366, which is valid. The bug has been moved to the POST state. 6 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn 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. |
|
Had a test with OCP-65165 based on this PR and #551, seems need to port part of codes in #563 too. jianpingshu@jshu-mac ~ % kubectl top pods -n openshift-cloud-credential-operator
NAME CPU(cores) MEMORY(bytes)
cloud-credential-operator-79fcdb7895-b9zcw 0m 134Mi
pod-identity-webhook-5f9fb46597-87w89 0m 10Mi
pod-identity-webhook-5f9fb46597-s67pn 0m 10MiCreated 100 configmap, ok jianpingshu@jshu-mac ~ % kubectl top pods -n openshift-cloud-credential-operator
NAME CPU(cores) MEMORY(bytes)
cloud-credential-operator-79fcdb7895-b9zcw 1m 132Mi
pod-identity-webhook-5f9fb46597-87w89 0m 10Mi
pod-identity-webhook-5f9fb46597-s67pn 0m 10MiCreated 100 secrets, memory increased obviously jianpingshu@jshu-mac ~ % kubectl top pods -n openshift-cloud-credential-operator
NAME CPU(cores) MEMORY(bytes)
cloud-credential-operator-79fcdb7895-b9zcw 1m 273Mi
pod-identity-webhook-5f9fb46597-87w89 0m 11Mi
pod-identity-webhook-5f9fb46597-s67pn 0m 10Mi |
|
@jianping-shu yes, thank you for the test. I think there's some lack of clarity about whether or not we're going to finish the backport here or not , it depends on some large PRs... |
|
@stevekuznetsov Got it! I think we can hold temporarily to wait 4.14 cco is more stable and direction got clearer. |
|
@jianping-shu makes perfect sense to me |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
|
/close |
|
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-15366. The bug has been updated to no longer refer to the pull request using the external bug tracker. DetailsIn 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. |
|
@stevekuznetsov: Closed this PR. DetailsIn 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. |
This is an automated cherry-pick of #546
/assign stevekuznetsov