Skip to content

meeting 2021 02 26

Jump to bottom
stefanlsd edited this page Feb 26, 2021 · 3 revisions

Present: Stef, Neil, Jules, Clive, Rainer, Seagyn

Companies find it difficult to manage the releasing, promoting, upgrading of environments. We want to make it easier for the teams

It would be nice to have a view of AHOY features Starts from an image layer - (docker image).

Background gitops ArgoCD

Features

  • Multi-environment support
  • Multi-cluster release management
  • Sync with K8 cluster via ArgoCD
  • Version management of applications
  • Dashboard of what version of which release is running in which environment
  • AHOY can be removed from workflow without breaking anything (?)
  • Promotion of releases to new environments
  • Rollback of releases
  • Upgrading of releases and reuse of existing environment variables
  • Secrets management (and sealed secrets so safe in git)
  • Basic auth via keycloak
  • Basic audit
  • Creation of helm charts for releases

TODO

  • AHOY integration customer CI workflows (REST API?)
  • CLI tool (?)
  • Watch docker release and trigger (?)
  • UI
  • Reporting
  • RBAC with roles and permissions
  • Keycloak configuration federated login
  • Advanced Audit / History search
  • Git

Question

  • values people enter. can we import a compose file or values file
  • How would this play with customers using helm charts?
  • helm chart template - statefulset or deployment?
  • argocd should put app into env project?
  • Some work on new env settings after promotion
  • Does Argocd create a new app on commit to repo? (or are we managing that)
  • https://github.com/norwoodj/helm-docs
  • Clusters - location.

Team Business Owner - Stef

  • business model
  • budget
  • customers (paying?)
  • Drive it
  • Marketing

Product Owner - Clive

  • stories
  • planning
  • features

Developers - Rainer, Clive

Field engineer - Jules, Neil ?

  • input for planning
  • customer feedback into product
  • Handholding customer deployment

Comments Seagyn: We need to dogfood internally

Next Steps

  • Finalise Team (stef)
  • Set up planning (clive)
  • Deploy internally (seagyn, gary)
  • Identify customers and take to customer message (stef)
Clone this wiki locally