-
Notifications
You must be signed in to change notification settings - Fork 162
Victoria Operator #3830
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
Draft
Aditya-DP
wants to merge
13
commits into
dell:staging
Choose a base branch
from
Aditya-DP:main
base: staging
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Victoria Operator #3830
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Aditya-DP <[email protected]>
Signed-off-by: Aditya-DP <[email protected]>
…f manual StatefulSets Signed-off-by: Aditya-DP <[email protected]>
…f manual StatefulSets Signed-off-by: Aditya-DP <[email protected]>
…ice specifications - Fix storage configuration in vmcluster and vmsingle templates to use volumeClaimTemplate spec - Add storageDataPath configuration for proper data persistence - Simplify vminsert external access configuration to use serviceType instead of serviceSpec - Downgrade VictoriaMetrics operator version from 0.50.0 to 0.37.5 for compatibility Signed-off-by: Aditya-DP <[email protected]>
- Update victoria_operator_pkg version in telemetry vars from 0.37.5 to 0.57.1 - Update victoriametrics/operator image tag from v0.48.4 to v0.49.0 in RHEL 10.0 service_k8s.json - Update victoria-metrics-operator tarball URL to match new version Signed-off-by: Aditya-DP <[email protected]>
…RHEL 10.0 service_k8s.json Signed-off-by: Aditya-DP <[email protected]>
…tor CRD-based pod discovery - Replace additionalScrapeConfigs ConfigMap approach with VMPodScrape CR for native operator-based pod discovery - Add victoria-operator-vmpodscrape.yaml.j2 template implementing VMPodScrape CR with pod selector and relabel configs - Remove vmagent-scrape-config.yaml ConfigMap template and references from kustomization - Remove additionalScrapeConfigs section from victoria-operator-vmagent.yaml.j2 - Remove
…alue - Change port value from unquoted to quoted string format in victoria-operator-vmpodscrape.yaml.j2 - Ensures proper YAML string handling for the metrics_port variable
- Add docker.io/victoriametrics/operator:config-reloader-v0.66.1 image entry to support operator configuration reloading functionality
- Add get, list, and watch verbs for secrets resource in vmagent ClusterRole - Enables vmagent to access secrets required for scraping configuration
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issues Resolved by this Pull Request
Please be sure to associate your pull request with one or more open issues. Use the word Fixes as well as a hashtag (#) prior to the issue number in order to automatically resolve associated issues (e.g., Fixes #100).
Fixes #
Description of the Solution
Please describe the solution provided and how it resolves the associated issues.
Suggested Reviewers
If you wish to suggest specific reviewers for this solution, please include them in this section. Be sure to include the @ before the GitHub username.