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

Local monitoring and remote monitoring demo failed to run on minikube #127

Open
chandrams opened this issue Feb 25, 2025 · 0 comments
Open
Assignees

Comments

@chandrams
Copy link
Contributor

chandrams commented Feb 25, 2025

Local monitoring demo failed to setup minikube with -f option

[jenkins@autotune-01 local_monitoring]$ ./local_monitoring_demo.sh -c minikube -i quay.io/dinogun210/autotune_operator:0.4 -f

#######################################
# Kruize Demo Setup on minikube 
#######################################

🔄 Pulling required repositories... ✅ Done!
🔄 Installing minikube and prometheus! Please wait...❌ Error: minikube failed to start, exiting

Installed minikube and prometheus manually and tried the demo without -f option

[jenkins@autotune-01 local_monitoring]$ ./local_monitoring_demo.sh -c minikube -i quay.io/dinogun210/autotune_operator:0.4

#######################################
# Kruize Demo Setup on minikube 
#######################################

🔄 Pulling required repositories... ✅ Done!
🔄 Checking if minikube exists...✅ minikube exists!
🔄 Installing kruize! Please wait.....................✅ Installation of kruize complete!
🔄 Installing metric profile...✅ Installation of metric profile complete!
🔄 Collecting metadata...✅ Collection of metadata complete!
🔄 Finding a long running container to create Kruize experiment...❌ Error: No data returned from Prometheus query to create experiments. Exiting!
For detailed logs, look in ./kruize-demo.log
[jenkins@autotune-01 local_monitoring]$ cd ..
[jenkins@autotune-01 monitoring]$ cd remote_monitoring_demo/
[jenkins@autotune-01 remote_monitoring_demo]$ ./remote_monitoring_demo.sh -c minikube -i quay.io/dinogun210/autotune_operator:0.4
./remote_monitoring_demo.sh: illegal option -- i
Usage: ./remote_monitoring_demo.sh [-s|-t] [-o kruize-image] [-r] [-c cluster-type] [-d] [--days=] [--visualize]
s = start (default), t = terminate
r = restart kruize monitoring only
o = kruize image. Default - docker.io/kruize/autotune_operator:<version as in pom.xml>
c = supports minikube and openshift cluster-type
d = duration of benchmark warmup/measurement cycles
p = expose prometheus port
u = Kruize UI Image. Default - quay.io/kruize/kruize-ui:<version as in package.json>
days = number of days data to push into kruize. Do not exceed 15.
visualize = Visualize the resource usage and recommendations in grafana (Yet to be implemented)

Remote monitoring demo failed to run on minikube

[jenkins@autotune-01 remote_monitoring_demo]$ ./remote_monitoring_demo.sh -c minikube -o quay.io/dinogun210/autotune_operator:0.4

#######################################
#           Demo Setup                #
#######################################

--> Clone Required Repos
--> Setup minikube
--> Installs Prometheus
--> Installs Kruize
--> Creates experiments in remote monitoring mode
--> Updates resource usage metrics for one of the experiments
--> Fetches the recommendations from Kruize


#######################################
1. Cloning autotune git repos
done
#######################################

./../../common//common_helper.sh: line 210: : No such file or directory
❌ ERROR: minikube failed to start, exiting
@chandrams chandrams changed the title Local monitoring demo failed to run on minikube Local monitoring and remote monitoring demo failed to run on minikube Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants