12.0.4 NodePort master realm login error

Configuring the server
1

I run 12.0.4 on local k8s cluster exposed through NodePort. This is my StatefulSet manifest:

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: keycloak
  labels:
    component: keycloak
    app: keycloak
spec:
  serviceName: svc-keycloak
  podManagementPolicy: "OrderedReady"
  replicas: 1
  updateStrategy:
    type: RollingUpdate
  selector:
    matchLabels:
      component: keycloak
      app: keycloak
  template:
    metadata:
      labels:
        component: keycloak
        app: keycloak
    spec:
      terminationGracePeriodSeconds: 10
      imagePullSecrets:
      - name: imagepullsecret
      containers:
      - name: keycloak
        image: myregistry/keycloak:12.0.4
        imagePullPolicy: IfNotPresent
        env:
        - name: KEYCLOAK_USER
          value: admin
        - name: KEYCLOAK_PASSWORD
          value: admin
        ports:
        - containerPort: 8080
          name: http
          protocol: TCP
        - containerPort: 8443
          name: https
          protocol: TCP
        readinessProbe:
          httpGet:
            path: /auth/realms/master
            port: 8080
            scheme: HTTP
          initialDelaySeconds: 30
          periodSeconds: 10
          timeoutSeconds: 30
          failureThreshold: 3
          successThreshold: 1
        resources: {}
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File

This is my NodePort service:

apiVersion: v1
kind: Service
metadata:
  name: svc-keycloak-nodeport
  labels:
    component: keycloak
    app: keycloak
spec:
  ports:
  - name: http
    nodePort: 30340
    port: 8080
    protocol: TCP
    targetPort: 8080
  type: NodePort
  selector:
    app: keycloak

Login bumps into the following error:

03:29:45,590 WARN [org.keycloak.events] (default task-5) type=LOGIN_ERROR, realmId=master, clientId=null, userId=null, ipAddress=10.244.0.1, error=expired_code, restart_after_timeout=true, authSessionParentId=74ebff86-6353-47f2-a52a-94880d29963b, authSessionTabId=rHhmOPKyJ4I

How to fix it?