-
Notifications
You must be signed in to change notification settings - Fork 535
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
Add ability to configure replicas for services #852
Conversation
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.
@martinjt looks great. Please update the README with the new values. Also, bump the chart's minor version and run make generate-examples CHARTS=opentelmetry-demo
Thanks @TylerHelmuth are there any other stateful services that I missed in the replicasOverride? |
I'd like @puckpuck opinion, buy maybe |
The Feature Flag service has a postgres database, so I figured that was ok, and I'd assumed the proxy wasn't stateful. |
What use case would someone set |
The idea is to scale up all the services at once, and make that easier for the scenario of just "we want more load". which makes it easier than adding an entry for each of them. Also when/if new components are added, they'll immediately get the replicas. |
Sorry, yes, this was in relation to the question about example charts
changing on every release. Want me to PR the removal?
…On Mon, 14 Aug 2023, 16:57 Tyler Helmuth, ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In strip-helm-chart-version.sh
<#852 (comment)>
:
> @@ -0,0 +1,3 @@
+#!/bin/sh
+
+sed '/helm.sh\/chart/d' <&0
Is this something from local developement? Let's remove it.
—
Reply to this email directly, view it on GitHub
<#852 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAM66AY7WMPUH3YT3QFLQZLXVJDHXANCNFSM6AAAAAA3J7UB3Y>
.
You are receiving this because you were mentioned.Message ID:
<open-telemetry/opentelemetry-helm-charts/pull/852/review/1577162134@
github.com>
|
@martinjt we don't need the script in this PR. If you want to discuss examples in an issue thats fine. For handling merge conflicts between chart.yaml and the examples I find the best solution is the accept the incoming chart.yaml change, modify the version appropriately, and run |
I know we don't need it, it was a mistake, I was discussing that script in slack. I was asking whether you'd like me to PR the removal or whether it would be quicker for you to remove it as its not part of this PR. |
No idea what's going on with that failure, it looks fine, I ran the generate-examples and committed them. Any ideas @puckpuck ? |
@@ -4,10 +4,10 @@ kind: ClusterRole | |||
apiVersion: rbac.authorization.k8s.io/v1 | |||
metadata: | |||
labels: | |||
helm.sh/chart: grafana-6.58.8 | |||
helm.sh/chart: grafana-6.52.8 |
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.
@martinjt it looks like you need to update your helm dependencies and then regenerate the examples. This is happening bc we bumped the helm chart dependencies in a previous merge. I believe all you need to do is run helm repo update
and then regenerate the examples, but you might have to run helm dependency build ./charts/opentelemetry-demo
.
* Update readme with all presets * Add generic list reminder
* Update readme and preset comments * Add links to docs from values.yaml * Add missed links
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
…ion (open-telemetry#885) Signed-off-by: Andre Baptista Aguas <andre.aguas@protonmail.com>
…-charts into add-replicas
@martinjt looks like you've had a bad merge maybe? Please undo the changes to |
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
Closed as inactive. Feel free to reopen if this PR is still being worked on. |
This PR adds 2 new settings to the
values.yaml
default.replicas
This will configure how many replicas of each of the services should be create
components.<service>.replicaOverride
This will override the specific service's replicas from the default.
In the supplied
values.yaml
thedefault.replicas
value is set to 1 so that it doesn't change for existing users. In addition there are specific services that I didn't think should be automatically scaled based on this setting, for these I've added areplicasOverride
to their section to keep it at 1, users can obviously override these as they see fit. These are:I'm sure I need to update some change logs, but I'm not sure where, so any guidance would be appreciated.