ceph / ceph/ceph-csi-operator

Helm: operator driverSpecDefaults not used as chart overrides values

Open
#576 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
63
Forks
59
Avg merge
1d 19h
Merged PRs (30d)
19

Description

# Describe the bug #

The driver charts include explicit configuration values which override those set in the operator's driverSpecDefaults. Changing values in driverSpecDefaults are therefore ignored as the driver already sets those values to the initial defaults.

# Environment details #

- Image/version of ceph-csi-operator : 1.0.4
- Image/version of Ceph-CSI driver : 3.17.0
- Kubernetes cluster version : 1.36.3
- Ceph cluster version : 20.2.1

# Steps to reproduce #

Steps to reproduce the behavior:

1. Create driver config including the following driverSpecDefaults:
```
operatorConfig:
driverSpecDefaults:
log:
rotation:
enabled: false
```

2. Leave the driver: {type} log fields unspecified (chart defaults)
2. Deploy the drivers
3. Examine the resulting Driver objects and see that log rotation is enabled in all of them.

# Additional context #

The driver chart values.yaml explicitly sets many of the values that are present in the driverSpecDefaults to the same values as present in the default driverSpecDefaults. If those values were commented out in chart, the drivers would get the same values on deployment, but the driverSpecDefaults could be used to override their defaults as expected.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the driver chart values.yaml files and compare their explicit defaults with the operator's driverSpecDefaults handling. Reproduce the deployment using log.rotation.enabled: false, then inspect the resulting Driver objects. Done means chart defaults no longer override values supplied through driverSpecDefaults while unspecified fields retain their defaults.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, helm, kubernetes
Domain
devops, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
66/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.