Error when starting kurrentdb in k8s with service description

[thoraage]

Describe the bug
I try to deploy kurrentdb locally in k8s (minikube) for testing and POC purposes. See description used under K8s description for pod and service. I get the error, included under Log output below, when I start kurrentdb with k8s service descriptor. Without a service descriptor I get no error.

To Reproduce
Steps to reproduce the behavior:

1. Start minikube with minikube start
2. Apply k8s-description from Additional context: kubectl apply -f description.yaml
3. Check log with kubectl logs kurrentdb

Expected behavior
Expected kurrentdb to start without problems.

Actual behavior
Kurrentdb crashed during startup with reference to arguments not used in description.

Config/Logs/Screenshots

K8s description for pod and service

apiVersion: v1
kind: Pod
metadata:
  name: kurrentdb
  labels:
    app: kurrentdb
spec:
  containers:
    - name: kurrentdb
      image: kurrentplatform/kurrentdb:25.1.0-x64-8.0-bookworm-slim
      ports:
        - containerPort: 1113
        - containerPort: 2113
      env:
        - name: EVENTSTORE_CLUSTER_SIZE
          value: "1"
        - name: EVENTSTORE_RUN_PROJECTIONS
          value: "All"
        - name: EVENTSTORE_START_STANDARD_PROJECTIONS
          value: "true"
        - name: EVENTSTORE_NODE_PORT
          value: "2113"
        - name: EVENTSTORE_INSECURE
          value: "true"
        - name: EVENTSTORE_ENABLE_ATOM_PUB_OVER_HTTP
          value: "true"
  restartPolicy: Always
---
apiVersion: v1
kind: Service
metadata:
  name: kurrentdb
  labels:
    app: kurrentdb
spec:
  selector:
    app: kurrentdb
  type: ClusterIP   # default, only accessible inside the cluster
  ports:
    - name: http
      port: 2113
      targetPort: 2113

Log output

...
      > [kurrentdb kurrentdb] [    1, 1,09:57:35.018,FTL] KurrentDB                      The option ServicePortHttp is not a known option.
      > [kurrentdb kurrentdb] [    1, 1,09:57:35.018,FTL] KurrentDB                      The option ServicePort is not a known option.
      > [kurrentdb kurrentdb] [    1, 1,09:57:35.018,FTL] KurrentDB                      The option ServiceHost is not a known option.
      > [kurrentdb kurrentdb] [    1, 1,09:57:35.018,FTL] KurrentDB                      The option Port2113TcpProto is not a known option.
      > [kurrentdb kurrentdb] [    1, 1,09:57:35.018,FTL] KurrentDB                      The option Port2113TcpPort is not a known option.
      > [kurrentdb kurrentdb] [    1, 1,09:57:35.018,FTL] KurrentDB                      The option Port2113TcpAddr is not a known option.
      > [kurrentdb kurrentdb] [    1, 1,09:57:35.018,FTL] KurrentDB                      The option Port2113Tcp is not a known option.
      > [kurrentdb kurrentdb] [    1, 1,09:57:35.018,FTL] KurrentDB                      The option Port is not a known option. Did you mean Log?
      > [kurrentdb kurrentdb] [    1, 1,09:57:35.018,FTL] KurrentDB                      Found unknown options. To continue anyway, set AllowUnknownOptions to true.
      > [kurrentdb kurrentdb] [    1, 1,09:57:35.019,INF] KurrentDB                      Use the --help option in the command line to see the full list of KurrentDB configuration options.
 - pods failed. Error: container kurrentdb terminated with exit code 1.

KurrentDB details

• KurrentDB server version:
  kurrentplatform/kurrentdb:25.1.0-x64-8.0-bookworm-slim
• Operating system:
  Linux (6.8.0-86-generic subscriptions doesn't work (using cluster nodes) if last node alive wasn't master #87-Ubuntu SMP PREEMPT_DYNAMIC)
• KurrentDB client library and version (if applicable):
  Not applicable

Additional context
I'm able to work around this by starting the pod first; and then the create the service.

[linear]

DB-1735

[timothycoleman]

Hi @thoraage, kurrentdb looks for environment variables that begin KURRENTDB_ (and also EVENTSTORE_ for backwards compatibility). I think your environment is likely adding keys with that prefix because of the name of the container/pod. Could you try a different name and see if that solves it. Thanks

[thoraage]

I tried to change the names and that works! That's great; thanks for the help!

The one triggering the fault seem to be the the service name. However, I will contest that this is something specific to my environment. I believe that kurrentdb in some way creates this.

Did you try to reproduce it using my description? I had a colleague try it and he got the same error.

[timothycoleman]

Hi @thoraage, sorry by 'your environment' I just meant kubernetes rather than something more specific to your set up

[thoraage]

No problem, but it is really weird that existence of a Service named kurrentdb should trigger this.