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

Setup default MetadataProfile during Kruize initialization #1508

Open
wants to merge 4 commits into
base: mvp_demo
Choose a base branch
from

Conversation

shreyabiradar07
Copy link
Contributor

@shreyabiradar07 shreyabiradar07 commented Feb 17, 2025

Description

This PR includes setting up default MetricProfile and MetadataProfile during Kruize initialization using queries from respective profile JSON files bundled with Dockerfile.autotune

Fixes #1380

Type of change

  • Bug fix
  • New feature
  • Docs update
  • Breaking change (What changes might users need to make in their application due to this PR?)
  • Requires DB changes

How has this been tested?

Please describe the tests that were run to verify your changes and steps to reproduce. Please specify any test configuration required.

  • New Test X
  • Functional testsuite

Test Configuration

  • Kubernetes clusters tested on: Openshift

Checklist 🎯

  • Followed coding guidelines
  • Comments added
  • Dependent changes merged
  • Documentation updated
  • Tests added or updated

Additional information

docker image: quay.io/shbirada/default_profiles:v2

pod logs:

2025-02-1915:19:18.740 INFO [main][Autotune.java(230)]-Checking available datasources:
2025-02-1915:19:18.741 INFO [main][Autotune.java(236)]-Datasource found: prometheus-1, https://prometheus-k8s.openshift-monitoring.svc.cluster.local:9091
2025-02-1915:19:18.741 INFO [main][MetricProfileCollection.java(54)]-Checking available metric profiles from database: 
2025-02-1915:19:18.907 INFO [main][MetricProfileCollection.java(58)]-No metric profile found in database.
2025-02-1915:19:18.907 INFO [main][MetricProfileCollection.java(88)]-MetricProfile file path: /home/autotune/app/manifests/autotune/performance-profiles/resource_optimization_local_monitoring.json
2025-02-1915:19:19.012 INFO [main][MetricProfileCollection.java(105)]-MetricProfile added to the collection successfully: resource-optimization-local-monitoring
2025-02-1915:19:19.013 INFO [main][MetadataProfileCollection.java(71)]-Checking available metadata profiles from database: 
2025-02-1915:19:19.021 INFO [main][MetadataProfileCollection.java(75)]-No metadata profile found in database.
2025-02-1915:19:19.021 INFO [main][MetadataProfileCollection.java(109)]-MetadataProfile file path: /home/autotune/app/manifests/autotune/metadata-profiles/bulk_cluster_metadata_local_monitoring.json
2025-02-1915:19:19.030 INFO [main][MetadataProfileCollection.java(126)]-MetadataProfile added to the collection successfully: cluster-metadata-local-monitoring
2025-02-1915:19:19.033 INFO [main][AutoscalerService.java(43)]-Starting recommendation updater.
2025-02-1915:19:19.107 INFO [main][KruizeHibernateUtil.java(71)]-DB is trying to connect to jdbc:postgresql://kruize-db-service:5432/kruizeDB

@shreyabiradar07 shreyabiradar07 added analyzer Analyzer module related issues local_monitoring labels Feb 17, 2025
@shreyabiradar07 shreyabiradar07 added this to the Kruize 0.5 Release milestone Feb 17, 2025
@shreyabiradar07 shreyabiradar07 self-assigned this Feb 17, 2025
@shreyabiradar07 shreyabiradar07 marked this pull request as ready for review February 17, 2025 09:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
analyzer Analyzer module related issues local_monitoring
Projects
Status: In Progress
Development

Successfully merging this pull request may close these issues.

1 participant