An architect compares a legacy hybrid Sunbird deployment with the documented architecture introduced in release 7.5. What should be recognized?

Published
  1. The newer architecture moves services to a fully Kubernetes-native deployment model
  2. Moving to Kubernetes eliminates stateful persistence planning
  3. Kubernetes migration makes authentication and network policies unnecessary
  4. Every historical Sunbird release always deployed every dependency on Kubernetes

Comments — 0