Splunk Operator: Certificate Management does not apply Splunk-managed roles

Abierto
  • ¿Algo no está bien?
#1,884 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
1-2 días
Aptitud para principiantes
52/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go, kubernetes
Área
infrastructure

Línea de trabajo

Start by tracing Certificate Management for the certs entries in the Standalone custom resource and how each role is translated into Splunk configuration; the issue does not name implementation files or tests. Reproduce with the supplied manifest using server and input roles, then check whether Splunk configuration uses the mounted certificates. Done means the configured roles make Splunk use those certificates.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Please select the type of request

Bug

Tell us more

Describe the request
The newly introduced Certificate Management does not actually set up any configuration within Splunk to actually use the mounted certificates, although option roles has been set.

Expected behavior

  • Certificates get created using the specified Issuer (works)
  • Certificate are mounted within the pod (works)
  • Splunk configuration is adjusted to use the certificates (doesn't work)

Splunk setup on K8S
SOK 3.2.0

Reproduction/Testing steps
Example deployment:

apiVersion: enterprise.splunk.com/v4
kind: Standalone
metadata:
  name: s1
  namespace: splunk-example-a
  finalizers:
  - enterprise.splunk.com/delete-pvc
spec:
  extraEnv:
    - name: TZ
      value: Europe/Berlin
  varVolumeStorageConfig:
    storageCapacity: 10Gi
  certs:
    - secretRef:
        name: s1-server-cert
      role: server
      issuerRef:
        name: cluster-ca-issuer
        kind: ClusterIssuer
    - secretRef:
        name: s1-input-cert
      role: input
      issuerRef:
        name: cluster-ca-issuer
        kind: ClusterIssuer

Initially, we had the following configuration in place. We removed it to make sure that this doesn't trigger the issue, but behaviour didn't change:

  defaults: |-
    splunk:
      http_enableSSL: true

K8s environment
k8s v1.36.4
Managed SKE Cluster on StackIT

Lenguaje dominante
Go
Estrellas
260
Forks
134
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de splunk/splunk-operator

Todos los issues de splunk/splunk-operator

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.