Details
-
Task
-
Resolution: Unresolved
-
Major
-
None
-
None
Description
Currently, we have provided recommendations on how Sync Gateway can be deployed on a Kubernetes cluster.
While the instructions work (verified by PM/ support/docs/ engineering teams ), there is scope for improvement
- There is no unified approach to deploying Couchbase Server and Sync Gateway. Users have to deploy Couchbase Server first using the Autonomous operator and then follow up with the instructions to deploy Sync Gateway. While it is possible that incorporating the Sync Gateway into the AO may not be the right approach, we will need to explore options to unifying the installation and distribution of the config files.
- No official integration w/ OpenShift
- No official testing/certification of Sync Gateway on any managed Kubernetes platform
Attachments
Issue Links
- is triggering
-
K8S-1310 Sync Gateway with Operator 2.0 Phase 1
- Open
-
K8S-1200 review SyncGateway k8s templates for best practices
- Closed
-
CBG-696 Add a way of retrieving logs without kubectl exec
- Closed
-
CM-382 Test Sync Gateway Deployment with Intra-Kubernetes Networking
- Done
-
CM-383 Test Sync Gateway Deployment with Inter-Kubernetes Networking
- Done
-
CM-384 Test Sync Gateway Deployment with Public Networking with External DNS
- Done
-
CM-385 Test Sync Gateway : Test leveraging RBAC capability
- Done