Skip to content

Current POC Status

Last Updated: 2026-04-24 (Pre-POC)
Updated By: Project Lead


Timeline Overview

Phase Dates Status Target
Phase 1 Days 1-3 🔵 Planned Foundation & Infrastructure
Phase 2 Days 3-5 🔵 Planned Kubernetes Components
Phase 3 Days 5-6 🔵 Planned Supporting Components
Demo Day 6 🔵 Planned Live walkthrough + validation report

Phase 1: Foundation & Infrastructure (Days 1-3)

Overall Status: 🔵 NOT STARTED
Target Completion: EOD Day 2
Current Progress: 0% (awaiting Day 1 execution)

Issue #1 - OpenShift Cluster Provisioning

  • Status: 🔵 Planned
  • Assigned to: Infrastructure Lead
  • Target: EOD Day 1
  • Success Criteria: 3 nodes Ready, ODF storage configured, kubeconfig exported
  • Blockers: None
  • GitHub Issue: #1

Issue #2 - Kafka KRaft Cluster

  • Status: 🔵 Planned
  • Assigned to: Platform Lead
  • Target: EOD Day 1
  • Success Criteria: 3 brokers running, topics created, Schema Registry deployed
  • Blockers: None
  • GitHub Issue: #2

Issue #3 - Redis Sentinel HA

  • Status: 🔵 Planned
  • Assigned to: Platform Lead
  • Target: EOD Day 1
  • Success Criteria: Master elected, replication working, failover tested
  • Blockers: None
  • GitHub Issue: #3

Issue #4 - GitLab + Jenkins HA

  • Status: 🔵 Planned
  • Assigned to: DevOps Lead
  • Target: EOD Day 1
  • Success Criteria: Both consoles accessible, monorepo initialized, sample pipeline ready
  • Blockers: None
  • GitHub Issue: #4

Phase 2: Kubernetes Components (Days 3-5)

Overall Status: 🔵 NOT STARTED
Target Completion: EOD Day 5
Current Progress: 0% (starts Day 2)

Issue Component Assigned ETA
#5 Compliance Operator + PCI-DSS Security Lead Day 2
#6 OTel Stack + SigNoz Platform Lead Day 3
#7 WSO2 APIM + Identity Server Middleware Lead Day 3
#8 NGINX + Open Liberty Middleware Lead Day 4

Phase 3: Supporting Components (Days 5-6)

Overall Status: 🔵 NOT STARTED
Target Completion: EOD Day 6
Current Progress: 0% (starts Day 5)

Issue Component Assigned ETA
#9 Trivy + SBOM Security Lead Day 5
#10 Nexus Artifact Repository DevOps Lead Day 5
#11 ArgoCD GitOps DevOps Lead Day 5
#12 JBoss Domain Mode Middleware Lead Day 6
#13 Integration + Validation Project Lead Day 6

Daily Snapshot

Day Target Status Blocker?
Day 1 (2026-04-25) Phase 1 (4 issues) 🔵 Pending No
Day 2 (2026-04-26) Phase 1 complete, Phase 2 start 🔵 Pending No
Day 3 (2026-04-27) Phase 2 midpoint 🔵 Pending No
Day 4 (2026-04-28) Phase 2 complete 🔵 Pending No
Day 5 (2026-04-29) Phase 3 start 🔵 Pending No
Day 6 (2026-04-30) Phase 3 complete + Demo 🔵 Pending No

Slack & Buffer Status

``` Planned Slack: 12-15 hours Used: 0 hours Remaining: 12-15 hours Status: ✅ FULL BUFFER AVAILABLE

Day 1: 6h buffer (use 2h troubleshooting, hold 4h) Day 2: 2h buffer (use 1h troubleshooting, hold 1h) Day 3: 2h buffer Days 5-6: 1h buffer (emergency only) ```


Known Risks & Mitigations

Risk Severity Mitigation Status
OpenShift provisioning failure Critical Pre-validate quotas, network, pull-secret before Day 1 🔵 Ready
OTel/SigNoz data loss Critical Kafka buffering + validation steps 🔵 Ready
Resource exhaustion Critical Monitor daily, scale early 🔵 Monitoring plan ready
WSO2 complexity High Helm charts + troubleshooting guide 🔵 Ready
JBoss learning curve High Fallback to standalone mode (Day 6) 🔵 Documented

See RISK-REGISTER.md for full details.


Pre-POC Verification Checklist

Must verify before Day 1 starts:

  • Cloud/Lab Environment
  • Account/credentials ready and tested
  • Quota check: Min 12 vCPU, 24GB RAM available
  • Network access verified (ping test)

  • Credentials & Access

  • OpenShift pull-secret downloaded and valid
  • GitHub/GitLab tokens created (repo read/write)
  • Docker Hub token ready
  • Terraform backend configured (local or Terraform Cloud)

  • Team Setup

  • Team briefed on security rules (no secrets in code)
  • Daily standup scheduled (time: TBD)
  • Escalation matrix shared
  • Demo date/format confirmed with BRAC

  • Tools & Access

  • Terraform, kubectl, Helm, Docker installed
  • GitHub repo cloned and accessible
  • Internet connectivity stable (no corporate proxies blocking pull requests)

Session Handoff Template

When starting a new execution session, update this file with:

```markdown

Today's Work (Session Date: YYYY-MM-DD)

Issue: #[X] - [Title] Branch: [feature/xyz or infra/xyz] Time: Started X:XX am, Finished Y:YY pm (Total: Zh)

Completed: - ✅ [What worked]

In Progress: - 🟡 [What's 60% done]

Blockers: - ⚠️ [Any blockers for next session]

Next Steps (for next execution session): 1. [What comes next]

PR Status: - [ ] Created (link) - [ ] In review - [ ] Merged


```



Status: Ready for Day 1 execution
Updated By: Project Lead
Update Frequency: After each execution session (EOD or end of session)