CPU limits quotas in demo mode aren't as expected VIP Authentication Hub

Products

• VIP Authentication Hub

Issue/Introduction

Installing VIP Authentication Hub, when setting the quota for the demo version, the quota is requested as normal configuration and not demo one, ie., some have 1000 or 2000 millicpu instead of 600 as per the excel sheet "deployment sizing sheet" (1).

This is the cpu limit for each of the POD:

Name:             <namespace>-ssp-admin-<number>
    Limits:
      cpu:     2
Name:             <namespace>-ssp-adminconsole-<number>
    Limits:
      cpu:     1
Name:             <namespace>-ssp-auth-mgr-<number>
    Limits:
      cpu:     600m
Name:             <namespace>-ssp-azserver-<number>
    Limits:
      cpu:     600m
Name:             <namespace>-ssp-db-metrics-exporter-<number>
    Limits:
      cpu:     400m
Name:             <namespace>-ssp-db-pxc-0
    Limits:
      cpu:  2
Name:             <namespace>-ssp-factor-<number>
    Limits:
      cpu:     600m
Name:             <namespace>-ssp-geolocation-<number>
    Limits:
      cpu:     600m
Name:             <namespace>-ssp-iarisk-<number>
    Limits:
      cpu:     2
Name:             <namespace>-ssp-identity-<number>
    Limits:
      cpu:     2
Name:             <namespace>-ssp-opa-<number>
    Limits:
      cpu:     600m
Name:             <namespace>-ssp-scheduler-<number>
    Limits:
      cpu:     2
Name:             <namespace>-ssp-signin-<number>
    Limits:
      cpu:     400m
Name:             <namespace>-ssp-swagger-<number>
    Limits:
      cpu:     400m
Name:             ssp-hazelcast-entp-0
    Limits:
      cpu:     2
Name:             ssp-hazelcast-entp-1
    Limits:
      cpu:     2

 

Resolution

Upgrade VIP Authentication Hub to the version 3.3 to fix this issue, when this version will be available.

 

Additional Information

 

1. Sizing Systems