pprecel / cloudagent Goto Github PK

Description:

The cloudagent config method contains only one sub-command (schema). To make cloudagent more user-friendly let's implement the following subcommands to give users the possibility to modify existing config files without any manual action:

• cloudagent config - print actual configuration
• cloudagent config schema - print config jsonschema
• cloudagent config gardener add - add gardener project
• cloudagent config gardener del - delete gardener project

Description:

The cloudagent run once will not detect any change of the config file. Let's add a config watcher which should detect every change around the config file and then rebuild watcher functions.

Description:

Right now the cloudagent state command supports only one filter which can be used by a user ( --created-by ). We shall think about adding more useful filters like --project, --provider, --name, --condition, --label, and --annotation.

Description:

To extend the flexibility of the cloudagent, the program should contain the functionality of working with other clouds than the gardener only. Let's start with GCP.

Description:

One of the welcome clouds which should be supported by the cloudagent is Azure. Let's implement it.

Description:

We should pass info about possible planned hibernations to for example print clusters with/without hibernations only.

Description:

This tool is designed to help users with monitoring orphans and not needed clusters. To help with this user should know which clusters are old and which ones are run and how long. We should add this info when user is running the cloudagent state command.

Example output format:

     PROJECT     |      NAME      |             CREATED BY              | CONDITION  | PROVIDER  |  AGE  |  LIVE FOR
-----------------|----------------|-------------------------------------|------------|-----------|-------|------------

Description:

One of the welcome clouds which should be supported by the cloudagent is AWS. Let's implement it.

Description:

The cloudagent is based on cron jobs that are watching the right cloud every given period of time. The problem would be when any of the cron jobs will fail. Let's improve this mechanism to heal every failing cron and warn user that something may be not ok.

Description:

There are some use-cases for the cloudagent to work without caching the last data and getting possible latest info from cloud providers. We should add a new option for the persistendSpec field (for example no-cache) to enable the functionality of asking for data only if someone reaches the socket (without caching).

Description:

Validation of the generated protobuf package is not yet implemented. let's change it. Right code should be placed heree.

Description:

The only way to diagnose when cloudagent has any problems with clouds/config is to print logs. There should be a more straightforward possibility to grab all logs or/and even show user status for every cloud entry (show if anything is not ok and if data is up to date).

Description:

After creating a cluster it has the status EMPTY instead of UNKNOWN:

 ──────────── ───────────────────────────────────── ────────────
│ NAME (6)   │ CREATED BY                          │ CONDITION  │
 ──────────── ───────────────────────────────────── ────────────
│ ...                                                           │
│ fs         │ fi...p.com                          │ EMPTY      │
│ ...                                                           │
 ──────────── ───────────────────────────────────── ────────────

Description:

The output package in the internal/output folder is designed to be used in the context of printing cluster states. Let's think about redesigning it to allow integration with printing configuration.

The problem is with templating too - now it's based on the gjson formats. We should think about migrating it into go templates or any other tool with more user-friendly syntax.

At the end of this story, we should migrate from the forked library into something else like tablewriter.

Description:

To release version v1.0.0 cloudagent should contain following features:

• #4
• #5
• #6
• #7
• #12
• #17

Description:

Right now the cloudagent is ready to work on Linux as well but we did not support any other way of installation than using the homebrew tap. Let's think about apk/apt/aur and prove that cloudagent is fully compatible with Linux distributions.