-
Notifications
You must be signed in to change notification settings - Fork 164
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
Release 1.0.0 #227
Release 1.0.0 #227
Conversation
4debef2
to
d1335df
Compare
Let's also add the ability to deploy the config as a |
And have the credentials passed as environment variables backed by secrets? That would be quite optimal. |
- name: MEMCACHED_CACHE_SIZE | ||
value: "1024" |
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.
This needs to correspond to the memory requests and limits. It shouldn't just arbitrarily be 1024
MB. It would be better to document how to do this than to hardcode it.
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.
Yep it should also match with stuff like..
# CLI flag: -blocks-storage.bucket-store.index-cache.memcached.max-item-size
[max_item_size: <int> | default = 1048576]
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.
The CACHE_SIZE
contains all the items, so it does not directly relate to max_item_size
, other than having to be bigger than it to fit at least one item.
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.
I've actually had a lot of issues figuring out which components of Cortex require what item sizes in the different caches. It'd be great if the Cortex documentation offered more clarity on what the max size an item could be, like an index, some metadata, or a block even.
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.
The
CACHE_SIZE
contains all the items, so it does not directly relate tomax_item_size
, other than having to be bigger than it to fit at least one item.
Yep u right. Leaving this here for future reference: https://github.com/bitnami/bitnami-docker-memcached/blob/master/1/debian-10/rootfs/opt/bitnami/scripts/memcached/run.sh
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.
I documented the helm values but we should have a Best-Practice wiki page on how to configure memcached properly with some (preferably) production experience. Doesn't have to be in this PR though
Any ETA on 1.0.0 release? Is it possible to tag the current master? We have some fixes on the Memcache chart that we want to apply to our workload. |
@ShuzZzle, I'd recommend breaking up this PR so that it only contains the breaking changes. Before it's ready, we can release a minor version with non-breaking updates and new features. Edit: never mind, I see this PR is already only the breaking changes. @lahsivjar comment threw me off because it's out of context. Sounds like they are requesting a minor version release (nothing to do with this PR). |
The same memcache fixxes in this PR or something similar? |
@kd7lxl @ShuzZzle Sorry for the confusion. I was not referring to this specific PR but releasing the current master with a minor tag. I need the changes done in liveliness probes in Memcached chart version 5.15.1. Should have opened a separate thread 😅 |
Sounds great, please do before we release a "buggy" version |
ddd930a
to
9f84719
Compare
bafd8a7
to
cb48943
Compare
{{- if .Values.ingress.ingressClass.enabled }} | ||
ingressClassName: {{ .Values.ingress.ingressClass.name }} | ||
{{- end }} |
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.
The helm-boilerplate way of doing this (as close as we get to standards) is:
https://github.com/helm/helm/blob/d4cc130fa90027e8c1c69ad2a06c6dee4c31d29d/pkg/chartutil/create.go#L240-L242
Signed-off-by: ShuzZzle <niclas.schad@gmail.com>
Signed-off-by: ShuzZzle <niclas.schad@gmail.com>
…rride Signed-off-by: ShuzZzle <niclas.schad@gmail.com>
Signed-off-by: ShuzZzle <niclas.schad@gmail.com>
Signed-off-by: ShuzZzle <niclas.schad@gmail.com>
Signed-off-by: ShuzZzle <niclas.schad@gmail.com>
Signed-off-by: ShuzZzle <niclas.schad@gmail.com>
Signed-off-by: ShuzZzle <niclas.schad@gmail.com>
Signed-off-by: ShuzZzle <niclas.schad@gmail.com>
Signed-off-by: ShuzZzle <niclas.schad@gmail.com>
Signed-off-by: ShuzZzle <niclas.schad@gmail.com>
Signed-off-by: ShuzZzle <niclas.schad@gmail.com>
Signed-off-by: ShuzZzle <niclas.schad@gmail.com>
Signed-off-by: ShuzZzle <niclas.schad@gmail.com>
Signed-off-by: ShuzZzle <niclas.schad@gmail.com>
Signed-off-by: ShuzZzle <niclas.schad@gmail.com>
Signed-off-by: ShuzZzle <niclas.schad@gmail.com>
Signed-off-by: ShuzZzle <niclas.schad@gmail.com>
Signed-off-by: ShuzZzle <niclas.schad@gmail.com>
Signed-off-by: ShuzZzle <niclas.schad@gmail.com>
2f13cfd
to
6d7eefc
Compare
Signed-off-by: ShuzZzle <niclas.schad@gmail.com>
592fc6e
to
1f1160e
Compare
Signed-off-by: ShuzZzle <niclas.schad@gmail.com>
Signed-off-by: ShuzZzle <niclas.schad@gmail.com>
Signed-off-by: ShuzZzle <niclas.schad@gmail.com>
Release 1.0.0
nginx.serviceMonitor
sectionWhich issue(s) this PR fixes:
Fixes #202, #252
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]