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
controller/registry: implement content extraction for catalog sources (#3029)
* go.mod: update the api dependency
Signed-off-by: Steve Kuznetsov <[email protected]>
* controller/registry: implement content extraction for catalog sources
Signed-off-by: Steve Kuznetsov <[email protected]>
---------
Signed-off-by: Steve Kuznetsov <[email protected]>
Copy file name to clipboardexpand all lines: deploy/chart/crds/0000_50_olm_00-catalogsources.crd.yaml
+11-1
Original file line number
Diff line number
Diff line change
@@ -532,8 +532,18 @@ spec:
532
532
topologyKey:
533
533
description: This pod should be co-located (affinity) or not co-located (anti-affinity) with the pods matching the labelSelector in the specified namespaces, where co-located is defined as running on a node whose value of the label with key topologyKey matches that of any node on which any of the selected pods is running. Empty topologyKey is not allowed.
534
534
type: string
535
+
extractContent:
536
+
description: ExtractContent configures the gRPC catalog Pod to extract catalog metadata from the provided index image and use a well-known version of the `opm` server to expose it. The catalog index image that this CatalogSource is configured to use *must* be using the file-based catalogs in order to utilize this feature.
537
+
type: object
538
+
properties:
539
+
cacheDir:
540
+
description: CacheDir is the directory storing the pre-calculated API cache.
541
+
type: string
542
+
catalogDir:
543
+
description: CatalogDir is the directory storing the file-based catalog contents.
544
+
type: string
535
545
memoryTarget:
536
-
description: "MemoryTarget configures the $GOMEMLIMIT value for the gRPC catalog Pod. This is a soft memory limit for the server, which the runtime will attempt to meet but makes no guarantees that it will do so. If this value is set, the Pod will have the following modifications made to the container running the server: - the $GOMEMLIMIT environment variable will be set to this value in bytes - the memory request will be set to this value - the memory limit will be set to 200% of this value \n This field should be set if it's desired to reduce the footprint of a catalog server as much as possible, or if a catalog being served is very large and needs more than the default allocation. If your index image has a file- system cache, determine a good approximation for this value by doubling the size of the package cache at /tmp/cache/cache/packages.json in the index image. \n This field is best-effort; if unset, no default will be used and no Pod memory limit or $GOMEMLIMIT value will be set."
546
+
description: "MemoryTarget configures the $GOMEMLIMIT value for the gRPC catalog Pod. This is a soft memory limit for the server, which the runtime will attempt to meet but makes no guarantees that it will do so. If this value is set, the Pod will have the following modifications made to the container running the server: - the $GOMEMLIMIT environment variable will be set to this value in bytes - the memory request will be set to this value \n This field should be set if it's desired to reduce the footprint of a catalog server as much as possible, or if a catalog being served is very large and needs more than the default allocation. If your index image has a file- system cache, determine a good approximation for this value by doubling the size of the package cache at /tmp/cache/cache/packages.json in the index image. \n This field is best-effort; if unset, no default will be used and no Pod memory limit or $GOMEMLIMIT value will be set."
0 commit comments