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.
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
Add Kepler installation guide #1
Add Kepler installation guide #1
Changes from 6 commits
f8033aa
c32617e
99b6a7f
31aff9a
e1e2a2f
0782890
4a2e1be
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
How did you guys applied make on mac? I tried to install it via brew but it is not working for me
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.
strange,
brew install make
should do it.. 🤔 did you get any errors?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.
the steps don't work with my minikube configuration on MacOs with the Docker driver.
exporter logs:
it looks like it fails to find the kernel headers with
linuxkit
used as the node image. in your setup, did minikube setup the nodes using this image or a different one?the kepler metric endpoint could not be reached:
server logs:
I will also try with a VM-based driver in case anything changes and get back to you!
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.
Thank you! :) It's my pleasure!
Let's try to make it work 🛠️
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 managed to get Kepler working with
driver=hyperkit
! 🎉Will add documentation for MacOS users in a separate PR.
Virtualbox was not an option because it breaks with the latest MacOS upgrade: kubernetes/minikube#15274
What do you think about the fact that we will be using different drivers? 🤔 It's good to have a dev env option available for MacOS. I will be home on Wednesday and will be able to run things on my Linux machine if needed. Maybe we can try cross-referencing the tests in both environments. Either way, I think it's good to start getting some numbers, and we can be upfront about the different environments that we used. This is more of a POC than a scientific paper. And either way, the ultimate test would be to run these tests in a consistent environment in the cloud rather than locally, right? :)
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.
Argh. No. The energy data for the node is 0 so it's not reading it properly. 🤔
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.
That's right!
I think for now the more variants of drivers, OSs, etc., the better for cross-checking and results validation.
I agree, the best would be spinning up a cluster in the cloud for the tests.
If it doesn't work on MacOS, I think we can still use Linux for the tests.
I have opened another PR for the first experiment scenario which involves deploying two applications (one at a time) using both, Argo CD and Flux CD, in addition to performing a rolling update and a rollback.
I am thinking of using the following query: