Ce contenu n'est pas disponible dans la langue sélectionnée.
Chapter 5. Console [operator.openshift.io/v1]
- Description
- Console provides a means to configure an operator to manage the console. Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).
- Type
-
object
- Required
-
spec
-
5.1. Specification
Property | Type | Description |
---|---|---|
|
| 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 |
|
| 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 |
| Standard object’s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata | |
|
| ConsoleSpec is the specification of the desired behavior of the Console. |
|
| ConsoleStatus defines the observed status of the Console. |
5.1.1. .spec
- Description
- ConsoleSpec is the specification of the desired behavior of the Console.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| customization is used to optionally provide a small set of customization options to the web console. |
|
| ingress allows to configure the alternative ingress for the console. This field is intended for clusters without ingress capability, where access to routes is not possible. |
|
| logLevel is an intent based logging for an overall component. It does not give fine grained control, but it is a simple way to manage coarse grained logging choices that operators have to interpret for their operands. Valid values are: "Normal", "Debug", "Trace", "TraceAll". Defaults to "Normal". |
|
| managementState indicates whether and how the operator should manage the component |
| `` | observedConfig holds a sparse config that controller has observed from the cluster state. It exists in spec because it is an input to the level for the operator |
|
| operatorLogLevel is an intent based logging for the operator itself. It does not give fine grained control, but it is a simple way to manage coarse grained logging choices that operators have to interpret for themselves. Valid values are: "Normal", "Debug", "Trace", "TraceAll". Defaults to "Normal". |
|
| plugins defines a list of enabled console plugin names. |
|
| providers contains configuration for using specific service providers. |
|
| route contains hostname and secret reference that contains the serving certificate. If a custom route is specified, a new route will be created with the provided hostname, under which console will be available. In case of custom hostname uses the default routing suffix of the cluster, the Secret specification for a serving certificate will not be needed. In case of custom hostname points to an arbitrary domain, manual DNS configurations steps are necessary. The default console route will be maintained to reserve the default hostname for console if the custom route is removed. If not specified, default route will be used. DEPRECATED |
| `` | unsupportedConfigOverrides overrides the final configuration that was computed by the operator. Red Hat does not support the use of this field. Misuse of this field could lead to unexpected behavior or conflict with other configuration options. Seek guidance from the Red Hat support before using this field. Use of this property blocks cluster upgrades, it must be removed before upgrading your cluster. |
5.1.2. .spec.customization
- Description
- customization is used to optionally provide a small set of customization options to the web console.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| addPage allows customizing actions on the Add page in developer perspective. |
|
| brand is the default branding of the web console which can be overridden by providing the brand field. There is a limited set of specific brand options. This field controls elements of the console such as the logo. Invalid value will prevent a console rollout. |
|
| capabilities defines an array of capabilities that can be interacted with in the console UI. Each capability defines a visual state that can be interacted with the console to render in the UI. Available capabilities are LightspeedButton. Each of the available capabilities may appear only once in the list. |
|
| Capabilities contains set of UI capabilities and their state in the console UI. |
|
| customLogoFile replaces the default OpenShift logo in the masthead and about dialog. It is a reference to a ConfigMap in the openshift-config namespace. This can be created with a command like 'oc create configmap custom-logo --from-file=/path/to/file -n openshift-config'. Image size must be less than 1 MB due to constraints on the ConfigMap size. The ConfigMap key should include a file extension so that the console serves the file with the correct MIME type. Recommended logo specifications: Dimensions: Max height of 68px and max width of 200px SVG format preferred |
|
| customProductName is the name that will be displayed in page titles, logo alt text, and the about dialog instead of the normal OpenShift product name. |
|
| developerCatalog allows to configure the shown developer catalog categories (filters) and types (sub-catalogs). |
|
| documentationBaseURL links to external documentation are shown in various sections of the web console. Providing documentationBaseURL will override the default documentation URL. Invalid value will prevent a console rollout. |
|
| perspectives allows enabling/disabling of perspective(s) that user can see in the Perspective switcher dropdown. |
|
| Perspective defines a perspective that cluster admins want to show/hide in the perspective switcher dropdown |
|
| projectAccess allows customizing the available list of ClusterRoles in the Developer perspective Project access page which can be used by a project admin to specify roles to other users and restrict access within the project. If set, the list will replace the default ClusterRole options. |
|
| quickStarts allows customization of available ConsoleQuickStart resources in console. |
5.1.3. .spec.customization.addPage
- Description
- addPage allows customizing actions on the Add page in developer perspective.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| disabledActions is a list of actions that are not shown to users. Each action in the list is represented by its ID. |
5.1.4. .spec.customization.capabilities
- Description
- capabilities defines an array of capabilities that can be interacted with in the console UI. Each capability defines a visual state that can be interacted with the console to render in the UI. Available capabilities are LightspeedButton. Each of the available capabilities may appear only once in the list.
- Type
-
array
5.1.5. .spec.customization.capabilities[]
- Description
- Capabilities contains set of UI capabilities and their state in the console UI.
- Type
-
object
- Required
-
name
-
visibility
-
Property | Type | Description |
---|---|---|
|
| name is the unique name of a capability. Available capabilities are LightspeedButton. |
|
| visibility defines the visibility state of the capability. |
5.1.6. .spec.customization.capabilities[].visibility
- Description
- visibility defines the visibility state of the capability.
- Type
-
object
- Required
-
state
-
Property | Type | Description |
---|---|---|
|
| state defines if the capability is enabled or disabled in the console UI. Enabling the capability in the console UI is represented by the "Enabled" value. Disabling the capability in the console UI is represented by the "Disabled" value. |
5.1.7. .spec.customization.customLogoFile
- Description
- customLogoFile replaces the default OpenShift logo in the masthead and about dialog. It is a reference to a ConfigMap in the openshift-config namespace. This can be created with a command like 'oc create configmap custom-logo --from-file=/path/to/file -n openshift-config'. Image size must be less than 1 MB due to constraints on the ConfigMap size. The ConfigMap key should include a file extension so that the console serves the file with the correct MIME type. Recommended logo specifications: Dimensions: Max height of 68px and max width of 200px SVG format preferred
- Type
-
object
Property | Type | Description |
---|---|---|
|
| Key allows pointing to a specific key/value inside of the configmap. This is useful for logical file references. |
|
|
5.1.8. .spec.customization.developerCatalog
- Description
- developerCatalog allows to configure the shown developer catalog categories (filters) and types (sub-catalogs).
- Type
-
object
Property | Type | Description |
---|---|---|
|
| categories which are shown in the developer catalog. |
|
| DeveloperConsoleCatalogCategory for the developer console catalog. |
|
| types allows enabling or disabling of sub-catalog types that user can see in the Developer catalog. When omitted, all the sub-catalog types will be shown. |
5.1.9. .spec.customization.developerCatalog.categories
- Description
- categories which are shown in the developer catalog.
- Type
-
array
5.1.10. .spec.customization.developerCatalog.categories[]
- Description
- DeveloperConsoleCatalogCategory for the developer console catalog.
- Type
-
object
- Required
-
id
-
label
-
Property | Type | Description |
---|---|---|
|
| ID is an identifier used in the URL to enable deep linking in console. ID is required and must have 1-32 URL safe (A-Z, a-z, 0-9, - and _) characters. |
|
| label defines a category display label. It is required and must have 1-64 characters. |
|
| subcategories defines a list of child categories. |
|
| DeveloperConsoleCatalogCategoryMeta are the key identifiers of a developer catalog category. |
|
| tags is a list of strings that will match the category. A selected category show all items which has at least one overlapping tag between category and item. |
5.1.11. .spec.customization.developerCatalog.categories[].subcategories
- Description
- subcategories defines a list of child categories.
- Type
-
array
5.1.12. .spec.customization.developerCatalog.categories[].subcategories[]
- Description
- DeveloperConsoleCatalogCategoryMeta are the key identifiers of a developer catalog category.
- Type
-
object
- Required
-
id
-
label
-
Property | Type | Description |
---|---|---|
|
| ID is an identifier used in the URL to enable deep linking in console. ID is required and must have 1-32 URL safe (A-Z, a-z, 0-9, - and _) characters. |
|
| label defines a category display label. It is required and must have 1-64 characters. |
|
| tags is a list of strings that will match the category. A selected category show all items which has at least one overlapping tag between category and item. |
5.1.13. .spec.customization.developerCatalog.types
- Description
- types allows enabling or disabling of sub-catalog types that user can see in the Developer catalog. When omitted, all the sub-catalog types will be shown.
- Type
-
object
- Required
-
state
-
Property | Type | Description |
---|---|---|
|
| disabled is a list of developer catalog types (sub-catalogs IDs) that are not shown to users. Types (sub-catalogs) are added via console plugins, the available types (sub-catalog IDs) are available in the console on the cluster configuration page, or when editing the YAML in the console. Example: "Devfile", "HelmChart", "BuilderImage" If the list is empty or all the available sub-catalog types are added, then the complete developer catalog should be hidden. |
|
| enabled is a list of developer catalog types (sub-catalogs IDs) that will be shown to users. Types (sub-catalogs) are added via console plugins, the available types (sub-catalog IDs) are available in the console on the cluster configuration page, or when editing the YAML in the console. Example: "Devfile", "HelmChart", "BuilderImage" If the list is non-empty, a new type will not be shown to the user until it is added to list. If the list is empty the complete developer catalog will be shown. |
|
| state defines if a list of catalog types should be enabled or disabled. |
5.1.14. .spec.customization.perspectives
- Description
- perspectives allows enabling/disabling of perspective(s) that user can see in the Perspective switcher dropdown.
- Type
-
array
5.1.15. .spec.customization.perspectives[]
- Description
- Perspective defines a perspective that cluster admins want to show/hide in the perspective switcher dropdown
- Type
-
object
- Required
-
id
-
visibility
-
Property | Type | Description |
---|---|---|
|
| id defines the id of the perspective. Example: "dev", "admin". The available perspective ids can be found in the code snippet section next to the yaml editor. Incorrect or unknown ids will be ignored. |
|
|
pinnedResources defines the list of default pinned resources that users will see on the perspective navigation if they have not customized these pinned resources themselves. The list of available Kubernetes resources could be read via |
|
| PinnedResourceReference includes the group, version and type of resource |
|
| visibility defines the state of perspective along with access review checks if needed for that perspective. |
5.1.16. .spec.customization.perspectives[].pinnedResources
- Description
-
pinnedResources defines the list of default pinned resources that users will see on the perspective navigation if they have not customized these pinned resources themselves. The list of available Kubernetes resources could be read via
kubectl api-resources
. The console will also provide a configuration UI and a YAML snippet that will list the available resources that can be pinned to the navigation. Incorrect or unknown resources will be ignored. - Type
-
array
5.1.17. .spec.customization.perspectives[].pinnedResources[]
- Description
- PinnedResourceReference includes the group, version and type of resource
- Type
-
object
- Required
-
group
-
resource
-
version
-
Property | Type | Description |
---|---|---|
|
| group is the API Group of the Resource. Enter empty string for the core group. This value should consist of only lowercase alphanumeric characters, hyphens and periods. Example: "", "apps", "build.openshift.io", etc. |
|
| resource is the type that is being referenced. It is normally the plural form of the resource kind in lowercase. This value should consist of only lowercase alphanumeric characters and hyphens. Example: "deployments", "deploymentconfigs", "pods", etc. |
|
| version is the API Version of the Resource. This value should consist of only lowercase alphanumeric characters. Example: "v1", "v1beta1", etc. |
5.1.18. .spec.customization.perspectives[].visibility
- Description
- visibility defines the state of perspective along with access review checks if needed for that perspective.
- Type
-
object
- Required
-
state
-
Property | Type | Description |
---|---|---|
|
| accessReview defines required and missing access review checks. |
|
| state defines the perspective is enabled or disabled or access review check is required. |
5.1.19. .spec.customization.perspectives[].visibility.accessReview
- Description
- accessReview defines required and missing access review checks.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| missing defines a list of permission checks. The perspective will only be shown when at least one check fails. When omitted, the access review is skipped and the perspective will not be shown unless it is required to do so based on the configuration of the required access review list. |
|
| ResourceAttributes includes the authorization attributes available for resource requests to the Authorizer interface |
|
| required defines a list of permission checks. The perspective will only be shown when all checks are successful. When omitted, the access review is skipped and the perspective will not be shown unless it is required to do so based on the configuration of the missing access review list. |
|
| ResourceAttributes includes the authorization attributes available for resource requests to the Authorizer interface |
5.1.20. .spec.customization.perspectives[].visibility.accessReview.missing
- Description
- missing defines a list of permission checks. The perspective will only be shown when at least one check fails. When omitted, the access review is skipped and the perspective will not be shown unless it is required to do so based on the configuration of the required access review list.
- Type
-
array
5.1.21. .spec.customization.perspectives[].visibility.accessReview.missing[]
- Description
- ResourceAttributes includes the authorization attributes available for resource requests to the Authorizer interface
- Type
-
object
Property | Type | Description |
---|---|---|
|
| Group is the API Group of the Resource. "*" means all. |
|
| Name is the name of the resource being requested for a "get" or deleted for a "delete". "" (empty) means all. |
|
| Namespace is the namespace of the action being requested. Currently, there is no distinction between no namespace and all namespaces "" (empty) is defaulted for LocalSubjectAccessReviews "" (empty) is empty for cluster-scoped resources "" (empty) means "all" for namespace scoped resources from a SubjectAccessReview or SelfSubjectAccessReview |
|
| Resource is one of the existing resource types. "*" means all. |
|
| Subresource is one of the existing resource types. "" means none. |
|
| Verb is a kubernetes resource API verb, like: get, list, watch, create, update, delete, proxy. "*" means all. |
|
| Version is the API Version of the Resource. "*" means all. |
5.1.22. .spec.customization.perspectives[].visibility.accessReview.required
- Description
- required defines a list of permission checks. The perspective will only be shown when all checks are successful. When omitted, the access review is skipped and the perspective will not be shown unless it is required to do so based on the configuration of the missing access review list.
- Type
-
array
5.1.23. .spec.customization.perspectives[].visibility.accessReview.required[]
- Description
- ResourceAttributes includes the authorization attributes available for resource requests to the Authorizer interface
- Type
-
object
Property | Type | Description |
---|---|---|
|
| Group is the API Group of the Resource. "*" means all. |
|
| Name is the name of the resource being requested for a "get" or deleted for a "delete". "" (empty) means all. |
|
| Namespace is the namespace of the action being requested. Currently, there is no distinction between no namespace and all namespaces "" (empty) is defaulted for LocalSubjectAccessReviews "" (empty) is empty for cluster-scoped resources "" (empty) means "all" for namespace scoped resources from a SubjectAccessReview or SelfSubjectAccessReview |
|
| Resource is one of the existing resource types. "*" means all. |
|
| Subresource is one of the existing resource types. "" means none. |
|
| Verb is a kubernetes resource API verb, like: get, list, watch, create, update, delete, proxy. "*" means all. |
|
| Version is the API Version of the Resource. "*" means all. |
5.1.24. .spec.customization.projectAccess
- Description
- projectAccess allows customizing the available list of ClusterRoles in the Developer perspective Project access page which can be used by a project admin to specify roles to other users and restrict access within the project. If set, the list will replace the default ClusterRole options.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| availableClusterRoles is the list of ClusterRole names that are assignable to users through the project access tab. |
5.1.25. .spec.customization.quickStarts
- Description
- quickStarts allows customization of available ConsoleQuickStart resources in console.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| disabled is a list of ConsoleQuickStart resource names that are not shown to users. |
5.1.26. .spec.ingress
- Description
- ingress allows to configure the alternative ingress for the console. This field is intended for clusters without ingress capability, where access to routes is not possible.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| clientDownloadsURL is a URL to be used as the address to download client binaries. If not specified, the downloads route hostname will be used. This field is required for clusters without ingress capability, where access to routes is not possible. The console operator will monitor the URL and may go degraded if it’s unreachable for an extended period. Must use the HTTPS scheme. |
|
| consoleURL is a URL to be used as the base console address. If not specified, the console route hostname will be used. This field is required for clusters without ingress capability, where access to routes is not possible. Make sure that appropriate ingress is set up at this URL. The console operator will monitor the URL and may go degraded if it’s unreachable for an extended period. Must use the HTTPS scheme. |
5.1.27. .spec.providers
- Description
- providers contains configuration for using specific service providers.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| statuspage contains ID for statuspage.io page that provides status info about. |
5.1.28. .spec.providers.statuspage
- Description
- statuspage contains ID for statuspage.io page that provides status info about.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| pageID is the unique ID assigned by Statuspage for your page. This must be a public page. |
5.1.29. .spec.route
- Description
- route contains hostname and secret reference that contains the serving certificate. If a custom route is specified, a new route will be created with the provided hostname, under which console will be available. In case of custom hostname uses the default routing suffix of the cluster, the Secret specification for a serving certificate will not be needed. In case of custom hostname points to an arbitrary domain, manual DNS configurations steps are necessary. The default console route will be maintained to reserve the default hostname for console if the custom route is removed. If not specified, default route will be used. DEPRECATED
- Type
-
object
Property | Type | Description |
---|---|---|
|
| hostname is the desired custom domain under which console will be available. |
|
| secret points to secret in the openshift-config namespace that contains custom certificate and key and needs to be created manually by the cluster admin. Referenced Secret is required to contain following key value pairs: - "tls.crt" - to specifies custom certificate - "tls.key" - to specifies private key of the custom certificate If the custom hostname uses the default routing suffix of the cluster, the Secret specification for a serving certificate will not be needed. |
5.1.30. .spec.route.secret
- Description
- secret points to secret in the openshift-config namespace that contains custom certificate and key and needs to be created manually by the cluster admin. Referenced Secret is required to contain following key value pairs: - "tls.crt" - to specifies custom certificate - "tls.key" - to specifies private key of the custom certificate If the custom hostname uses the default routing suffix of the cluster, the Secret specification for a serving certificate will not be needed.
- Type
-
object
- Required
-
name
-
Property | Type | Description |
---|---|---|
|
| name is the metadata.name of the referenced secret |
5.1.31. .status
- Description
- ConsoleStatus defines the observed status of the Console.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| conditions is a list of conditions and their status |
|
| OperatorCondition is just the standard condition fields. |
|
| generations are used to determine when an item needs to be reconciled or has changed in a way that needs a reaction. |
|
| GenerationStatus keeps track of the generation for a given resource so that decisions about forced updates can be made. |
|
| observedGeneration is the last generation change you’ve dealt with |
|
| readyReplicas indicates how many replicas are ready and at the desired state |
|
| version is the level this availability applies to |
5.1.32. .status.conditions
- Description
- conditions is a list of conditions and their status
- Type
-
array
5.1.33. .status.conditions[]
- Description
- OperatorCondition is just the standard condition fields.
- Type
-
object
- Required
-
type
-
Property | Type | Description |
---|---|---|
|
| |
|
| |
|
| |
|
| |
|
|
5.1.34. .status.generations
- Description
- generations are used to determine when an item needs to be reconciled or has changed in a way that needs a reaction.
- Type
-
array
5.1.35. .status.generations[]
- Description
- GenerationStatus keeps track of the generation for a given resource so that decisions about forced updates can be made.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| group is the group of the thing you’re tracking |
|
| hash is an optional field set for resources without generation that are content sensitive like secrets and configmaps |
|
| lastGeneration is the last generation of the workload controller involved |
|
| name is the name of the thing you’re tracking |
|
| namespace is where the thing you’re tracking is |
|
| resource is the resource type of the thing you’re tracking |
5.2. API endpoints
The following API endpoints are available:
/apis/operator.openshift.io/v1/consoles
-
DELETE
: delete collection of Console -
GET
: list objects of kind Console -
POST
: create a Console
-
/apis/operator.openshift.io/v1/consoles/{name}
-
DELETE
: delete a Console -
GET
: read the specified Console -
PATCH
: partially update the specified Console -
PUT
: replace the specified Console
-
/apis/operator.openshift.io/v1/consoles/{name}/status
-
GET
: read status of the specified Console -
PATCH
: partially update status of the specified Console -
PUT
: replace status of the specified Console
-
5.2.1. /apis/operator.openshift.io/v1/consoles
- HTTP method
-
DELETE
- Description
- delete collection of Console
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- list objects of kind Console
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
POST
- Description
- create a Console
Parameter | Type | Description |
---|---|---|
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
| fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
5.2.2. /apis/operator.openshift.io/v1/consoles/{name}
Parameter | Type | Description |
---|---|---|
|
| name of the Console |
- HTTP method
-
DELETE
- Description
- delete a Console
Parameter | Type | Description |
---|---|---|
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
HTTP code | Reponse body |
---|---|
200 - OK |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- read the specified Console
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update the specified Console
Parameter | Type | Description |
---|---|---|
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
| fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace the specified Console
Parameter | Type | Description |
---|---|---|
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
| fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
5.2.3. /apis/operator.openshift.io/v1/consoles/{name}/status
Parameter | Type | Description |
---|---|---|
|
| name of the Console |
- HTTP method
-
GET
- Description
- read status of the specified Console
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update status of the specified Console
Parameter | Type | Description |
---|---|---|
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
| fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace status of the specified Console
Parameter | Type | Description |
---|---|---|
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
| fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |