Update .spec.configuration API changes

[obaydullahmhs]

No description provided.

[github-actions]

Visit the preview URL for this PR (updated for commit 417244e):

https://kubedb-v2-hugo--pr840-reconfig-vddkg1cf.web.app

_{(expires Fri, 06 Feb 2026 12:31:19 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 0f29ae8ae0bd54a99bf2b223b6833be47acd5943}

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
25884160	Triggered	Generic Password	f670872	docs/guides/clickhouse/concepts/clickhouse.md.bak	View secret
25884161	Triggered	Username Password	f670872	docs/guides/cassandra/concepts/cassandra.md.bak	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[ArnobKumarSaha]

Whats remaining here ?

[refat75]

File: docs/guides/mariadb/reconfigure/cluster/index.md
Line: 374

There's a line like:

If everything goes well, `KubeDB` Enterprise operator will update the `configSecret` of `MariaDB` object.

For applyConfig we don't update the configSecret of DB object. Rather we update the configuration.inline field of DB object.

Maybe it can be rewritten as:

If everything goes well, `KubeDB` operator will update the `configuration` field  of `MariaDB` object.

Any thought on this?
@souravbiswassanto @sheikh-arman @Neaj-Morshad-101

[Neaj-Morshad-101]

why redis in proxysql?

[Neaj-Morshad-101]

@Bonusree Can you check this?

[souravbiswassanto]

At first, you have to create a secret with custom configuration file in it and provide its name in spec.configuration.secretName. The operator reads this Secret internally and applies the configuration automatically.