vitess-operator
vitess-operator copied to clipboard
planetscale
Kubernetes Operator for Vitess
Consistently got this error event when trying to startup a vitess cluster on GKE Autopilot running k8s v1.22.10 and vitess 14.0.1, tried both operator version 2.7.1 and 2.7.2 both failed....
In k8s 1.21+, bounded service account token are enfoced which requries a different prefix for service account token mounts, and are not removed in `reconcile_subcontroller.go`. My patch fixes the issue...
When configured backup, backup parameters not added to vtcld pods **Product version** Vitess version 14.0.1 Operator version 2.7.2 **Problem** backup arguments are not added by operator to vtcld pods it...
## Description Adding a rolling update strategy bundled in VTop out of the box will be a nice feature to have. It will fix some of the issues that users...
## Description Make sure to update the kubernetes version list for the VTop and make sure it works with the latest versions.
## Feature Supporting backups which can be scheduled to run later or on a schedule.
## Description There are a few things that can be cleaned up in VTop - - Cleaner separation of vitess layer and k8s layer - Directory restructure (operator-framework dependency has...
## Description We would need to fix VTAdmin deployment once we have made the change to VTAdmin to be running as a single binary.
## Description We should look at improving operator docs and autogenerating some of them
## Description We should add some automation that helps us do the release of rc-1.