(feat): Extra Valkey config#44
Conversation
This PR implements the ability for users to supply additional configuration for Valkey. Any provided parameters are appended to default configuration required by the operator Signed-off-by: utdrmac <matthew.boehm@percona.com>
Signed-off-by: utdrmac <matthew.boehm@percona.com>
Signed-off-by: utdrmac <matthew.boehm@percona.com>
Signed-off-by: utdrmac <matthew.boehm@percona.com>
Signed-off-by: utdrmac <matthew.boehm@percona.com>
Signed-off-by: utdrmac <matthew.boehm@percona.com>
Signed-off-by: utdrmac <matthew.boehm@percona.com>
Signed-off-by: utdrmac <matthew.boehm@percona.com>
|
ugh. why didn't lint/fmt/vet catch those? |
jdheyburn
left a comment
There was a problem hiding this comment.
Minor comments, keen to hear opinions, otherwise LGTM
Signed-off-by: utdrmac <matthew.boehm@percona.com>
Signed-off-by: utdrmac <matthew.boehm@percona.com>
|
e2e still fails due to #43 |
no this is different issue than 43. its failing because of events limitation. maybe as u have added new emit event other events are not coming. https://github.com/valkey-io/valkey-operator/actions/runs/20936033780/job/60159472854?pr=44. check this PR description #37. maybe you can update events check accordingly. currently we are not asserting for all events due to events rate limit. |
|
I only added 1 new event which isn't triggered during the e2e. When I run e2e on my local kind cluster, I don't get that failure; I get the same failure as #43. |
no i don't think its related. you can check the issue description failure test case and logs are different for both of these errors. i have neven seen failure of valkey creation CR test case in main branch. if in case we are seeing, we need to create different issue. this PR is failing this test "Manager when a ValkeyCluster CR is applied [It] creates a Valkey Cluster deployment" 43 issue is with other test "Manager when a ValkeyCluster experiences degraded state [It] should detect and recover when a deployment is deleted" https://github.com/valkey-io/valkey-operator/actions/runs/20806446577/job/59761668293 quick fix: we may need to remove assertions of some of the events. valkey-operator/test/e2e/e2e_test.go Line 405 in 44d674b |
|
Rebasing (or add merge commit of main) should fix the e2e test now. |
Signed-off-by: utdrmac <matthew.boehm@percona.com>
Signed-off-by: utdrmac <matthew.boehm@percona.com>
Signed-off-by: utdrmac <matthew.boehm@percona.com>
|
Just an update, that I'm working on the minor changes requested above, but I'm getting golang crashes when building the docker image. |
Signed-off-by: utdrmac <matthew.boehm@percona.com>
bjosv
left a comment
There was a problem hiding this comment.
LGTM, just added a nit for the record.
Just a rebase needed, then open comments can be addressed in separate PR.
| // buildValkeyNodeConfigMap builds a ConfigMap containing the embedded liveness | ||
| // and readiness probe scripts, plus an empty valkey.conf. | ||
| // The ConfigMap is named after valkeyNodeResourceName(node). | ||
| // The ConfigMap is named via config.go:getConfigMapName(node). |
There was a problem hiding this comment.
nit: remove this line or change to GetServerConfigMapName, getConfigMapName was maybe used in a previous iteration.
Signed-off-by: utdrmac <matthew.boehm@percona.com>
Signed-off-by: utdrmac <matthew.boehm@percona.com>
|
@sandeepkunusoth Please check my merge with your latest TLS, as the config is moved into a separate file. |
Signed-off-by: utdrmac <matthew.boehm@percona.com>
Signed-off-by: utdrmac <matthew.boehm@percona.com>
…eyConfig Signed-off-by: Joseph Heyburn <jdheyburn@gmail.com>
|
@utdrmac I rebased this branch from main, looks like its causing some e2e tests to fail - would you mind taking a look? |
|
🎉 Thanks everyone for helping, commenting, and testing! |
The upstream sample YAML now includes spec.config (from valkey-io/valkey-operator#44), which the chart's CRDs did not know about, causing a strict decoding error. Sync CRDs from the latest operator main and replace the remote sample link in NOTES.txt with an inline example that won't drift. Signed-off-by: Daan Vinken <daanvinken@tythus.com> Signed-off-by: Daan Vinken <dvinken@tesla.com>
The upstream sample YAML now includes spec.config (from valkey-io/valkey-operator#44), which the chart's CRDs did not know about, causing a strict decoding error. Sync CRDs from the latest operator main and replace the remote sample link in NOTES.txt with an inline example that won't drift. Signed-off-by: Daan Vinken <daanvinken@tythus.com>

This feature request implements the ability for users to supply their own configuration for Valkey as an inline stanza when deploying a new cluster. The user configuration is appended to the required base configuration, which is created as a configMap. Since the operator manages the configMap, any changes to the config are reconciled. Additionally, users cannot override the required cluster settings.