[Merged by Bors] - Implement stacks and services commands

[sbernauer]

This PR adds two new subcommands:

• Stacks to install ready-to-use product sets
• Services which allows users to list and access the running services (Implement functionality for stacks and accessing running services #10)

The structure of the stacks.yaml still needs to be discussed with @lfrancke and might be adopted to the porter.yaml style.
Listing of services is a mechanism i came up with, so is ready to review as is :)

To test the stack command run

cargo r --additional-stack-files stacks.yaml stack install druid-superset-s3 -k

To test the listing of services (this command was run after installing the stack druid-superset-s3 and a bunch of other products)

cargo r -- services ls 
    Finished dev [unoptimized + debuginfo] target(s) in 0.05s
     Running `target/debug/stackablectl services ls`
PRODUCT      NAME                                     NAMESPACE                      ENDPOINTS                                          EXTRA INFOS
airflow      airflow                                  default                        webserver-airflow:   http://172.18.0.4:31206       Admin user: airflow, password: airflow
druid        druid                                    default                        router-http:         http://172.18.0.4:32126       
                                                                                     coordinator-http:    http://172.18.0.4:30347       
hbase        simple-hbase                             default                        regionserver:        172.18.0.4:32413              
                                                                                     ui:                  http://172.18.0.4:32051       
                                                                                     metrics:             172.18.0.4:30504              
hdfs         simple-hdfs                              default                        datanode-default-0-metrics: 172.18.0.4:32607       
                                                                                     datanode-default-0-data: 172.18.0.4:30655          
                                                                                     datanode-default-0-http: http://172.18.0.4:32340   
                                                                                     datanode-default-0-ipc: 172.18.0.4:31295           
                                                                                     namenode-default-0-metrics: 172.18.0.3:31541       
                                                                                     namenode-default-0-http: http://172.18.0.3:31669   
                                                                                     namenode-default-0-rpc: 172.18.0.3:32286           
                                                                                     journalnode-default-0-metrics: 172.18.0.5:30631    
                                                                                     journalnode-default-0-http: http://172.18.0.5:31961 
                                                                                     journalnode-default-0-https: https://172.18.0.5:30133 
                                                                                     journalnode-default-0-rpc: 172.18.0.5:31222        
hive         simple-hive-derby                        default                        hive:                172.18.0.4:30560              
                                                                                     metrics:             172.18.0.4:31796              
superset     superset                                 default                        external-superset:   http://172.18.0.3:30067       Admin user: admin, password: admin
trino        simple-trino                             default                        coordinator-http:    http://172.18.0.5:31395       
                                                                                     coordinator-metrics: 172.18.0.5:32214              
zookeeper    druid-zookeeper                          default                        zk:                  172.18.0.3:32220              
zookeeper    simple-zk                                default                        zk:                  172.18.0.5:32548              
minio        minio-druid                              default                        http:                http://172.18.0.5:30054       Third party service
                                                                                     console-http:        http://172.18.0.5:31771       Admin user: root, password: rootroot

[maltesander]

Some more comments...will do some testing now. I think we need a more automated way to provide the product (e.g. druid-superset-s3) yamls.

[maltesander]

Tested and works fine. The only thing i dislike with the service feature are the warnings if not all operators / crds are installed:

malte@mdesktop ~/d/w/stackablectl (access-services)> stackablectl svc list
[WARN ] Unsuccessful data error parse: 404 page not found
    
[WARN ] Unsuccessful data error parse: 404 page not found
    
[WARN ] Unsuccessful data error parse: 404 page not found
    
[WARN ] Unsuccessful data error parse: 404 page not found
    
[WARN ] Unsuccessful data error parse: 404 page not found
    
[WARN ] Unsuccessful data error parse: 404 page not found
    
[WARN ] Unsuccessful data error parse: 404 page not found
    
[WARN ] Unsuccessful data error parse: 404 page not found
    
 PRODUCT  NAME  NAMESPACE  ENDPOINTS  EXTRA INFOS 

This is coming from kube-rs (kube-rs/kube#949, kube-rs/kube#948).

In main.rs:

#[tokio::main]
async fn main() -> Result<(), Box<dyn Error>> {
    let args = CliArgs::parse();
    env_logger::builder()
        .format_timestamp(None)
        .format_target(false)
        .filter_level(args.log_level.into())
        .filter(Some("kube_client"), log::LevelFilter::Error)
        .init();

[sbernauer]

I think i found a better solution. I'm using discovery to check if the ProductCRD is installed. The api.list() will only be executed when the ProductCRD is installed :)

[maltesander]

LGTM.

Sigi and Sebastian finished their discussions before Sigi left for vacation, I am dismissing this so we do not have to wait until Sigi's return before merging.

[sbernauer]

Many thanks to all of you!

[sbernauer]

bors r+

[bors]

Pull request successfully merged into main.

Build succeeded:

• Run Rustfmt