Skip to content

Fix MaxScale securityContext UID and widen ProxySQL backend AppBinding filter - #1182

Merged
ArnobKumarSaha merged 1 commit into
masterfrom
arnob-mxs-be
Sep 18, 2026
Merged

ArnobKumarSaha merged 1 commit into
masterfrom
arnob-mxs-be

Conversation

@ArnobKumarSaha

Copy link
Copy Markdown
Member

MariaDB MaxScale (kubedbcom-mariadb-editor-options)

MaxScale runs as uid 997, not 999. Added a maxscale.container.securityContext helper and changed the MaxScale pod fsGroup default; MariaDB and its sidecars keep 999. The spec.openshift.securityContext.runAsUser override still takes precedence.

ProxySQL backend (kubedbcom-proxysql-editor-options)

getAppBindings() only listed kubedb.com/mysql AppBindings. ProxySQL can also front MariaDB and PerconaXtraDB, so the filter now accepts kubedb.com/mariadb and kubedb.com/perconaxtradb.

Verified with helm template charts/kubedbcom-mariadb-editor-options --set spec.mode=MariaDBReplication: MaxScale renders 997, MariaDB 999.

…g filter

MaxScale runs as uid 997, not 999; give it its own container securityContext
helper and pod fsGroup default.

ProxySQL can route to MariaDB and PerconaXtraDB backends, so the backend
AppBinding dropdown now accepts those types in addition to MySQL.

Signed-off-by: Arnob kumar saha <arnob@appscode.com>
@ArnobKumarSaha
ArnobKumarSaha merged commit de962d0 into master Sep 18, 2026
4 checks passed
@ArnobKumarSaha
ArnobKumarSaha deleted the arnob-mxs-be branch September 18, 2026 13:52
@ArnobKumarSaha

Copy link
Copy Markdown
Member Author

maxscale 997 part is done here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant