Operator failing to sync CRDs when applied using "oc apply"

Solution Unverified - Updated -

Issue

  • Running the oc apply -f tenant.yaml where tenant.yaml includes the following content:

    ---
    kind: Secret
    apiVersion: v1
    metadata:
      name: admin-secret
    data:
      admin_password: XXXXXXXXXXXXXX
    type: Opaque
    ---
    apiVersion: capabilities.3scale.net/v1alpha1
    kind: Tenant
    metadata:
      name: new-tenant
    spec:
      organizationName: new-org
      email: neworguser@example.com
      username: admin
      systemMasterUrl: 'https://master.example.com'
      masterCredentialsRef:
        name: system-seed
      passwordCredentialsRef:
        name: admin-secret
      tenantSecretRef:
        name: tennant-secret
    ---
    apiVersion: capabilities.3scale.net/v1beta1
    kind: Backend
    metadata:
      name: backend-api
    spec:
      name: backend-api
      systemName: backend-api
      description: Backend of demo-api
      privateBaseURL: >-
        https://echo-api.3scale.net:443
      providerAccountRef:
        name: tennant-secret
      metrics:
        hits:
          description: Number of API hits
          friendlyName: Hits
          unit: hit
    
  • Following error gets thrown:

    Message: LookupProviderAccount: providerAccountFromSecretReferenceSource: Secret "tennant-secret" not found
    

Environment

  • Red Hat 3scale API Management
    • 2.11 On-premises

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content