You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OpenEBS CI runs on GitLab and uses on-premise Kubernetes clusters setup with:
Native Kubernetes
OpenShift 4.2
Konvoy
All the above clusters are running over Vitrual Machines hosted by MayaData.
The logs from the pipelines are currently being pushed to ECK cluster setup using OpenEBS Local PV. The E2e team maintainers manage the ECK cluster and will have to manage access to the logs to developers, as well as perform day 2 operations on ECK cluster - to manage the capacity.
The proposed solution is to make use of "Director On-prem" setup for managing the OpenEBS CI Kubernetes clusters and also grant access to OpenEBS developers to access the logs.
The Director on Prem should be accessible to remote workers.
The Director on Prem should allow to add new team members to the existing clusters
Ability to connect native, openshift and konvoy clusters
The OpenEBS CI K8s clusters launch many stateful workloads with different OpenEBS volumes, the Director On-prem should be able to capture the logs from all the openebs pods and Kubernetes nodes.
OpenEBS director should be non-intrusive to the running of pipelines.
The text was updated successfully, but these errors were encountered:
OpenEBS CI runs on GitLab and uses on-premise Kubernetes clusters setup with:
All the above clusters are running over Vitrual Machines hosted by MayaData.
The logs from the pipelines are currently being pushed to ECK cluster setup using OpenEBS Local PV. The E2e team maintainers manage the ECK cluster and will have to manage access to the logs to developers, as well as perform day 2 operations on ECK cluster - to manage the capacity.
The proposed solution is to make use of "Director On-prem" setup for managing the OpenEBS CI Kubernetes clusters and also grant access to OpenEBS developers to access the logs.
The text was updated successfully, but these errors were encountered: