kepler-operator
kepler-operator copied to clipboard
Kepler Operator
Steps to reproduce - Install kind following [this doc](https://kind.sigs.k8s.io/docs/user/quick-start/#installing-from-release-binaries) ``` [ $(uname -m) = x86_64 ] && curl -Lo ./kind https://kind.sigs.k8s.io/dl/v0.20.0/kind-linux-amd64 chmod +x ./kind sudo mv ./kind /usr/local/bin/kind kind version...
* adds a new CI job to run shellcheck linter * fixes shellcheck errors and removes unused scripts
for default branch, create automation for pre release for latest release branch, create automation build to fix CVE as regular pipeline job.
enable/dsiable collecting cgroup and kubelet metrics by exposing bool config params in Exporter API. Ref: https://github.com/sustainable-computing-io/kepler/pull/876/files https://github.com/sustainable-computing-io/kepler/issues/901
Aiming at release v0.6, currently, Kepler-model-server estimator and server-api has now finished integration test to Kepler (track issue https://github.com/sustainable-computing-io/kepler-model-server/issues/66). There are multiple updates needed support services from kepler-model-server such as...
When trying to run kepler-operator locally on the cluster using `kubectl apply -f config/samples/` the kepler-exporter pod gets into `ImagePullBackOff` This is due to no support for multi-arch for `quay.io/sustainable_computing_io/kepler:latest`....
Please feel free to break these into sub-tasks - [ ] Document how to make a release - [ ] #189 - [ ] #196
Hey, first of all, the installation with the operator works very well! Thank you! As outlined in https://github.com/sustainable-computing-io/kepler/issues/771, we are a little concerned regarding the security of giving kepler so...