Skip to content

Conversation

@horis233
Copy link
Contributor

@horis233 horis233 commented Feb 23, 2022

In order to make bindinfo adopters get the secret update immediately when the original secret is updated, we will add an opt-in mechanism into ODLM the bindinfo controller.

When the target deployments/stateful sets/daemonsets have specific labels,

operator.ibm.com/bindinfoRefresh: enabled

And add resource information into the annotation

bindinfoRefresh/secret: "<secretName1>,<secretName2>"
bindinfoRefresh/configmap: "<configmap1>"

ODLM will rolling update them to refresh their pods when the bindinfo is updated.

An annotation bindinfo/restartTime: will be inserted/updated in the deployments/statefulsets/daemonsets to trigger the rolling update.

Also, we leverage cache filter to optimize the memory usage

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

  1. Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:


In order to make bindinfo adopters get the secret update immediately when the original secret is updated, we will add an opt-in mechanism into ODLM the bindinfo controller.

When the target deployments/stateful sets/daemonsets have specific labels,

```
operator.ibm.com/bindinfoRefresh: enabled
```

And add resource information into the annotation

```
bindinfoRefresh/secret: "<secretName1>,<secretName2>"
bindinfoRefresh/configmap: "<configmap1>"
```

ODLM will rolling update them to refresh their pods when the bindinfo is updated.

An annotation bindinfo/restartTime: <time> will be inserted/updated in the deployments/statefulsets/daemonsets to trigger the rolling update.

Also, we leverage cache filter to optimize the memory usage
@horis233
Copy link
Contributor Author

/retest

Copy link
Contributor

@Daniel-Fan Daniel-Fan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@ibm-ci-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Daniel-Fan, horis233

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:
  • OWNERS [Daniel-Fan,horis233]

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

@ibm-ci-bot ibm-ci-bot merged commit 1f05a1c into IBM:master Feb 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants