[tlse] enable galera tls for internal TLS #678
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Create cert for galera instance and configure the instance to use it. Galera will always be configured to support TLS as its on the DB user level if TLS will be enforced or not. Jira: OSPRH-2440
stuggi
requested review from
olliewalsh,
dciabrin and
Deydra71
and removed request for
lewisdenny
Deydra71
approved these changes
Feb 19, 2024
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Deydra71, stuggi The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-merge-bot
bot
merged commit 528d9fa
into
openstack-k8s-operators:main
7 checks passed
|
I could not test it locally, but from my previous work on the mariadb-operator, the certificate created for galera should populate the 'organization' field, otherwise this trip the SST transfer setup done by wsrep_sst_rsync. This will not show at the initial deployment because there is no SST involved when the DB is bootstrapped as there are no data to be transferred yet. |
stuggi
added a commit
to stuggi/openstack-operator
that referenced
this pull request
Apr 9, 2024
From comment on openstack-k8s-operators#678 (comment) ~~~ The certificate created for galera should populate the 'organization' field, otherwise this trip the SST transfer setup done by wsrep_sst_rsync. This will not show at the initial deployment because there is no SST involved when the DB is bootstrapped as there are no data to be transferred yet. ~~~ Jira: OSPRH-2440
stuggi
added a commit
to stuggi/openstack-operator
that referenced
this pull request
Apr 9, 2024
From comment on openstack-k8s-operators#678 (comment) ~~~ The certificate created for galera should populate the 'organization' field, otherwise this trip the SST transfer setup done by wsrep_sst_rsync. This will not show at the initial deployment because there is no SST involved when the DB is bootstrapped as there are no data to be transferred yet. ~~~ Jira: OSPRH-2440
stuggi
added a commit
to stuggi/openstack-operator
that referenced
this pull request
Apr 9, 2024
From comment on openstack-k8s-operators#678 (comment) ~~~ The certificate created for galera should populate the 'organization' field, otherwise this trip the SST transfer setup done by wsrep_sst_rsync. This will not show at the initial deployment because there is no SST involved when the DB is bootstrapped as there are no data to be transferred yet. ~~~ Jira: OSPRH-2440
stuggi
added a commit
to stuggi/openstack-operator
that referenced
this pull request
Apr 10, 2024
From comment on openstack-k8s-operators#678 (comment) ~~~ The certificate created for galera should populate the 'organization' field, otherwise this trip the SST transfer setup done by wsrep_sst_rsync. This will not show at the initial deployment because there is no SST involved when the DB is bootstrapped as there are no data to be transferred yet. ~~~ Jira: OSPRH-2440
stuggi
added a commit
to stuggi/openstack-operator
that referenced
this pull request
Apr 11, 2024
From comment on openstack-k8s-operators#678 (comment) ~~~ The certificate created for galera should populate the 'organization' field, otherwise this trip the SST transfer setup done by wsrep_sst_rsync. This will not show at the initial deployment because there is no SST involved when the DB is bootstrapped as there are no data to be transferred yet. ~~~ Jira: OSPRH-2440
stuggi
added a commit
to stuggi/openstack-operator
that referenced
this pull request
Apr 12, 2024
From comment on openstack-k8s-operators#678 (comment) ~~~ The certificate created for galera should populate the 'organization' field, otherwise this trip the SST transfer setup done by wsrep_sst_rsync. This will not show at the initial deployment because there is no SST involved when the DB is bootstrapped as there are no data to be transferred yet. ~~~ Jira: OSPRH-2440
stuggi
added a commit
to stuggi/openstack-operator
that referenced
this pull request
Apr 24, 2024
From comment on openstack-k8s-operators#678 (comment) ~~~ The certificate created for galera should populate the 'organization' field, otherwise this trip the SST transfer setup done by wsrep_sst_rsync. This will not show at the initial deployment because there is no SST involved when the DB is bootstrapped as there are no data to be transferred yet. ~~~ Jira: OSPRH-2440
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Create cert for galera instance and configure the instance to use it. Galera will always be configured to support TLS as its on the DB user level if TLS will be enforced or not.
Jira: OSPRH-2440