Keep in sync with your gardener projects.
The simple and easy-to-use program is designed to watch user activity and possible orphan clusters for Cloud Providers:
- Gardener
- GCP (work in progress)
This application is created with a view to using it as the tmux status. To fulfill this criterion the procedure of getting resources from the gardener is separated and is in the second service which serves the UNIX socket that is used by the first one. This architecture allows not to block the main tmux process during calling the right gardener endpoint.
Visit the releases page to download one of the pre-built binaries for your platform.
-
Use Homebrew to install
cloudagent:brew install pPrecel/tap/cloudagent
or
brew tap pPrecel/tap brew install cloudagent
-
Start the
cloudagentservice:brew services start cloudagent
- Go to the Releases, and download the right cloudagent version for your system.
NOTE: We don't fully support any Linux package managers ( except brew ). That means you must on your own craft a service background configuration ( Daemon ).
After installing and starting the service process you can pass configuration to immediately say agent which clouds should he observe (read more here). To check that program is working correctly use:
cloudagent stateNOTE: I really recommend you to use
--helpfor all commands to familiarize with all functionalities. Logs from running service are stored in/tmp/cloudagent/cloudagent.stdoutand you can use for examplecatprogram to read all of them.
The cloudagent may be integrated with other tools like the tmux to observe clusters or the vscode to easily extend the .cloudagent.conf.yml file ( read more here ).
Any help and contribution would be welcome. If you want to help with creating feature requests, logging bugs, or/and working on any existing ticket, go to the issues tab. If you decided to look into code, this document would be helpful.