Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-1216

SSO/Keycloak container does not have resources limit/request

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Critical Critical
    • 1.2
    • None
    • Operator
    • False
    • False
    • Undefined
    • GITOPS Sprint 204

      Version of operator v1.2.0-20

      Steps to reproduce.

      1. Install GitOps Operator in OCP 4.7

      2. Create an Argo CD instance in default namespace with SSO provider "keycloak"

      3. Go to Workloads -> Pods

      4. View the keycloak Pod's yaml.   There is no "resources" limits/request

      5. Edit the CR to add resources limit/request using the same as dex

      6. Go to Workloads -> Pods and observe the keycloak pod is in Error status

       

              aveerama@redhat.com Abhishek Veeramalla
              wtam_at_redhat William Tam
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: