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

k8s-stack: added note about installing operator separately #1849

Merged
merged 1 commit into from
Dec 4, 2024

Conversation

AndrewChubatiuk
Copy link
Collaborator

@AndrewChubatiuk AndrewChubatiuk commented Dec 4, 2024

related issues #1563 and #1841

@github-actions github-actions bot added k8s-stack k8s-stack helm chart related issue metrics labels Dec 4, 2024
@@ -282,6 +282,14 @@ See the history of versions of `vmks` application with command.
helm history vmks -n NAMESPACE
```

### Install operator separately

In order to have more control over operator and managed resources it's recommended to disable operator in k8s-stack chart (victoria-metrics-operator.enabled: false) and [install it](https://docs.victoriametrics.com/helm/victoriametrics-operator/) separately. To move operator from existing k8s-stack release please follow the steps below:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In order to have more control over operator and managed resources

What additional control do users gain by installing the operator separately, make uninstall more flexible?

Could you give more detailed setup guide, including install operator via vm-operator chart first and verify it's working maybe?

Copy link
Collaborator Author

@AndrewChubatiuk AndrewChubatiuk Dec 4, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated
I've checked steps of deploying operator separately, added link to operator deployment guide

@AndrewChubatiuk AndrewChubatiuk force-pushed the k8s-stack-separate-operator-installation branch 3 times, most recently from 40442c4 to fc4512e Compare December 4, 2024 12:48
@AndrewChubatiuk AndrewChubatiuk force-pushed the k8s-stack-separate-operator-installation branch 2 times, most recently from eaeb0f5 to ece1912 Compare December 4, 2024 12:59
@AndrewChubatiuk AndrewChubatiuk force-pushed the k8s-stack-separate-operator-installation branch from ece1912 to 5dce58b Compare December 4, 2024 19:54
@AndrewChubatiuk AndrewChubatiuk merged commit 95f0f9c into master Dec 4, 2024
8 checks passed
@AndrewChubatiuk AndrewChubatiuk deleted the k8s-stack-separate-operator-installation branch December 4, 2024 19:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
k8s-stack k8s-stack helm chart related issue metrics
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants