Explore creating a new valkey package to replace dev-redis
#97
Assignees
Labels
Comments
5 tasks
Racer159
added a commit
to defenseunicorns/uds-package-valkey
that referenced
this issue
Jun 12, 2024
## Description This initializes the repository to create a UDS Package Valkey ## Related Issue Fixes defenseunicorns/uds-package-gitlab#97 ## Type of change - [ ] Bug fix (non-breaking change which fixes an issue) - [X] New feature (non-breaking change which adds functionality) - [X] Other (security config, docs update, etc) ## Checklist before merging - [X] Test, docs, adr added or updated as needed - [X] [Contributor Guide Steps](https://github.com/defenseunicorns/uds-package-valkey/blob/main/CONTRIBUTING.md#developer-workflow) followed --------- Co-authored-by: zamaz <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe what should be investigated or refactored
We should explore creating a new
valkeypackage to replace dev-redis so that we have a better, more prod-like base to test on (similar to the postgres operator swap #96 )Links to any relevant code
uds-package-gitlab/bundle/uds-bundle.yaml
Line 18 in e0972cb
Additional context
This valkey package will likely not be the main focus but we should ensure that it is reasonably well tested since it is currently trying to be used.
We should make sure this doesn't bump us to needing a higher spec runner (including leaving enough headroom for the gitlab runner)
This is also blocked on Valkey becoming a viable fork of redis: https://www.linuxfoundation.org/press/linux-foundation-launches-open-source-valkey-community
The text was updated successfully, but these errors were encountered: