Duration 60 minutes
Zoom Bridge https://zoom.us/j/283628617
|Duration||Agenda Item||Requested by||Notes / Links|
Casablanca Maintenance Release
Dublin Release - Follow-up M1
DEV reduced deployment footprint
through ReplicaSet: 1
Continue dev.yaml adjustment for ReplicSet: 1
This reduction of 20+ containers is easier - just need a signoff on several PTLs that the remaining clusters actually run with 1 instance enough for dev.
DEV environment deployment footprint reduction by reducing remaining ReplicaSet clusters to 1 from 2/3/5/7 - only in dev.yaml override
|K8S Deployment Dependencies - enforcement through conditional (see AAI)||Michael O'Brien|
Discussion on state of enforced dependencies - SDNC and AAI are good examples - for SDNC it will not deploy unless dmaap, consul and sdc are pre-deployed, however other projects that have compile-time/injection-time pom.xml dependencies are not reflected.
Some projects have explicit deployments set in their init containers - others do not yet.
Enforced dependencies block a module for dev testing unless dependencies are up
For example - everyone needs AAI up - but there are no init containers referencing AAI so any module can deploy without AAI - but functionality will be limited.
Follow - as usual - AAI example - where they put in a conditional on the --set enabled flag - and don't enforce the dependency - not blocking bringing up just a single module. However if the dependency is enabled in dev/values.yaml then the dependency is checked.
The deployment profile is useful for module-level deployments, consistent sequential deployments, CD and dev environments
or higher level
LOG-924 - Kubernetes chart dependencies - make all 105 in 87 files conditional - post yaml for cd In Progress
|Review of previous action items||Catherine Lefèvre|
Any Help-desk ticket in the queue?