-
Notifications
You must be signed in to change notification settings - Fork 107
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
docs: Provide operatorhub.io installation instructions #889
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@saschagrunert I'm sorry to have invalidated the lgtm tag, but I also added instructions on using the upstream bundles. This is mainly useful for people wanting to test the latest code. See also one question inline |
@@ -12,7 +12,7 @@ metadata: | |||
namespace: olm | |||
spec: | |||
sourceType: grpc | |||
image: quay.io/security-profiles-operator/security-profiles-operator-catalog:latest | |||
image: gcr.io/k8s-staging-sp-operator/security-profiles-operator-catalog:latest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@saschagrunert Should I also amend release.md or some release script so that these are kept in sync when we do a release?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, definitely 👍
Codecov Report
@@ Coverage Diff @@
## main #889 +/- ##
=======================================
Coverage 50.99% 50.99%
=======================================
Files 42 42
Lines 4536 4536
=======================================
Hits 2313 2313
Misses 2142 2142
Partials 81 81 |
/test pull-security-profiles-operator-test-e2e |
I amended the release doc in this PR since the tests needed a re-run anyway :-) |
/test pull-security-profiles-operator-test-e2e |
Now that SPO exists on operatorhub.io, make sure we tell people how to use it.
…perator-catalog:latest The example was pointing to a nonexistent catalog. Let's use the catalog that is refreshed after every build instead.
This is mostly useful for anyone testing nightlies.
…nged The OLM manifests at examples/olm/install-resources.yaml contain unversioned image tags, but at the release time they should contain the release tag.
Rebased on master in hopes of getting a clean CI run |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jhrozek, saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Merging to save the environment. |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Now that SPO exists on operatorhub.io, make sure we tell people how to
use it.
Which issue(s) this PR fixes:
Fixes #779
Does this PR have test?
N/A
Special notes for your reviewer:
Tested on our vagrant fedora image.
Does this PR introduce a user-facing change?