API Reference
Packages
olm.operatorframework.io/v1
Package v1 contains API Schema definitions for the olm v1 API group
Resource Types
AvailabilityMode
Underlying type: string
AvailabilityMode defines the availability of the catalog
Appears in: - ClusterCatalogSpec
| Field | Description |
|---|---|
Available |
|
Unavailable |
BundleMetadata
BundleMetadata is a representation of the identifying attributes of a bundle.
Appears in: - ClusterExtensionInstallStatus
| Field | Description | Default | Validation |
|---|---|---|---|
name string |
The name field is required and follows the DNS subdomain standard as defined in [RFC 1123]. It must contain only lowercase alphanumeric characters, hyphens (-) or periods (.), start and end with an alphanumeric character, and be no longer than 253 characters. |
Required: {} |
|
version string |
The version field is required and references the version that this bundle represents. The version field follows the semantic versioning standard as defined in https://semver.org/. |
Required: {} |
CRDUpgradeSafetyEnforcement
Underlying type: string
Appears in: - CRDUpgradeSafetyPreflightConfig
| Field | Description |
|---|---|
None |
None will not perform CRD upgrade safety checks. |
Strict |
Strict will enforce the CRD upgrade safety check and block the upgrade if the CRD would not pass the check. |
CRDUpgradeSafetyPreflightConfig
CRDUpgradeSafetyPreflightConfig is the configuration for CRD upgrade safety preflight check.
Appears in: - PreflightConfig
| Field | Description | Default | Validation |
|---|---|---|---|
enforcement CRDUpgradeSafetyEnforcement |
The enforcement field is required and configures the state of the CRD Upgrade Safety pre-flight check. Allowed values are "None" or "Strict". The default value is "Strict". When set to "None", the CRD Upgrade Safety pre-flight check is skipped during an upgrade operation. Use this option with caution as unintended consequences such as data loss can occur. When set to "Strict", the CRD Upgrade Safety pre-flight check runs during an upgrade operation. |
Enum: [None Strict] Required: {} |
CatalogFilter
CatalogFilter defines the attributes used to identify and filter content from a catalog.
Appears in: - SourceConfig
| Field | Description | Default | Validation |
|---|---|---|---|
packageName string |
The packageName field specifies the name of the package to be installed and is used to filter the content from catalogs. The packageName field is required, immutable, and follows the DNS subdomain standard as defined in [RFC 1123]. It must contain only lowercase alphanumeric characters, hyphens (-) or periods (.), start and end with an alphanumeric character, and be no longer than 253 characters. Some examples of valid values are: - some-package - 123-package - 1-package-2 - somepackage Some examples of invalid values are: - -some-package - some-package- - thisisareallylongpackagenamethatisgreaterthanthemaximumlength - some.package [RFC 1123]: https://tools.ietf.org/html/rfc1123 |
MaxLength: 253 Required: {} |
|
version string |
The version field is an optional semver constraint (a specific version or range of versions). When unspecified, the latest version available is installed. Acceptable version ranges are no longer than 64 characters. Version ranges are composed of comma- or space-delimited values and one or more comparison operators, known as comparison strings. You can add additional comparison strings using the OR operator (||). # Range Comparisons To specify a version range, you can use a comparison string like ">=3.0, <3.6". When specifying a range, automatic updates will occur within that range. The example comparison string means "install any version greater than or equal to 3.0.0 but less than 3.6.0.". It also states intent that if any upgrades are available within the version range after initial installation, those upgrades should be automatically performed. # Pinned Versions To specify an exact version to install you can use a version range that "pins" to a specific version. When pinning to a specific version, no automatic updates will occur. An example of a pinned version range is "0.6.0", which means "only install version 0.6.0 and never upgrade from this version". # Basic Comparison Operators The basic comparison operators and their meanings are: - "=", equal (not aliased to an operator) - "!=", not equal - "<", less than - ">", greater than - ">=", greater than OR equal to - "<=", less than OR equal to # Wildcard Comparisons You can use the "x", "X", and "" characters as wildcard characters in all comparison operations. Some examples of using the wildcard characters: - "1.2.x", "1.2.X", and "1.2." is equivalent to ">=1.2.0, < 1.3.0" - ">= 1.2.x", ">= 1.2.X", and ">= 1.2." is equivalent to ">= 1.2.0" - "<= 2.x", "<= 2.X", and "<= 2." is equivalent to "< 3" - "x", "X", and "*" is equivalent to ">= 0.0.0" # Patch Release Comparisons When you want to specify a minor version up to the next major version you can use the "~" character to perform patch comparisons. Some examples: - "~1.2.3" is equivalent to ">=1.2.3, <1.3.0" - "~1" and "~1.x" is equivalent to ">=1, <2" - "~2.3" is equivalent to ">=2.3, <2.4" - "~1.2.x" is equivalent to ">=1.2.0, <1.3.0" # Major Release Comparisons You can use the "^" character to make major release comparisons after a stable 1.0.0 version is published. If there is no stable version published, // minor versions define the stability level. Some examples: - "^1.2.3" is equivalent to ">=1.2.3, <2.0.0" - "^1.2.x" is equivalent to ">=1.2.0, <2.0.0" - "^2.3" is equivalent to ">=2.3, <3" - "^2.x" is equivalent to ">=2.0.0, <3" - "^0.2.3" is equivalent to ">=0.2.3, <0.3.0" - "^0.2" is equivalent to ">=0.2.0, <0.3.0" - "^0.0.3" is equvalent to ">=0.0.3, <0.0.4" - "^0.0" is equivalent to ">=0.0.0, <0.1.0" - "^0" is equivalent to ">=0.0.0, <1.0.0" # OR Comparisons You can use the "||" character to represent an OR operation in the version range. Some examples: - ">=1.2.3, <2.0.0 || >3.0.0" - "^0 || ^3 || ^5" For more information on semver, please see https://semver.org/ |
MaxLength: 64 |
|
channels string array |
The channels field is optional and specifies a set of channels belonging to the package specified in the packageName field. A channel is a package-author-defined stream of updates for an extension. Each channel in the list must follow the DNS subdomain standard as defined in [RFC 1123]. It must contain only lowercase alphanumeric characters, hyphens (-) or periods (.), start and end with an alphanumeric character, and be no longer than 253 characters. You can specify no more than 256 channels. When specified, it constrains the set of installable bundles and the automated upgrade path. This constraint is an AND operation with the version field. For example: - Given channel is set to "foo" - Given version is set to ">=1.0.0, <1.5.0" - Only bundles that exist in channel "foo" AND satisfy the version range comparison are considered installable - Automatic upgrades are constrained to upgrade edges defined by the selected channel When unspecified, upgrade edges across all channels are used to identify valid automatic upgrade paths. Some examples of valid values are: - 1.1.x - alpha - stable - stable-v1 - v1-stable - dev-preview - preview - community Some examples of invalid values are: - -some-channel - some-channel- - thisisareallylongchannelnamethatisgreaterthanthemaximumlength - original_40 - --default-channel [RFC 1123]: https://tools.ietf.org/html/rfc1123 |
MaxItems: 256 items:MaxLength: 253 items:XValidation: {self.matches("^a-z0-9?(\.a-z0-9?)*$") channels entries must be valid DNS1123 subdomains |
|
selector LabelSelector |
The selector field is optional and filters the set of ClusterCatalogs used in the bundle selection process. When unspecified, all ClusterCatalogs are used in the bundle selection process. |
||
upgradeConstraintPolicy UpgradeConstraintPolicy |
The upgradeConstraintPolicy field is optional and controls whether the upgrade paths defined in the catalog are enforced for the package referenced in the packageName field. Allowed values are "CatalogProvided", "SelfCertified", or omitted. When set to "CatalogProvided", automatic upgrades only occur when upgrade constraints specified by the package author are met. When set to "SelfCertified", the upgrade constraints specified by the package author are ignored. This allows upgrades and downgrades to any version of the package. This is considered a dangerous operation as it can lead to unknown and potentially disastrous outcomes, such as data loss. Use this option only if you have independently verified the changes. When omitted, the default value is "CatalogProvided". |
CatalogProvided | Enum: [CatalogProvided SelfCertified] |
CatalogSource
CatalogSource is a discriminated union of possible sources for a Catalog. CatalogSource contains the sourcing information for a Catalog
Appears in: - ClusterCatalogSpec
| Field | Description | Default | Validation |
|---|---|---|---|
type SourceType |
The type field specifies the type of source for the catalog. The type field is required. The only allowed value is "Image". When set to "Image", the ClusterCatalog content is sourced from an OCI image. When using an image source, the image field must be set and must be the only field defined for this type. |
Enum: [Image] Required: {} |
|
image ImageSource |
The image field configures how catalog contents are sourced from an OCI image. The image field is required when type is Image, and forbidden otherwise. |
ClusterCatalog
The ClusterCatalog resource makes File-Based Catalog (FBC) data available to your cluster. For more information on FBC, see https://olm.operatorframework.io/docs/reference/file-based-catalogs/#docs
Appears in: - ClusterCatalogList
| Field | Description | Default | Validation |
|---|---|---|---|
apiVersion string |
olm.operatorframework.io/v1 |
||
kind string |
ClusterCatalog |
||
kind string |
Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds |
||
apiVersion string |
APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources |
||
metadata ObjectMeta |
Refer to Kubernetes API documentation for fields of metadata. |
||
spec ClusterCatalogSpec |
The spec field defines the desired state of the ClusterCatalog. The spec field is required. The controller ensures that the catalog is unpacked and served over the catalog content HTTP server. |
Required: {} |
|
status ClusterCatalogStatus |
The status field contains the following information about the state of the ClusterCatalog: - Whether the catalog contents are being served via the catalog content HTTP server - Whether the ClusterCatalog is progressing to a new state - A reference to the source from which the catalog contents were retrieved |
ClusterCatalogList
ClusterCatalogList contains a list of ClusterCatalog
| Field | Description | Default | Validation |
|---|---|---|---|
apiVersion string |
olm.operatorframework.io/v1 |
||
kind string |
ClusterCatalogList |
||
kind string |
Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds |
||
apiVersion string |
APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources |
||
metadata ListMeta |
Refer to Kubernetes API documentation for fields of metadata. |
||
items ClusterCatalog array |
items is a list of ClusterCatalogs. items is required. |
Required: {} |
ClusterCatalogSpec
ClusterCatalogSpec defines the desired state of ClusterCatalog
Appears in: - ClusterCatalog
| Field | Description | Default | Validation |
|---|---|---|---|
source CatalogSource |
The source field defines the source of a catalog. A catalog contains information on content that can be installed on a cluster. The catalog source makes catalog contents discoverable and usable by other on-cluster components. These components can present the content in a GUI dashboard or install content from the catalog on the cluster. The catalog source must contain catalog metadata in the File-Based Catalog (FBC) format. For more information on FBC, see https://olm.operatorframework.io/docs/reference/file-based-catalogs/#docs. The source field is required. Below is a minimal example of a ClusterCatalogSpec that sources a catalog from an image: source: type: Image image: ref: quay.io/operatorhubio/catalog:latest |
Required: {} |
|
priority integer |
The priority field defines a priority for this ClusterCatalog. The priority field is optional. Clients use the ClusterCatalog priority as a tie-breaker between ClusterCatalogs that meet their requirements. Higher numbers mean higher priority. Clients decide how to handle scenarios where multiple ClusterCatalogs with the same priority meet their requirements. Clients should prompt users for additional input to break the tie. When omitted, the default priority is 0. Use negative numbers to specify a priority lower than the default. Use positive numbers to specify a priority higher than the default. The lowest possible value is -2147483648. The highest possible value is 2147483647. |
0 | |
availabilityMode AvailabilityMode |
The availabilityMode field defines how the ClusterCatalog is made available to clients on the cluster. The availabilityMode field is optional. Allowed values are "Available", "Unavailable", or omitted. When omitted, the default value is "Available". When set to "Available", the catalog contents are unpacked and served over the catalog content HTTP server. Clients should consider this ClusterCatalog and its contents as usable. When set to "Unavailable", the catalog contents are no longer served over the catalog content HTTP server. Treat this the same as if the ClusterCatalog does not exist. Use "Unavailable" when you want to keep the ClusterCatalog but treat it as if it doesn't exist. |
Available | Enum: [Unavailable Available] |
ClusterCatalogStatus
ClusterCatalogStatus defines the observed state of ClusterCatalog
Appears in: - ClusterCatalog
| Field | Description | Default | Validation |
|---|---|---|---|
conditions Condition array |
The conditions field represents the current state of this ClusterCatalog. The current condition types are Serving and Progressing. The Serving condition represents whether the catalog contents are being served via the HTTP(S) web server: - When status is True and reason is Available, the catalog contents are being served. - When status is False and reason is Unavailable, the catalog contents are not being served because the contents are not yet available. - When status is False and reason is UserSpecifiedUnavailable, the catalog contents are not being served because the catalog has been intentionally marked as unavailable. The Progressing condition represents whether the ClusterCatalog is progressing or is ready to progress towards a new state: - When status is True and reason is Retrying, an error occurred that may be resolved on subsequent reconciliation attempts. - When status is True and reason is Succeeded, the ClusterCatalog has successfully progressed to a new state and is ready to continue progressing. - When status is False and reason is Blocked, an error occurred that requires manual intervention for recovery. If the system initially fetched contents and polling identifies updates, both conditions can be active simultaneously: - The Serving condition remains True with reason Available because the previous contents are still served via the HTTP(S) web server. - The Progressing condition is True with reason Retrying because the system is working to serve the new version. |
||
resolvedSource ResolvedCatalogSource |
The resolvedSource field contains information about the resolved source based on the source type. | ||
urls ClusterCatalogURLs |
The urls field contains the URLs that can be used to access the catalog. | ||
lastUnpacked Time |
The lastUnpacked field represents the last time the catalog contents were extracted from their source format. For example, when using an Image source, the OCI image is pulled and image layers are written to a file-system backed cache. This extraction from the source format is called "unpacking". |
ClusterCatalogURLs
ClusterCatalogURLs contains the URLs that can be used to access the catalog.
Appears in: - ClusterCatalogStatus
| Field | Description | Default | Validation |
|---|---|---|---|
base string |
The base field is a cluster-internal URL that provides endpoints for accessing the catalog content. Clients should append the path for the endpoint they want to access. Currently, only a single endpoint is served and is accessible at the path /api/v1. The endpoints served for the v1 API are: - /all - this endpoint returns the entire catalog contents in the FBC format New endpoints may be added as needs evolve. |
MaxLength: 525 Required: {} |
ClusterExtension
ClusterExtension is the Schema for the clusterextensions API
Appears in: - ClusterExtensionList
| Field | Description | Default | Validation |
|---|---|---|---|
apiVersion string |
olm.operatorframework.io/v1 |
||
kind string |
ClusterExtension |
||
kind string |
Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds |
||
apiVersion string |
APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources |
||
metadata ObjectMeta |
Refer to Kubernetes API documentation for fields of metadata. |
||
spec ClusterExtensionSpec |
spec is an optional field that defines the desired state of the ClusterExtension. | ||
status ClusterExtensionStatus |
status is an optional field that defines the observed state of the ClusterExtension. |
ClusterExtensionConfig
ClusterExtensionConfig is a discriminated union which selects the source configuration values to be merged into the ClusterExtension's rendered manifests.
Appears in: - ClusterExtensionSpec
| Field | Description | Default | Validation |
|---|---|---|---|
configType ClusterExtensionConfigType |
The configType field is required and specifies the type of configuration source. The only allowed value is "Inline". When set to "Inline", the cluster extension configuration is defined inline within the ClusterExtension resource. |
Enum: [Inline] Required: {} |
|
inline JSON |
The inline field contains JSON or YAML values specified directly in the ClusterExtension. The inline field must be set if configType is "Inline". The inline field accepts arbitrary JSON/YAML objects. The inline field is validated at runtime against the schema provided by the bundle if a schema is provided. |
Type: object |
ClusterExtensionConfigType
Underlying type: string
Appears in: - ClusterExtensionConfig
| Field | Description |
|---|---|
Inline |
ClusterExtensionInstallConfig
ClusterExtensionInstallConfig is a union which selects the clusterExtension installation config. ClusterExtensionInstallConfig requires the namespace and serviceAccount which should be used for the installation of packages.
Appears in: - ClusterExtensionSpec
| Field | Description | Default | Validation |
|---|---|---|---|
preflight PreflightConfig |
The preflight field is optional and configures the checks that run before installation or upgrade of the content for the package specified in the packageName field. When specified, it replaces the default preflight configuration for install/upgrade actions. When not specified, the default configuration is used. |
ClusterExtensionInstallStatus
ClusterExtensionInstallStatus is a representation of the status of the identified bundle.
Appears in: - ClusterExtensionStatus
| Field | Description | Default | Validation |
|---|---|---|---|
bundle BundleMetadata |
The bundle field is required and represents the identifying attributes of a bundle. A "bundle" is a versioned set of content that represents the resources that need to be applied to a cluster to install a package. |
Required: {} |
ClusterExtensionList
ClusterExtensionList contains a list of ClusterExtension
| Field | Description | Default | Validation |
|---|---|---|---|
apiVersion string |
olm.operatorframework.io/v1 |
||
kind string |
ClusterExtensionList |
||
kind string |
Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds |
||
apiVersion string |
APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources |
||
metadata ListMeta |
Refer to Kubernetes API documentation for fields of metadata. |
||
items ClusterExtension array |
items is a required list of ClusterExtension objects. | Required: {} |
ClusterExtensionSpec
ClusterExtensionSpec defines the desired state of ClusterExtension
Appears in: - ClusterExtension
| Field | Description | Default | Validation |
|---|---|---|---|
namespace string |
The namespace field specifies a Kubernetes namespace. This is the namespace where the provided ServiceAccount must exist. It also designates the default namespace where namespace-scoped resources for the extension are applied to the cluster. Some extensions may contain namespace-scoped resources to be applied in other namespaces. This namespace must exist. The namespace field is required, immutable, and follows the DNS label standard as defined in [RFC 1123]. It must contain only lowercase alphanumeric characters or hyphens (-), start and end with an alphanumeric character, and be no longer than 63 characters. [RFC 1123]: https://tools.ietf.org/html/rfc1123 |
MaxLength: 63 Required: {} |
|
serviceAccount ServiceAccountReference |
The serviceAccount field specifies a ServiceAccount used to perform all interactions with the cluster that are required to manage the extension. The ServiceAccount must be configured with the necessary permissions to perform these interactions. The ServiceAccount must exist in the namespace referenced in the spec. The serviceAccount field is required. |
Required: {} |
|
source SourceConfig |
The source field is required and selects the installation source of content for this ClusterExtension. Set the sourceType field to perform the selection. Catalog is currently the only implemented sourceType. Setting sourceType to "Catalog" requires the catalog field to also be defined. Below is a minimal example of a source definition (in yaml): source: sourceType: Catalog catalog: packageName: example-package |
Required: {} |
|
install ClusterExtensionInstallConfig |
The install field is optional and configures installation options for the ClusterExtension, such as the pre-flight check configuration. |
||
config ClusterExtensionConfig |
The config field is optional and specifies bundle-specific configuration. Configuration is bundle-specific and a bundle may provide a configuration schema. When not specified, the default configuration of the resolved bundle is used. The config field is validated against a configuration schema provided by the resolved bundle. If the bundle does not provide a configuration schema, the final manifests are derived on a best-effort basis. For more information on how to configure the bundle, see the bundle's end-user documentation. |
ClusterExtensionStatus
ClusterExtensionStatus defines the observed state of a ClusterExtension.
Appears in: - ClusterExtension
| Field | Description | Default | Validation |
|---|---|---|---|
conditions Condition array |
The set of condition types which apply to all spec.source variations are Installed and Progressing. The Installed condition represents whether the bundle has been installed for this ClusterExtension: - When Installed is True and the Reason is Succeeded, the bundle has been successfully installed. - When Installed is False and the Reason is Failed, the bundle has failed to install. The Progressing condition represents whether the ClusterExtension is advancing towards a new state: - When Progressing is True and the Reason is Succeeded, the ClusterExtension is making progress towards a new state. - When Progressing is True and the Reason is Retrying, the ClusterExtension has encountered an error that could be resolved on subsequent reconciliation attempts. - When Progressing is False and the Reason is Blocked, the ClusterExtension has encountered an error that requires manual intervention for recovery. When the ClusterExtension is sourced from a catalog, it may also communicate a deprecation condition. These are indications from a package owner to guide users away from a particular package, channel, or bundle: - BundleDeprecated is set if the requested bundle version is marked deprecated in the catalog. - ChannelDeprecated is set if the requested channel is marked deprecated in the catalog. - PackageDeprecated is set if the requested package is marked deprecated in the catalog. - Deprecated is a rollup condition that is present when any of the deprecated conditions are present. |
||
install ClusterExtensionInstallStatus |
The install field is a representation of the current installation status for this ClusterExtension. |
ImageSource
ImageSource enables users to define the information required for sourcing a Catalog from an OCI image
If we see that there is a possibly valid digest-based image reference AND pollIntervalMinutes is specified, reject the resource since there is no use in polling a digest-based image reference.
Appears in: - CatalogSource
| Field | Description | Default | Validation |
|---|---|---|---|
ref string |
The ref field defines the reference to a container image containing catalog contents. The ref field is required. The ref field cannot be more than 1000 characters. A reference has 3 parts: the domain, name, and identifier. The domain is typically the registry where an image is located. It must be alphanumeric characters (lowercase and uppercase) separated by the "." character. Hyphenation is allowed, but the domain must start and end with alphanumeric characters. Specifying a port to use is also allowed by adding the ":" character followed by numeric values. The port must be the last value in the domain. Some examples of valid domain values are "registry.mydomain.io", "quay.io", "my-registry.io:8080". The name is typically the repository in the registry where an image is located. It must contain lowercase alphanumeric characters separated only by the ".", "", "__", "-" characters. Multiple names can be concatenated with the "/" character. The domain and name are combined using the "/" character. Some examples of valid name values are "operatorhubio/catalog", "catalog", "my-catalog.prod". An example of the domain and name parts of a reference being combined is "quay.io/operatorhubio/catalog". The identifier is typically the tag or digest for an image reference and is present at the end of the reference. It starts with a separator character used to distinguish the end of the name and beginning of the identifier. For a digest-based reference, the "@" character is the separator. For a tag-based reference, the ":" character is the separator. An identifier is required in the reference. Digest-based references must contain an algorithm reference immediately after the "@" separator. The algorithm reference must be followed by the ":" character and an encoded string. The algorithm must start with an uppercase or lowercase alpha character followed by alphanumeric characters and may contain the "-", "", "+", and "." characters. Some examples of valid algorithm values are "sha256", "sha256+b64u", "multihash+base58". The encoded string following the algorithm must be hex digits (a-f, A-F, 0-9) and must be a minimum of 32 characters. Tag-based references must begin with a word character (alphanumeric + "_") followed by word characters or ".", and "-" characters. The tag must not be longer than 127 characters. An example of a valid digest-based image reference is "quay.io/operatorhubio/catalog@sha256:200d4ddb2a73594b91358fe6397424e975205bfbe44614f5846033cad64b3f05" An example of a valid tag-based image reference is "quay.io/operatorhubio/catalog:latest" |
MaxLength: 1000 Required: {} |
|
pollIntervalMinutes integer |
The pollIntervalMinutes field sets the interval, in minutes, at which the image source is polled for new content. The pollIntervalMinutes field is optional. You cannot specify pollIntervalMinutes when ref is a digest-based reference. When omitted, the image is not polled for new content. |
Minimum: 1 |
PreflightConfig
PreflightConfig holds the configuration for the preflight checks. If used, at least one preflight check must be non-nil.
Appears in: - ClusterExtensionInstallConfig
| Field | Description | Default | Validation |
|---|---|---|---|
crdUpgradeSafety CRDUpgradeSafetyPreflightConfig |
The crdUpgradeSafety field configures the CRD Upgrade Safety pre-flight checks that run before upgrades of installed content. The CRD Upgrade Safety pre-flight check safeguards from unintended consequences of upgrading a CRD, such as data loss. |
ResolvedCatalogSource
ResolvedCatalogSource is a discriminated union of resolution information for a Catalog. ResolvedCatalogSource contains the information about a sourced Catalog
Appears in: - ClusterCatalogStatus
| Field | Description | Default | Validation |
|---|---|---|---|
type SourceType |
The type field specifies the type of source for the catalog. The type field is required. The only allowed value is "Image". When set to "Image", information about the resolved image source is set in the image field. |
Enum: [Image] Required: {} |
|
image ResolvedImageSource |
The image field contains resolution information for a catalog sourced from an image. The image field must be set when type is Image, and forbidden otherwise. |
ResolvedImageSource
ResolvedImageSource provides information about the resolved source of a Catalog sourced from an image.
Appears in: - ResolvedCatalogSource
| Field | Description | Default | Validation |
|---|---|---|---|
ref string |
The ref field contains the resolved image digest-based reference. The digest format allows you to use other tooling to fetch the exact OCI manifests that were used to extract the catalog contents. |
MaxLength: 1000 Required: {} |
ServiceAccountReference
ServiceAccountReference identifies the serviceAccount used fo install a ClusterExtension.
Appears in: - ClusterExtensionSpec
| Field | Description | Default | Validation |
|---|---|---|---|
name string |
The name field is a required, immutable reference to the name of the ServiceAccount used for installation and management of the content for the package specified in the packageName field. This ServiceAccount must exist in the installNamespace. The name field follows the DNS subdomain standard as defined in [RFC 1123]. It must contain only lowercase alphanumeric characters, hyphens (-) or periods (.), start and end with an alphanumeric character, and be no longer than 253 characters. Some examples of valid values are: - some-serviceaccount - 123-serviceaccount - 1-serviceaccount-2 - someserviceaccount - some.serviceaccount Some examples of invalid values are: - -some-serviceaccount - some-serviceaccount- [RFC 1123]: https://tools.ietf.org/html/rfc1123 |
MaxLength: 253 Required: {} |
SourceConfig
SourceConfig is a discriminated union which selects the installation source.
Appears in: - ClusterExtensionSpec
| Field | Description | Default | Validation |
|---|---|---|---|
sourceType string |
The sourceType field is required and specifies the type of install source. The only allowed value is "Catalog". When set to "Catalog", information for determining the appropriate bundle of content to install is fetched from ClusterCatalog resources on the cluster. When using the Catalog sourceType, the catalog field must also be set. |
Enum: [Catalog] Required: {} |
|
catalog CatalogFilter |
The catalog field configures how information is sourced from a catalog. The catalog field is required when sourceType is "Catalog", and forbidden otherwise. |
SourceType
Underlying type: string
SourceType defines the type of source used for catalogs.
Appears in: - CatalogSource - ResolvedCatalogSource
| Field | Description |
|---|---|
Image |
UpgradeConstraintPolicy
Underlying type: string
Appears in: - CatalogFilter
| Field | Description |
|---|---|
CatalogProvided |
The extension will only upgrade if the new version satisfies the upgrade constraints set by the package author. |
SelfCertified |
Unsafe option which allows an extension to be upgraded or downgraded to any available version of the package and ignore the upgrade path designed by package authors. This assumes that users independently verify the outcome of the changes. Use with caution as this can lead to unknown and potentially disastrous results such as data loss. |