Configure ingress controller in kubernetes clusters

[Ricardo Rocha]

Allow enabling by default an ingress controller in kubernetes clusters.

There are multiple backend options, traefik, nginx, octavia based, etc. Make it configurable at the cluster level so that Magnum can offer multiple options, and leave it up to the users and/or operators to specify which backend supports the clusters.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/528756

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/528756
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=0b18989a50ec7c7323d23f5e84c94dda70363fba
Submitter: Zuul
Branch: master

commit 0b18989a50ec7c7323d23f5e84c94dda70363fba
Author: Ricardo Rocha <email address hidden>
Date: Mon Dec 18 16:31:30 2017 +0000

    [kubernetes] add ingress controller

    Add ingress controller configuration and backend to kubernetes clusters.

    A new label 'ingress_controller' defines which backend should serve
    ingress, with traefik added as the only option for now.

    It is defined as a DaemonSet, with instances on all nodes defined with a
    certain role. This role is set as an additional cluster label
    'ingress_controller_role', with a default value of 'ingress'.

    For now no node is automatically set with this role, with users or operators
    having to do this manually after cluster creation.

    Change-Id: I5175cf91f37e2988dc3d33042558d994810842f3
    Closes-Bug: #1738808

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/queens
Review: https://review.openstack.org/547136

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/547136
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=5d0d7c31a69853db7a5b4b0e6893c34841ba464c
Submitter: Zuul
Branch: stable/queens

commit 5d0d7c31a69853db7a5b4b0e6893c34841ba464c
Author: Ricardo Rocha <email address hidden>
Date: Mon Dec 18 16:31:30 2017 +0000

    [kubernetes] add ingress controller

    Add ingress controller configuration and backend to kubernetes clusters.

    A new label 'ingress_controller' defines which backend should serve
    ingress, with traefik added as the only option for now.

    It is defined as a DaemonSet, with instances on all nodes defined with a
    certain role. This role is set as an additional cluster label
    'ingress_controller_role', with a default value of 'ingress'.

    For now no node is automatically set with this role, with users or operators
    having to do this manually after cluster creation.

    Change-Id: I5175cf91f37e2988dc3d33042558d994810842f3
    Closes-Bug: #1738808
    (cherry picked from commit 0b18989a50ec7c7323d23f5e84c94dda70363fba)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/magnum 6.1.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/magnum 7.0.0 release.