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

"how to install an operator" using out of date OLM CRD/CR. #3915

Closed
grokspawn opened this issue Feb 19, 2024 · 4 comments
Closed

"how to install an operator" using out of date OLM CRD/CR. #3915

grokspawn opened this issue Feb 19, 2024 · 4 comments

Comments

@grokspawn
Copy link

grokspawn commented Feb 19, 2024

This refers to installing the CRDs/CRs for a basic OLM install under the "How do I get Operator Lifecycle Manager?" section, but these are woefully out of date. These actually point to v0.18.3 of OLM. Evidently OLM switched to a goreleaser config which instead captures the artifacts with tagged releases.

So this should be migrated to a way that looks like the scripted steps

curl -L https://github.com/operator-framework/operator-lifecycle-manager/releases/download/v0.26.0/install.sh -o install.sh
chmod +x install.sh
./install.sh v0.26.0 

c.f. https://github.com/operator-framework/operator-lifecycle-manager/releases/latest

Copy link
Contributor

This issue is stale because it has been open for 30 days with no activity.

@grokspawn
Copy link
Author

/remove-lifecycle stale

Copy link
Contributor

github-actions bot commented May 2, 2024

This issue is stale because it has been open for 30 days with no activity.

Copy link
Contributor

github-actions bot commented Jun 1, 2024

This issue was closed because it has been inactive for 30 days since being marked as stale.

@github-actions github-actions bot closed this as completed Jun 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant