Kubernetes Control Plane Charm

node-security-group is not configurable

Bug #1834477 reported by Nicolas Pochet
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kubernetes Control Plane Charm
Invalid
Undecided
Unassigned
Openstack Integrator Charm
Invalid
Undecided
Unassigned

Bug Description

Currently, node-security-group is not configurable via the openstack-integrator charm.

https://kubernetes.io/docs/concepts/cluster-administration/cloud-providers/#load-balancer

It is necessary when manage-security-groups is set to True.

It also affects the kubernetes-common layer as this layer is responsible for the configuration of the integration: https://github.com/charmed-kubernetes/layer-kubernetes-common/blob/cda05cfceb864f7488483e791470473db85cca36/lib/charms/layer/kubernetes_common.py#L471

See original description
Nicolas Pochet (npochet)
description: updated
Revision history for this message
George Kraft (cynerva) wrote :

It looks like this is no longer relevant, since we switched to the external OpenStack cloud controller manager back in Charmed Kubernetes 1.15, which does not appear to have an equivalent option[1]. Also of note is that manage-security-groups is only supported when using the Neutron backend, and Neutron support is deprecated in favor of Octavia.

[1]: https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/using-openstack-cloud-controller-manager.md

Changed in charm-openstack-integrator:
status: New → Invalid
Changed in charm-kubernetes-master:
status: New → Invalid
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.