openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

fixing new API error

Browse Source
This commit is contained in:
Kathryn Alexander
2025-10-17 15:45:46 -04:00
committed by openshift-cherrypick-robot
parent e048ee9852
commit 6ed15c8b3f
2 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
rest_api/config_apis/clusterimagepolicy-config-openshift-io-v1.adoc
View File

@@ -80,7 +80,7 @@ images not matching the verification policy will be treated.
| scopes is a required field that defines the list of image identities assigned to a policy. Each item refers to a scope in a registry implementing the "Docker Registry HTTP API V2".
Scopes matching individual images are named Docker references in the fully expanded form, either using a tag or digest. For example, docker.io/library/busybox:latest (not busybox:latest).
More general scopes are prefixes of individual-image scopes, and specify a repository (by omitting the tag or digest), a repository
namespace, or a registry host (by only specifying the host name and possibly a port number) or a wildcard expression starting with `*.`, for matching all subdomains (not including a port number).
namespace, or a registry host (by only specifying the host name and possibly a port number) or a wildcard expression starting with `\*.`, for matching all subdomains (not including a port number).
Wildcards are only supported for subdomain matching, and may not be used in the middle of the host, i.e. *.example.com is a valid case, but example*.*.com is not.
This support no more than 256 scopes in one object. If multiple scopes match a given image, only the policy requirements for the most specific scope apply. The policy requirements for more general scopes are ignored.
In addition to setting a policy appropriate for your own deployed applications, make sure that a policy on the OpenShift image repositories
@@ -554,7 +554,7 @@ Description::
| Parameter | Type | Description
| `body`
| xref:../config_apis/clusterimagepolicy-config-openshift-io-v1.adoc#clusterimagepolicy-config-openshift-io-v1[`ClusterImagePolicy`] schema
|
|
|===
.HTTP responses
@@ -687,7 +687,7 @@ Description::
| Parameter | Type | Description
| `body`
| xref:../config_apis/clusterimagepolicy-config-openshift-io-v1.adoc#clusterimagepolicy-config-openshift-io-v1[`ClusterImagePolicy`] schema
|
|
|===
.HTTP responses
@@ -789,7 +789,7 @@ Description::
| Parameter | Type | Description
| `body`
| xref:../config_apis/clusterimagepolicy-config-openshift-io-v1.adoc#clusterimagepolicy-config-openshift-io-v1[`ClusterImagePolicy`] schema
|
|
|===
.HTTP responses

8
rest_api/config_apis/imagepolicy-config-openshift-io-v1.adoc
View File

@@ -80,7 +80,7 @@ images not matching the verification policy will be treated.
| scopes is a required field that defines the list of image identities assigned to a policy. Each item refers to a scope in a registry implementing the "Docker Registry HTTP API V2".
Scopes matching individual images are named Docker references in the fully expanded form, either using a tag or digest. For example, docker.io/library/busybox:latest (not busybox:latest).
More general scopes are prefixes of individual-image scopes, and specify a repository (by omitting the tag or digest), a repository
namespace, or a registry host (by only specifying the host name and possibly a port number) or a wildcard expression starting with `*.`, for matching all subdomains (not including a port number).
namespace, or a registry host (by only specifying the host name and possibly a port number) or a wildcard expression starting with `\*.`, for matching all subdomains (not including a port number).
Wildcards are only supported for subdomain matching, and may not be used in the middle of the host, i.e. *.example.com is a valid case, but example*.*.com is not.
This support no more than 256 scopes in one object. If multiple scopes match a given image, only the policy requirements for the most specific scope apply. The policy requirements for more general scopes are ignored.
In addition to setting a policy appropriate for your own deployed applications, make sure that a policy on the OpenShift image repositories
@@ -580,7 +580,7 @@ Description::
| Parameter | Type | Description
| `body`
| xref:../config_apis/imagepolicy-config-openshift-io-v1.adoc#imagepolicy-config-openshift-io-v1[`ImagePolicy`] schema
|
|
|===
.HTTP responses
@@ -713,7 +713,7 @@ Description::
| Parameter | Type | Description
| `body`
| xref:../config_apis/imagepolicy-config-openshift-io-v1.adoc#imagepolicy-config-openshift-io-v1[`ImagePolicy`] schema
|
|
|===
.HTTP responses
@@ -815,7 +815,7 @@ Description::
| Parameter | Type | Description
| `body`
| xref:../config_apis/imagepolicy-config-openshift-io-v1.adoc#imagepolicy-config-openshift-io-v1[`ImagePolicy`] schema
|
|
|===
.HTTP responses