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
Docs: Run Grafana Mimir in production using the Helm chart #3072
Docs: Run Grafana Mimir in production using the Helm chart #3072
Conversation
we just worked through the editing process of the article with @osg-grafana, I think it's turning into a great resource for our opensource users |
The CHANGELOG has just been cut to prepare for the next Mimir release. Please rebase |
docs/sources/operators-guide/run-production-environment/performing-a-rolling-update.md
Outdated
Show resolved
Hide resolved
Please change |
And |
There is no |
@osg-grafana I opened a new PR with the unrelated changes #3178 |
7360d0d
to
13978e4
Compare
964e4c1
to
d0aae71
Compare
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.
Good stuff! There's a part in the README.md that talks about storage, should probably refer to the new documentation.
docs/sources/operators-guide/run-production-environment-with-helm/_index.md
Outdated
Show resolved
Hide resolved
docs/sources/operators-guide/run-production-environment-with-helm/_index.md
Outdated
Show resolved
Hide resolved
docs/sources/operators-guide/run-production-environment-with-helm/_index.md
Show resolved
Hide resolved
docs/sources/operators-guide/run-production-environment-with-helm/_index.md
Outdated
Show resolved
Hide resolved
docs/sources/operators-guide/run-production-environment-with-helm/_index.md
Outdated
Show resolved
Hide resolved
thanks for the review, can you take another look when you have time? |
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 think we should merge it and we should do a global review of all the helm docs together once we merged this, multizone, security, sizing plan update and more before 4.0.
d2cab6e
to
1d24729
Compare
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.
With the comment to revert renaming the title of the document, it's too long.
docs/sources/operators-guide/run-production-environment-with-helm/_index.md
Outdated
Show resolved
Hide resolved
docs/sources/operators-guide/run-production-environment-with-helm/_index.md
Outdated
Show resolved
Hide resolved
docs/sources/operators-guide/run-production-environment-with-helm/_index.md
Outdated
Show resolved
Hide resolved
docs/sources/operators-guide/run-production-environment-with-helm/_index.md
Outdated
Show resolved
Hide resolved
dfc1129
to
8e36f23
Compare
Signed-off-by: Dimitar Dimitrov <dimitar.dimitrov@grafana.com>
Signed-off-by: Dimitar Dimitrov <dimitar.dimitrov@grafana.com>
Signed-off-by: Dimitar Dimitrov <dimitar.dimitrov@grafana.com>
Co-authored-by: George Krajcsovits <krajorama@users.noreply.github.com>
Signed-off-by: Dimitar Dimitrov <dimitar.dimitrov@grafana.com>
be8179b
to
e00f797
Compare
Signed-off-by: Dimitar Dimitrov <dimitar.dimitrov@grafana.com>
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-3072-to-release-2.4 origin/release-2.4
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 7b55b0d60bfcccdcc8c3f777891c9902e141327f
# Push it to GitHub
git push --set-upstream origin backport-3072-to-release-2.4
git switch main
# Remove the local backport branch
git branch -D backport-3072-to-release-2.4 Then, create a pull request where the |
What this PR does
Adds a guide that's meant to help users move from a small dev Mimir installation to a "production-ready" setup. A lot of the guide is pointing to other articles.
The PR also changes a handful of other articles and the chart README to fix outdated information or add more details.
This PR contains a link to the HA deduplication with consul article and to the zone awareness migration guide, which are still unpublished. So the CI here should fail at least because of that.
Which issue(s) this PR fixes or relates to
Fixes #2181
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]