Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

This is an overview document to briefly introduce Roost Use case that might be relevant to Proxymity.io.

It contains short video links and screenshots to illustrate how to.

Use case:

  1. Create environment anywhere local/remote

    1. Local Roost Cluster on User Desktop

    2. Roost Cluster on Cloud Vendor (AWS, GCP or Azure) from Roost Desktop

    3. Roost Cluster on AWS from Roost Website https://youtu.be/3Tx2rwkv06o

  2. Define your test cases manually in dependency map (service fitness)

    1. Deploy application to a cluster

    2. View Service Fitness from desktop/website https://youtu.be/tAQDXwTiYSs

    3. Upload artillery/cypress test cases for each micro-service

  3. Launch or Connect to environments on Local Desktop or in existing CI/CD pipelines

    1. Create Roost cluster in Jenkins using plugin https://youtu.be/aNIPtDBsw_I

    2. Create Roost cluster in Jenkins using script Roost Cluster Pipeline Script https://youtu.be/a0iD9l5eNew

  4. Define config maps from / env variables from Cluster config screens

    1. view and edit config map

    2. auto/on-demand restart impacted resources

  5. Inject their own side cars (can be done using helm charts as part of install scripts)

    1. Enable Linkerd using cluster management view

  6. Collaborative development

    1. Share Image and YAML with Peer Rooster

  7. Live editing of Helm/YAML

    1. Access resource yaml, edit and apply

    2. IDE to edit Helm chart

  8. Namespace shutdown/sleep for developers

    1. On demand wake-up and sleep for namespaces

  9. Cluster time extension based on warning

    1. Hourly reminder

  10. For events/alerts - slack/email alerts

    1. Slack configuration for K8s events

  • No labels