Skip to content
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

Install plan is not getting generated when installing through Catalog Source #211

Closed
R3hankhan123 opened this issue Sep 17, 2024 · 5 comments

Comments

@R3hankhan123
Copy link

When trying to install the authorino operator through the catalog source using the following commands

kubectl create namespace authorino-operator

kubectl -n authorino-operator apply -f -<<EOF
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: operatorhubio-catalog
  namespace: authorino-operator
spec:
  sourceType: grpc
  image: quay.io/kuadrant/authorino-operator-catalog:latest
  displayName: Authorino Operator
EOF

kubectl apply -f - <<EOF
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: authorino-operator
spec:
  channel: alpha
  name: authorino-operator
  source: operatorhubio-catalog
  sourceNamespace: authorino-operator
  installPlanApproval: Automatic
EOF

The install plan is not getting generated and all available catalogsources are healthy

Screenshot 2024-09-17 at 2 55 42 PM Screenshot 2024-09-17 at 2 56 07 PM
@adam-cattermole
Copy link
Member

adam-cattermole commented Sep 17, 2024

Hi @R3hankhan123. The catalog image you're using quay.io/kuadrant/authorino-operator-catalog:latest looks to only contain bundled operators with channel: stable, perhaps that's the issue with the subscription?

@R3hankhan123
Copy link
Author

Hi, @adam-cattermole after using the stable channel the install plan is still not being generated

Screenshot 2024-09-17 at 3 22 03 PM

@adam-cattermole
Copy link
Member

It looks likely you're missing an OperatorGroup for the authorino-operator namespace which lets OLM install operators there. Could you try create one like this:

kubectl apply -f - <<EOF
apiVersion: operators.coreos.com/v1
kind: OperatorGroup
metadata:
  name: authorino-og
  namespace: authorino-operator
spec: {}
EOF

@R3hankhan123
Copy link
Author

Interesting, usually the OperatorGroup gets created by default. The solution worked though thanks!

@adam-cattermole
Copy link
Member

Great, glad it's working! Will close this but feel free to re-open if you find an issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

2 participants