Description of problem: For OpenShift Online, we're going to need to set kubernetesMasterConfig.admissionConfig at install time. Version-Release number of selected component (if applicable): 3.2 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: There is no way to set kubernetesMasterConfig.admissionConfig in the installer. Expected results: Ability to define kubernetesMasterConfig.admissionConfig in the BYO inventory at install time. Additional info: The exact settings we'll be using for INT are listed here, for reference. https://github.com/openshift/online/issues/62#issuecomment-199369802
https://github.com/openshift/openshift-ansible/pull/1660
This pull request has passed both tests, but has not been merged.
The pull request still hasn't merged, and appears to still be worked on. I'm putting this back in assigned.
Check on openshift-ansible -b master Scenarios 1: Install env without admissionConfig Check the master config admissionConfig: apiLevels: <--snip--> kubernetesMasterConfig: admissionConfig: apiServerArguments: <--snip--> Get the expected result Install env with master admissionConfig openshift_master_admission_plugin_order=["RunOnceDuration", "NamespaceLifecycle", "OriginPodNodeEnvironment", "ClusterResourceOverride", "LimitRanger", "ServiceAccount", "SecurityContextConstraint", "ResourceQuota"] openshift_master_admission_plugin_config={"RunOnceDuration":{"configuration":{"apiVersion":"v1","kind":"RunOnceDurationConfig","activeDeadlineSecondsOverride":3600}},"ClusterResourceOverride":{"configuration":{"apiVersion":"v1","kind":"ClusterResourceOverrideConfig","limitCPUToMemoryPercent":200,"cpuRequestToLimitPercent":6,"memoryRequestToLimitPercent":60}}} {openshift_master_kube_admission_plugin_order=["providerSelection","RunOnceDuration"] openshift_master_kube_admission_plugin_config={"RunOnceDuration":{"configuration": "Just a testing"}} Check the result <--snip--> admissionConfig: pluginOrderOverride: - RunOnceDuration - NamespaceLifecycle - OriginPodNodeEnvironment - ClusterResourceOverride - LimitRanger - ServiceAccount - SecurityContextConstraint - ResourceQuota pluginConfig: ClusterResourceOverride: configuration: apiVersion: v1 cpuRequestToLimitPercent: 6 kind: ClusterResourceOverrideConfig limitCPUToMemoryPercent: 200 memoryRequestToLimitPercent: 60 RunOnceDuration: configuration: activeDeadlineSecondsOverride: 3600 apiVersion: v1 kind: RunOnceDurationConfig apiLevels: <--snip--> kubernetesMasterConfig: admissionConfig: pluginOrderOverride: - providerSelection - RunOnceDuration pluginConfig: RunOnceDuration: configuration: Just a testing apiServerArguments: get the expected results. Move this issue to VERIFIED.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1065
*** Bug 1354321 has been marked as a duplicate of this bug. ***