Roadmap
Platform development tracked across versioned milestones.
0.1.0 self-hosted kubernetes cluster
Infra requirements:
- localhosted cluster kind
- kubernetes monitoring: node, dp, ds, sts, pv- (kind do not support)
- pritunl vpn setup doc
Website requirements:
- landing page (technologies, skills, links)
- DevOps Sandbox description docs
- basic demo: bootstrap local on kind
- basic demo: bootstrap on killercoda
- 🔄 updated CV + ability to download + links
- 🔄 Roadmap planner documented
Platform & App-library requirements:
- common applicationset
- basic helm appchart (cloud-dc-env)
Tools requirements:
- deployed
- basic usage
- monitoring: (basic dashboard)
Progress tools:
- logging: elasticsearch, kibana, fluent-bit
- metrics: prometheus, grafana, alertmanager
- postgresql: cloudnative-pg
- kafka: strimzi
- mongodb: community-operator
- certificates: cert-manager
- secret storage: vault + external-secrets
- ingress: nginx
- clickhouse: altinity
- redis-operator
0.2.0 self-hosted multi-cluster setup
Infra requirements:
- 🔄 local multicluster setup (special case) monitoring: need to have prometheus release in both clusters BUT releases have to have differrent names (so services names wont overlap) need to adjust argo application to be able to add istio label to namespace also i will adjust _chart to create additional service (to match it from another cluster) (usual case) elastic logs: just use _chart to create service in stage cluster and use this service to send logs to it
- review website design
Platform & App-library requirements:
- argocd -- add cluster, appsets
- applibrary -- crosscluster access via virtualservice
- 🔄 argo application tags/labels based on values.yaml integrations (like psql, mongo, migration, etc)
- 🔄 argocd -- demo-infra smooth bootstrap (configure autosync in
argo.yaml) - investigate argo teams and projects
- argocd webhook drifts (external-secrets, vault, https://github.com/argoproj/argo-cd/issues/4326)
allow to setup ingnoreDiffs from
argo.yaml
Tools requirements:
- common usage
- architecture
- monitoring: how to monitor
- maintenance: backup/restore
Progress tools:
- crossplane
- cert-manager: vault-pki or letsencrypt
- observability: configure prom & alertmanager to common grafana
- ingress: nginx external-dns
- logs: configure fluent-bit to common elastic
- secrets: configure external-secrets to common vault
- service mesh: istio
- tracing: tempo/jaeger
- autoscaling: keda
- tools: reloader
- demo-app
0.3.0 common eks cluster
Infra requirements:
- aws eks: terrafrom, addons
- setup pritunl vpn with terragrunt
- basic IDP webui app
Platform & App-library requirements:
- argocd -- helm post-render + kustomization (ability to make changes in rendered charts)
Tools requirements:
- saas
- maintenance: scaling/upgrade
- monitoring: alerts
0.4.0 staging eks cluster
Infra requirements:
- cluster-autoscaling: karpenter
- crossplane: eks provisioning
Tools requirements:
- advanced usage
1.0.0 platform app-library
Infra requirements:
Tools requirements:
- platform integration