Splunk Operator: 3.1.0 ruins configuration for LM

[wzhiana]

Please select the type of request

Bug

Tell us more

Describe the request
splunk-operator 3.1.0 ruins LM with ephemeral storage.

we had config:

"etcVolumeStorageConfig" = {
  "ephemeralStorage" = true
 }
"varVolumeStorageConfig" = {
   "ephemeralStorage" = true
}

then when we updated splunk-operator controller and crd's - all were fine till we updated license.
as we wanted to install new license, we updated secret and restarted terraform.
but it failed with:

Error: API response status: Failure

  with kubernetes_manifest.splunk_licensemanager,
  on splunk-licensemanager.tf line 109, in resource "kubernetes_manifest" "splunk_licensemanager":
 109: resource "kubernetes_manifest" "splunk_licensemanager" {

LicenseManager.enterprise.splunk.com "prod" is invalid:
[spec.varVolumeStorageConfig: Invalid value: "object": no such key:
storageClassName evaluating rule: storageClassName and ephemeralStorage are
mutually exclusive, spec.varVolumeStorageConfig: Invalid value: "object": no
such key: storageCapacity evaluating rule: storageCapacity and
ephemeralStorage are mutually exclusive, spec.etcVolumeStorageConfig: Invalid
value: "object": no such key: storageClassName evaluating rule:
storageClassName and ephemeralStorage are mutually exclusive,
spec.etcVolumeStorageConfig: Invalid value: "object": no such key:
storageCapacity evaluating rule: storageCapacity and ephemeralStorage are
mutually exclusive]

Error: Kubernetes API Error: Invalid LicenseManager.enterprise.splunk.com [prod]

  with kubernetes_manifest.splunk_licensemanager,
  on splunk-licensemanager.tf line 109, in resource "kubernetes_manifest" "splunk_licensemanager":
 109: resource "kubernetes_manifest" "splunk_licensemanager" {


Error: spec.varVolumeStorageConfig

  with kubernetes_manifest.splunk_licensemanager,
  on splunk-licensemanager.tf line 109, in resource "kubernetes_manifest" "splunk_licensemanager":
 109: resource "kubernetes_manifest" "splunk_licensemanager" {

Invalid value: "object": no such key: storageClassName evaluating rule:
storageClassName and ephemeralStorage are mutually exclusive

Error: spec.varVolumeStorageConfig

  with kubernetes_manifest.splunk_licensemanager,
  on splunk-licensemanager.tf line 109, in resource "kubernetes_manifest" "splunk_licensemanager":
 109: resource "kubernetes_manifest" "splunk_licensemanager" {

Invalid value: "object": no such key: storageCapacity evaluating rule:
storageCapacity and ephemeralStorage are mutually exclusive

Error: spec.etcVolumeStorageConfig

  with kubernetes_manifest.splunk_licensemanager,
  on splunk-licensemanager.tf line 109, in resource "kubernetes_manifest" "splunk_licensemanager":
 109: resource "kubernetes_manifest" "splunk_licensemanager" {

Invalid value: "object": no such key: storageClassName evaluating rule:
storageClassName and ephemeralStorage are mutually exclusive

Error: spec.etcVolumeStorageConfig

  with kubernetes_manifest.splunk_licensemanager,
  on splunk-licensemanager.tf line 109, in resource "kubernetes_manifest" "splunk_licensemanager":
 109: resource "kubernetes_manifest" "splunk_licensemanager" {

Invalid value: "object": no such key: storageCapacity evaluating rule:
storageCapacity and ephemeralStorage are mutually exclusive

Looks like in new version something is broken.

Expected behavior
It should work like it was before 3.1.0

Splunk setup on K8S

• not related

Reproduction/Testing steps

• upgrade to 3.1.0 and update license
  K8s environment
• Useful information about the K8S environment being used. Eg. version of K8s, kind of K8s cluster etc..

Proposed changes(optional)

• Proposed change, if any.

K8s collector data(optional)

• Please provide data collected from the K8s collectors, if any.

Additional context(optional)

• Add any other context about the problem here.

[kasiakoziol]

Hello @yaroslav-nakonechnikov
Thanks for raising the issue. @patrykw-splunk has already implemented a fix for that (#1857) and we are actively working on moving the fix forward.
Meantime, to unblock you, we would recommend to install fixed CRDs (present in the PR and soon on the develop branch) with CEL validation failure addressed.
Best regards,
SOK Team

[wzhiana]

splunk/splunk-ansible#826