Configure ingress controller in kubernetes clusters

Bug #1738808 reported by Ricardo Rocha
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
Undecided
Spyros Trigazis

Bug Description

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.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to magnum (master)

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

Changed in magnum:
assignee: nobody → Ricardo Rocha (rocha-porto)
status: New → In Progress
Changed in magnum:
assignee: Ricardo Rocha (rocha-porto) → Spyros Trigazis (strigazi)
Changed in magnum:
assignee: Spyros Trigazis (strigazi) → Ricardo Rocha (rocha-porto)
Changed in magnum:
assignee: Ricardo Rocha (rocha-porto) → Spyros Trigazis (strigazi)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (master)

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

Changed in magnum:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to magnum (stable/queens)

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (stable/queens)

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)

tags: added: in-stable-queens
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/magnum 6.1.0

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/magnum 7.0.0

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.