Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #546

/assign stevekuznetsov

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-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jun 23, 2023

@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 /jira refresh.

Details

In response to this:

This is an automated cherry-pick of #546

/assign stevekuznetsov

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
Copy link
Contributor

stevekuznetsov commented Jun 23, 2023

/jira cherrypick PORTENABLE-526

@codecov
Copy link

codecov bot commented Jun 23, 2023

Codecov Report

Merging #548 (1d6d6ff) into release-4.13 (0621fca) will decrease coverage by 0.03%.
The diff coverage is 0.00%.

Additional details and impacted files

Impacted file tree graph

@@               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              
Impacted Files Coverage Δ
...redentialsrequest/credentialsrequest_controller.go 53.53% <0.00%> (-0.55%) ⬇️

@stevekuznetsov
Copy link
Contributor

stevekuznetsov commented Jun 23, 2023

/jira cherrypick PORTENABLE-528

1 similar comment
@stevekuznetsov
Copy link
Contributor

stevekuznetsov commented Jun 23, 2023

/jira cherrypick PORTENABLE-528

@stevekuznetsov
Copy link
Contributor

/retitle [release-4.13] OCPBUGS-15365: operator: use a partial metadata watch for Namespaces

@openshift-ci openshift-ci bot changed the title [release-4.13] PORTENABLE-526: operator: use a partial metadata watch for Namespaces [release-4.13] OCPBUGS-15365: operator: use a partial metadata watch for Namespaces Jun 23, 2023
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 23, 2023
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-15365, which is invalid:

  • expected Jira Issue OCPBUGS-15365 to depend on a bug targeting a version in 4.14.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is an automated cherry-pick of #546

/assign stevekuznetsov

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
Copy link
Contributor

/jira cherrypick OCPBUGS-15365

@openshift-ci-robot
Copy link
Contributor

@stevekuznetsov: Detected clone of Jira Issue OCPBUGS-15365 with correct target version. Will retitle the PR to link to the clone.
/retitle OCPBUGS-15366: [release-4.13] OCPBUGS-15365: operator: use a partial metadata watch for Namespaces

Details

In response to this:

/jira cherrypick OCPBUGS-15365

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-ci openshift-ci bot changed the title [release-4.13] OCPBUGS-15365: operator: use a partial metadata watch for Namespaces OCPBUGS-15366: [release-4.13] OCPBUGS-15365: operator: use a partial metadata watch for Namespaces Jun 23, 2023
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-15366, which is invalid:

  • expected dependent Jira Issue OCPBUGS-15365 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is New instead
  • expected dependent Jira Issue OCPBUGS-15365 to target a version in 4.14.0, but it targets "4.13.z" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is an automated cherry-pick of #546

/assign stevekuznetsov

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
Copy link
Contributor

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@stevekuznetsov: This pull request references Jira Issue OCPBUGS-15366, which is invalid:

  • expected dependent Jira Issue OCPBUGS-15365 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is New instead
  • expected dependent Jira Issue OCPBUGS-15365 to target a version in 4.14.0, but it targets "4.14" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

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.

@abutcher
Copy link
Member

/approve
/label backport-risk-assessed

@openshift-ci openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jun 23, 2023
@abutcher
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 23, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 23, 2023

[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

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 11, 2023

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

Details

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 understand the commands that are listed here.

@sjenning
Copy link
Contributor

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 19, 2023
@openshift-ci-robot
Copy link
Contributor

@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
  • bug is open, matching expected state (open)
  • bug target version (4.13.z) matches configured target version for branch (4.13.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-15365 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
  • dependent Jira Issue OCPBUGS-15365 targets the "4.14.0" version, which is one of the valid target versions: 4.14.0
  • bug has dependents

Requesting review from QA contact:
/cc @jianping-shu

Details

In response to this:

/jira refresh

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-ci openshift-ci bot requested a review from jianping-shu July 19, 2023 13:12
@jianping-shu
Copy link

jianping-shu commented Jul 25, 2023

Had a test with OCP-65165 based on this PR and #551, seems need to port part of codes in #563 too.
After cluster install.

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           10Mi

Created 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           10Mi

Created 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

@stevekuznetsov
Copy link
Contributor

@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...

@jianping-shu
Copy link

@stevekuznetsov Got it! I think we can hold temporarily to wait 4.14 cco is more stable and direction got clearer.

@stevekuznetsov
Copy link
Contributor

@jianping-shu makes perfect sense to me

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 25, 2023
@stevekuznetsov
Copy link
Contributor

/close

@openshift-ci openshift-ci bot closed this Oct 25, 2023
@openshift-ci-robot
Copy link
Contributor

@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.

Details

In response to this:

This is an automated cherry-pick of #546

/assign stevekuznetsov

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-ci
Copy link
Contributor

openshift-ci bot commented Oct 25, 2023

@stevekuznetsov: Closed this PR.

Details

In response to this:

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants