Conversation
We're adding a service VM to support 2, work in progress, features in the OpenStack platform architecture. This VM runs 2 pods: A dnsmasq one and an haproxy one. The dnsmasq pod has been configured to serve the ETCD A and SRV records on the service VM, forwards requests to Neutron DNS and configures the bootstrap and master servers to use it. The haproxy pod has been configured to serve requests for the `api` hostname that the installer depends on. This VM is not meant to be put in production but rather allow for development to progress while the final architecture implementations for these 2 services are finished.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: flaper87 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@flaper87: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
See PR #904. Sorry for the overlap |
|
PR #904 merged so this can be closed. /close |
|
@russellb: Closed this PR. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
We're adding a service VM to support 2, work in progress, features in the OpenStack platform architecture. This VM runs 2 pods: A dnsmasq one and an haproxy one.
The dnsmasq pod has been configured to serve the ETCD A and SRV records on the service VM, forwards requests to Neutron DNS and configures the bootstrap and master servers to use it.
The haproxy pod has been configured to serve requests for the
apihostname that the installer depends on.This VM is not meant to be put in production but rather allow for development to progress while the final architecture implementations for these 2 services are finished.
/cc @tomassedovic
/assign @russellb @hardys