Skip to content

OLM - running in a restricted environment. #3327

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
rridtraining opened this issue Jun 25, 2024 · 1 comment
Open

OLM - running in a restricted environment. #3327

rridtraining opened this issue Jun 25, 2024 · 1 comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@rridtraining
Copy link

rridtraining commented Jun 25, 2024

I'm trying to run OLM in a restricted kubernetes environment.
I was able to deploy OLM successfully, but when I try to subscribe to an operator, the manifest always takes a docker image like quay.io/image:tag instead of my-local-repository/image:tag.
I've seen that all manifests are in the /configs of the catalog docker image (quay.io/operatorhubio/catalog:latest), so I'm trying to rebuild the docker image but it doesn't take into account the changes I've applied.
Is there a configuration I can add to overwrite the docker repositories in the manifest in OLM catalog (quay.io/operatorhubio/catalog:latest)?

  • To subscribe
    apiVersion: operators.coreos.com/v1alpha1
    kind: Subscription
    metadata:
    name: my-argocd-operator
    namespace: operators
    spec: channel: alpha
    name: argocd-operator
    source: operatorhubio-catalog
    sourceNamespace: olm
Copy link

Issues go stale after 90 days of inactivity. If there is no further activity, the issue will be closed in another 30 days.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

1 participant