-
Notifications
You must be signed in to change notification settings - Fork 26
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
Enable caching using memcached #184
Enable caching using memcached #184
Conversation
We have to wait until openstack-k8s-operators/lib-common#298 is merged ... |
/test heat-operator-build-deploy-kuttl |
1 similar comment
/test heat-operator-build-deploy-kuttl |
/test heat-operator-build-deploy-kuttl |
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would you mind updating the README with a note about this being required? We probably need some kind of automation to update the samples I used in the README. They're probably all outdated now anyway.
https://github.com/openstack-k8s-operators/heat-operator/blob/main/README.md
This introduces the capability to use memcached as cache backend, to reproduce the setting in TripleO. Enabling caching in heat provides large performance benefit in token validation and some resource queries.
Good catch. I've updated README. |
/test heat-operator-build-deploy-kuttl |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bshephar, kajinamit The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
b3dea63
into
openstack-k8s-operators:main
This introduces the capability to use memcached as cache backend, to reproduce the setting in TripleO.
Enabling caching in heat provides large performance benefit in token validation and some resource queries.