Steve Wilkerson 74f3eb5824 Ingress: Move ingress objects back to the extensions api
This updates the ingress objects to move them back to the
extensions API.  While 1.16 moves them under the networking
api, they're still rendered and deployed as extensions/ objects.
This move prevents issues from arising where older versions of
kubernetes might still be deployed during an upgrade, as the
move to the networking API is nonfunctional at this time

Change-Id: I814bbc833b5b9f79f34aefc60b9c1f9890bca826
Signed-off-by: Steve Wilkerson <sw5822@att.com>
2019-10-28 21:31:06 +00:00
2019-10-10 15:47:20 +08:00
2019-10-23 19:16:28 +00:00
2019-10-23 19:16:28 +00:00
2019-10-21 18:27:41 +00:00
2019-10-21 18:27:41 +00:00
2019-09-11 12:46:34 +04:00
2019-04-19 19:34:11 +00:00
2019-02-27 15:02:06 +08:00
2018-05-15 13:04:28 -05:00

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
Helm charts for deploying OpenStack on Kubernetes
Readme 126 MiB
Languages
Smarty 82.3%
Shell 16%
Python 1.3%
Jinja 0.2%
Makefile 0.2%