Skip to content
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

Reduce Excessive Resync #324

Merged
merged 2 commits into from
Oct 8, 2020
Merged

Conversation

dvaldivia
Copy link
Collaborator

Reduces the amount of resync caused by updateTenantStatus. If we attempt to update a status that is already in the tenant we simply don't to avoid re-queueing the tenant being processed.

Also re-adds the state printer columns that we use to have in v2 of operator.

Screen Shot 2020-10-08 at 1 52 53 PM

Reduces the amount of resync caused by updateTenantStatus. If we attempt to update a status that is already in the tenant we simply don't to avoid re-queueing the tenant being processed.

Also re-adds the state printer columns that we use to have in v2 of operator.
@harshavardhana harshavardhana merged commit bbf89de into minio:master Oct 8, 2020
jmontleon added a commit to jmontleon/operator that referenced this pull request Jul 23, 2024
I am not certain about this one. Can others weigh in:

```
features.operators.openshift.io/proxy-aware

Specify whether an Operator supports running on a cluster behind a proxy by accepting the standard HTTP_PROXY and HTTPS_PROXY proxy environment variables. If applicable, the Operator passes this information to the workload it manages (operands).
```

Signed-off-by: Jason Montleon <jmontleo@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants