Azure Integrator Charm

Azure LB support for k8s like OpenStack's

Bug #1895807 reported by Pedro Guimarães
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Azure Integrator Charm
Fix Released
Wishlist
Joseph Borg
Azure Integrator Charm 1.22

Bug Description

Hi k8s team,

We are missing feature parity across supported cloud substrates in terms of LB integration in front of Kubernetes master API endpoint.

Without having it, we need to manually update the lb members of an external load-balancer which breaks the automation or scale-out/scale-in operations. Or we need to have an VIP for the master API endpoint, but it's not feasible at all because managing an additional and moving IP address for HA purpose is not supported on top of public clouds (blocked by arp spoofing protection feature enabled by default) and by Juju.

That is a blocker in an ongoing project since we have no way to achieve redundancy and HA for the endpoint.

See original description
Revision history for this message
Nobuto Murata (nobuto) wrote :

Without having the equivalent of the following one across the supported cloud substrates, Charmed Kubernetes has to be deployed with SPOF.
https://bugs.launchpad.net/charm-openstack-integrator/+bug/1836885

description: updated
Revision history for this message
Pedro Guimarães (pguimaraes) wrote :

Adding field-high since we cannot set a VIP and that means a SPOF on top of Azure.

George Kraft (cynerva)
Changed in charm-kubernetes-master:
importance: Undecided → High
Changed in charm-azure-integrator:
importance: Undecided → High
status: New → Triaged
Changed in charm-kubernetes-master:
status: New → Triaged
George Kraft (cynerva)
no longer affects: charm-kubernetes-master
Revision history for this message
Pedro Guimarães (pguimaraes) wrote :

Hi, working on this issue and we realized we need to do a (1) load balancer creation; and (2) update load balancer backend pool. For that, we've used ARM templates:

https://pastebin.canonical.com/p/KBmtvVHqwG/

Revision history for this message
Chris Sanders (chris.sanders) wrote :

The good news is, replacing kubeapi-lb with cloud LB (AWS, Azure, Google) is on the roadmap for this cycle. However, I need to unsubscribe field-high because this is a feature development not a bug in the existing integrator charm. Removing field-high isn't an indication that it's low priority simply that it's doesn't fit the classification.

The initial bug states "feature parity across supported cloud substrates" and that is a bit of an unbounded request. It is possible that specific features be added to a particular integrator before being rolled out to the others. I believe the discussion here is covered by replacing kubeapi-lb with cloud LB but I wanted to be clear that if you have a different use case that you believe is not covered please open a bug for that specific use case so we can evaluate and track it as well.

George Kraft (cynerva)
Changed in charm-azure-integrator:
importance: High → Wishlist
Revision history for this message
Cory Johns (johnsca) wrote :

The Azure portion of this was done in [1] and the K8s portion is being worked in [2].

[1]: https://github.com/juju-solutions/charm-azure-integrator/pull/28
[2]: https://bugs.launchpad.net/charm-kubernetes-master/+bug/1921776

Cory Johns (johnsca)
Changed in charm-azure-integrator:
milestone: none → 1.22
assignee: nobody → Joseph Borg (joeborg)
status: Triaged → Fix Committed
Kevin W Monroe (kwmonroe)
Changed in charm-azure-integrator:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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