fdb-kubernetes-operator
fdb-kubernetes-operator copied to clipboard
FoundationDB
A kubernetes operator for FoundationDB
Currently the `chooseRemovals` reconciler "only" evaluates the locality distribution. I think it would also make sense to take the different process conditions into account e.g. we should prefer to remove...
We've added support for using the unified foundationdb-kubernetes image in the main server pods. We should also allow using this image in the backup pods as well, so we only...
The feature to specify an IP family to select from the PodIPs list does not work with the unified image. We should add support for this mechanism.
There are cases where a user may want to have custom parameters that substitute variables from the environment, such as for populating custom locality fields. The old split image supports...
We currently customize the monitor conf for the unified image with different flags based on how many storage servers we are running per disk. This adds some complexity, because we...
The new unified image has a different default user ID than the old split image. This may cause problems in the transition, if the new user cannot access files written...
Once we have a stable version for the new unified image, we should make it the default image type in the unit tests, and mark it as a future default...
We had a question in the forums about how to use the `RoutingConfig` options: https://forums.foundationdb.org/t/how-to-use-routingconfig-with-fdb-operator/3069. We should expand our documentation to address these questions.
Once we believe the unified image mode is stable, we should remove the warnings about it being experimental in our documentation.
Instead of using the `processGroupsToRemove ` and `processGroupsToRemoveWithoutExclusion ` a user should directly target the desired `FoundationDBProcessGroup` and set the `remove` flag there. This should trigger an exclusion and once...