FailedCreate errors trying to deploy SiteMinder in containers in Openshift
search cancel

FailedCreate errors trying to deploy SiteMinder in containers in Openshift

book

Article ID: 450195

calendar_today

Updated On:

Products

SITEMINDER

Issue/Introduction

Trying to deploy SiteMinder Policy Server and Admin UI in containers, these fail to deploy and the following errors are obtained in the event log

109s        Warning   FailedCreate        replicaset/policyserver-siteminder-policy-server-6d57496b96     Error creating: pods "policyserver-siteminder-policy-server-6d57496b96-mx4q5" is forbidden: [maximum cpu usage per Pod is 1, but limit is 1500m, maximum memory usage per Pod is 2Gi, but limit is 5Gi, maximum cpu usage per Container is 1, but limit is 1500m, maximum memory usage per Container is 1Gi, but limit is 5Gi]

Environment

CA SiteMinder 12.9 on Openshift

Cause

The LimitRange Specification inside the values.yaml is in this case, the following:

spec:

  limits:
  - max:
      cpu: "1"        # MAXIMUM 1 CPU (1000m) TOTAL PER POD
      memory: 2Gi
    type: Pod

The multi-container pod sums up the CPU limits of ALL four containers inside it:     

Container                           CPU                         Limit Requested
     policy-server                 300m    
     admin-ui                        400m
     config-retriever              150m (or default)
     runtime-config-retriever 150m (or default)

If any containers don't have explicit limits, OpenShift applies the LimitRange default of 500m per unconfigured container.
 
In this case, Kubernetes summed the Administrative Server containers up to 1940m (1.94 CPUs), which directly breaks the Pod-level maximum
rule of 1 (1000m).

Resolution

Increase the namespace LimitRange to a slightly higher value accommodating the Administrative Server pod.

As a start, increase the CPU to 2 and Memory to 3Gi.

If the admin pod still fails after those changes, then increase the  CPU to 3 and Memory up to 4Gi;