This file defines a Custom Resource example for IPC (Inter-Process Communication) configuration in the eevee.bot/v1 API. It shows how to configure a bot named “my-eevee-bot” to use NATS as its messaging system with settings such as:

  • Managed NATS deployment through eevee-operator
  • NATS container image specification
  • Automatic token generation for authentication
  • Reference to Kubernetes secrets for secure token storage

The example demonstrates how to configure NATS as the messaging system for eevee.bot with managed deployment and authentication.

  ---
apiVersion: eevee.bot/v1
kind: IpcConfig
metadata:
  name: my-eevee-bot
  namespace: my-eevee-bot
spec:
  # Only NATS is supported for now
  nats:
    # Options for eevee-operator managed NATS
    managed:
      # Should the eevee-operator deploy a NATS server for us?
      enabled: true
      # NATS container image to use
      image: docker.io/nats:latest
    # Options for NATS token auth
    token:
      # Should the eevee-operator generate a token for NATS auth?
      generate: true
      # Where to access the NATS auth token
      secretKeyRef:
        secret:
          name: my-irc-network-secrets
        key: token

Specification

Managed NATS Properties

image (string)

NATS container image to use (e.g. docker.io/nats:latest)

imagePullPolicy (string, optional)

Image pull policy for the NATS container. One of Always, IfNotPresent, Never. Default: IfNotPresent

resources (object, optional)

Standard Kubernetes resource requests and limits for the NATS container (CPU, memory, etc.). Accepts a standard Kubernetes V1ResourceRequirements object. If not specified, the container runs with default limits.