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

Aperta
  • Qualcosa non va?
#1,884 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
1-2 giorni
Idoneità per principianti
52/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go, kubernetes
Ambito
infrastructure

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
Go
Stelle
260
Fork
134
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di splunk/splunk-operator

Tutte le issue di splunk/splunk-operator

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.