You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
doc for overriding public endpoints in the keystone catalog (#930)
* how to override public endpoints for keystone catalog commit 1
* how to override public endpoints for keystone catalog OSPC-809
* OSPC-809 modify the doc as per the feedback
* OSPC-809 modify the doc as per feedback
# Helm Overriding public endpoint fqdn openstack services
2
+
3
+
By default in Genestack the public endpoint fqdn for any openstack service is created with the cluster domain. For example if the cluster domain is "cluster.local" and keystone pods are in the "openstack" namespace then the fqdn for the keystone service would be "keystone-api.openstack.svc.cluster.local" which might not be ideal for production environments. There are examples provided in the documentation to override the domain for the [gateway api routes](https://docs.rackspacecloud.com/infrastructure-nginx-gateway-api-custom/#custom-routes); this however doesn't override the fqdn for the openstack services in the keystone catalog.
4
+
5
+
Below we will discuss how to override the public endpoint fqdn in the keystone catalog using helm values
6
+
7
+
# Providing the required overrides for public endpoints in the keystone catalog
8
+
9
+
In order to modify the public endpoint fqdn for any openstack service then helm overrides can be used; taking an example of keystone service.
10
+
11
+
This is the httproute for keystone service:
12
+
13
+
```shell
14
+
kubectl get httproute -n openstack custom-keystone-gateway-route-http
This although doesn't modify the public endpoint for the keystone service in the catalog; to modify the fqdn for the keystone service in the catalog we would need to create an helm overrides file:
20
+
21
+
```yaml
22
+
endpoints:
23
+
identity:
24
+
host_fqdn_override:
25
+
public:
26
+
tls: {}
27
+
host: keystone.cluster.local
28
+
port:
29
+
api:
30
+
public: 443
31
+
scheme:
32
+
public: https
33
+
```
34
+
35
+
this file needs to be moved into /etc/genestack/helm-configs/keystone/ directory and when installing the helm chart this will override the fqdn of the keystone service in the catalog.
36
+
37
+
!!! note
38
+
The fqdn in the httproute and helm overrides must be the same
39
+
40
+
This is an example overrides file for nova:
41
+
42
+
!!! example "`host_fqdn_overrides.yaml`"
43
+
44
+
``` yaml
45
+
endpoints:
46
+
compute:
47
+
host_fqdn_override:
48
+
public:
49
+
tls: {}
50
+
host: nova.cluster.local
51
+
port:
52
+
api:
53
+
public: 443
54
+
scheme:
55
+
public: https
56
+
compute_metadata:
57
+
host_fqdn_override:
58
+
public:
59
+
tls: {}
60
+
host: metadata.nova.cluster.local
61
+
port:
62
+
metadata:
63
+
public: 443
64
+
scheme:
65
+
public: https
66
+
compute_novnc_proxy:
67
+
host_fqdn_override:
68
+
public:
69
+
tls: {}
70
+
host: novnc.nova.cluster.local
71
+
port:
72
+
novnc_proxy:
73
+
public: 443
74
+
scheme:
75
+
public: https
76
+
```
77
+
78
+
!!! note
79
+
gateway-api handles tls encryption on public endpoints; it is not required to specify tls parameters in helm
0 commit comments