v0.0.18

This release adds the ability to overwrite the Cluster Operator's default valkey.conf file using the inline valkeyConfig.rawConfig option.

Here's an usage example:

resource "kubernetes_manifest" "valkey" {
  manifest = {
    "apiVersion" = "cache.halter.io/v1alpha1"
    "kind"       = "ValkeyCluster"
    "metadata" = {
      "name"    = var.name
      namespace = var.namespace
    }
    "spec" = {
      image      = "ghcr.io/halter/valkey:8.0.2"
      "valkeyConfig" = {
        "rawConfig" = <<-EOT
        port 6379
        cluster-enabled yes
        cluster-config-file nodes.conf
        cluster-node-timeout 5000
        appendonly yes
        protected-mode no
        cluster-preferred-endpoint-type ip
        maxmemory 12mb
        EOT
      }
    }
  }
}

What's Changed

• Add support for providing a custom Valkey configuration by @marcus-crane in #14

Full Changelog: v0.0.17...v0.0.18