Skip to content
This repository has been archived by the owner on Dec 19, 2023. It is now read-only.

unable to use operator in-cluster (x509: certificate signed by unknown authority) #30

Open
kadel opened this issue Oct 13, 2023 · 4 comments
Labels

Comments

@kadel
Copy link
Member

kadel commented Oct 13, 2023

Describe the bug

When running operator in cluster I get the following errors

 status:
    conditions:
    - lastTransitionTime: "2023-10-13T13:38:01Z"
      status: "False"
      type: Deployed
    - lastTransitionTime: "2023-10-13T13:38:01Z"
      status: "True"
      type: Initialized
    - lastTransitionTime: "2023-10-13T13:38:26Z"
      message: |-
        values don't meet the specifications of the schema(s) in the following chart(s):
        upstream:
        Get "https://raw.githubusercontent.com/bitnami/charts/main/bitnami/postgresql/values.schema.json": x509: certificate signed by unknown authority
      reason: ReconcileError
      status: "True"
      type: Irreconcilable
    - lastTransitionTime: "2023-10-13T13:38:01Z"
      message: |-
        values don't meet the specifications of the schema(s) in the following chart(s):
        upstream:
        Get "https://raw.githubusercontent.com/bitnami/charts/main/bitnami/postgresql/values.schema.json": x509: certificate signed by unknown authority
      reason: InstallError
      status: "True"
      type: ReleaseFailed

What are the steps to reproduce this bug?

  1. build and push operator, bundle and catalog images
  2. add CatalogSource
  3. create a backstage instance using sample

Versions of software used and environment

tested on crc and 4.13 cluster on GCP both with the same problem

@kadel
Copy link
Member Author

kadel commented Oct 13, 2023

backstage/charts#141 is probably going to "fix" this.
It is not going to fix the root cause of why this is getting certificate errors, but after it is merged, the helm chart won't try fetching remote schemas anymore.

But the root cause of this is still going to be present, and it could cause problems somewhere else.

@tumido
Copy link
Member

tumido commented Oct 17, 2023

Is this duplicate of #29 ?

@kadel
Copy link
Member Author

kadel commented Oct 18, 2023

Is this duplicate of #29 ?

no. Fixing #29 will only resolve one of the symptoms of this problem

@tumido
Copy link
Member

tumido commented Oct 18, 2023

FTR: Operator should consume CAs from the cluster it's running in. I suspect this issue comes from the CSV we have defined for the operator.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants