Skip to content

Enable database TLS on 2025.1#2245

Draft
seunghun1ee wants to merge 2 commits intostackhpc/2025.1from
enable-database-tls
Draft

Enable database TLS on 2025.1#2245
seunghun1ee wants to merge 2 commits intostackhpc/2025.1from
enable-database-tls

Conversation

@seunghun1ee
Copy link
Copy Markdown
Member

Upstream Kolla-Ansible backported ProxySQL 3.0.x to 2025.1 release.
https://review.opendev.org/c/openstack/kolla-ansible/+/974712
https://review.opendev.org/c/openstack/kolla/+/974429

ProxySQL 3.0.x has a fix for the bug sysown/proxysql#4877 which prevented using TLS between database and ProxySQL.
Re-enable Database TLS and add tasks for creating certificates for ProxySQL.

Note: Two variables database_enable_tls_internal and database_enable_tls_backend have default value true but these are still explicitly set to true to ensure existing systems can also get effect.

@seunghun1ee seunghun1ee self-assigned this Mar 31, 2026
@seunghun1ee seunghun1ee requested a review from a team as a code owner March 31, 2026 15:34
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request enables internal and backend database TLS by upgrading ProxySQL to version 3.0.x and adding the necessary certificate generation tasks. A review comment identifies a hardcoded path in the root CA copy task that should be parameterized with the stackhpc_ca_secret_store variable to support different secret store backends.

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