Skip to content

Commit 334b663

Browse files
committed
vault: Use internal FQDN for barbican -> Vault communication
Typically the certificate is only valid for the FQDN. This will not cause a problem usually because the internal API generally uses the VIP directly rather than an FQDN.
1 parent 738a9c5 commit 334b663

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

doc/source/configuration/vault.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -351,7 +351,7 @@ Configure Barbican
351351
enabled_secretstore_plugins=vault_plugin
352352
353353
[vault_plugin]
354-
vault_url = https://{{ kolla_internal_vip_address }}:8200
354+
vault_url = https://{{ kolla_internal_fqdn }}:8200
355355
use_ssl = True
356356
{% raw %}
357357
ssl_ca_crt_file = {{ openstack_cacert }}

etc/kayobe/environments/ci-multinode/kolla/config/barbican.conf

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ enable_multiple_secret_stores=false
55
enabled_secretstore_plugins=vault_plugin
66

77
[vault_plugin]
8-
vault_url = https://{{ kolla_internal_vip_address }}:8200
8+
vault_url = https://{{ kolla_internal_fqdn }}:8200
99
use_ssl = True
1010
{% raw %}
1111
ssl_ca_crt_file = {{ openstack_cacert }}

0 commit comments

Comments
 (0)