You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per a discussion on the olm-dev triage call on Feb 4th, it was agreed that both the `initializer` and `registry-server` binaries should be deprecated in favor of `opm` equivalent commands.
Copy file name to clipboardexpand all lines: README.md
+3-1
Original file line number
Diff line number
Diff line change
@@ -8,8 +8,10 @@ Operator Registry runs in a Kubernetes or OpenShift cluster to provide operator
8
8
This project provides the following binaries:
9
9
10
10
*`opm`, which generates and updates registry databases as well as the index images that encapsulate them.
11
-
*`initializer`, which takes as an input a directory of operator manifests and outputs a sqlite database containing the same data for querying.
11
+
*`initializer`, which takes as an input a directory of operator manifests and outputs a sqlite database containing the same data for querying
12
+
* Deprecated - use `opm registry|index add` instead
12
13
*`registry-server`, which takes a sqlite database loaded with manifests, and exposes a gRPC interface to it.
14
+
* Deprecated - use `opm registry serve` instead
13
15
*`configmap-server`, which takes a kubeconfig and a configmap reference, and parses the configmap into the sqlite database before exposing it via the same interface as `registry-server`.
0 commit comments