992e82fc1dbcca989f171b7679cee96a924259de
The way that the minikube K8s script orders a host's resolv.conf file leaves service endpoints inaccessible from the host itself even though they are accessible within the cluster, leaving the OpenStack client unusable from the minikube node. This change resolves the service access issues by reordering the DNS entries in the host's resolv.conf file. Change-Id: I58bf6d541e59f3049a0e350291e07241f6a6b544 Signed-off-by: Drew Walters <andrew.walters@att.com>
Openstack-Helm-Infra
Mission
The goal of OpenStack-Helm-Infra is to provide charts for services or integration of third-party solutions that are required to run OpenStack-Helm.
For more information, please refer to the OpenStack-Helm repository.
Communication
- Join us on Slack - #openstack-helm
- Join us on IRC: #openstack-helm on freenode
- Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-4 on freenode
- Meeting Agenda Items: Agenda
Launchpad
Bugs and blueprints are tracked via OpenStack-Helm's Launchpad. Any bugs or blueprints filed in the OpenStack-Helm-Infra Launchpad will be closed and requests will be made to file them in the appropriate location.
Description
Languages
Smarty
81%
Shell
17.1%
Python
1.4%
Jinja
0.3%
Makefile
0.2%