Allow charm users to set admission-control

Bug #1841416 reported by Bui Hong Ha
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kubernetes Control Plane Charm
Fix Released
Wishlist
Tim Van Steenburgh

Bug Description

Currently, kube-api's admission-control is fixed at deployment with preset values [1].
This prevents users from passing their own admissions (for example: PodSecurityPolicy).

Also, in v1.15 admission controls, which are set in the charm, are already enabled by default.
Admission control therefore should be passed as additional plugins using flag: --enable-admission-lugins.

# Reference
1. https://github.com/charmed-kubernetes/charm-kubernetes-master/blob/master/reactive/kubernetes_master.py
2. https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/

Tags: sts
Changed in charm-kubernetes-master:
status: New → Triaged
importance: Undecided → Wishlist
Revision history for this message
Tim Van Steenburgh (tvansteenburgh) wrote :
Changed in charm-kubernetes-master:
status: Triaged → In Progress
assignee: nobody → Tim Van Steenburgh (tvansteenburgh)
Changed in charm-kubernetes-master:
status: In Progress → Fix Committed
milestone: none → 1.16
Changed in charm-kubernetes-master:
status: Fix Committed → Fix Released
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.