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
refactor pkg/redis. It works fine and it was written with Redis Sentinel in mind but it is worth reviewing the implementation in order to make it less coupled internally and more testable and transparent.
loose control over created resources, especially StatefulSet. Current approach cherry picks bits from the StatefulSet spec and it makes sense to turn Redis CRD into a thin StatefulSet wrapper to give end users more control over the generated StatefulSet hence Pods and containers (Support for initialDelaySeconds and init containers amaizfinance/redis-operator#9 is an example feature request and it is clear that it is not the last. Other kubernetes operators dealing with the same problem end up with a messed API. Feel free to look at the most popular operators, their type definitions and requests to add missing container and Pod Spec fields and you will understand what I mean).
remove redis exporter container. There are different scenarios of gathering metrics, and side-container pattern is just one of them. Provide a short instruction on how to connect an exporter.
replace Drone CI with github actions AND gitlab CI.
synchronize main branch between gitlab and github.
replace Docker Hub with Gitlab Container Registry and Github container registry.
replace bazel with kaniko for building container images and native go build command. Reason: bazel configuration does not seem to "age" well providing an extra layer of maintenance. Reproducability of builds stays as a requirement.
This list is subject to be extended. Discussion is open. Any feedback is welcome!
The text was updated successfully, but these errors were encountered:
From amaizfinance/redis-operator#12:
This is an umbrella issue to hold a checklist of tasks for a
v1
release.go build
command. Reason: bazel configuration does not seem to "age" well providing an extra layer of maintenance. Reproducability of builds stays as a requirement.This list is subject to be extended. Discussion is open. Any feedback is welcome!
The text was updated successfully, but these errors were encountered: