Merge pull request #36317 from jboxman/ocp-apis-49

APIs 4.9

Author: jboxman

_topic_map.yml

@@ -2463,8 +2463,8 @@ Topics:
     File: installplan-operators-coreos-com-v1alpha1
   - Name: 'Operator [operators.coreos.com/v1]'
     File: operator-operators-coreos-com-v1
-  - Name: 'OperatorCondition [operators.coreos.com/v1]'
-    File: operatorcondition-operators-coreos-com-v1
+  - Name: 'OperatorCondition [operators.coreos.com/v2]'
+    File: operatorcondition-operators-coreos-com-v2
   - Name: 'OperatorGroup [operators.coreos.com/v1]'
     File: operatorgroup-operators-coreos-com-v1
   - Name: 'PackageManifest [packages.operators.coreos.com/v1]'

api-config.yaml

@@ -781,7 +781,7 @@ apiMap:
     namespaced: false
   - kind: OperatorCondition
     group: operators.coreos.com
-    version: v1
+    version: v2
     plural: operatorconditions
     namespaced: true
   - kind: OperatorGroup

rest_api/authorization_apis/localsubjectaccessreview-authorization-k8s-io-v1.adoc

@@ -36,7 +36,7 @@ Required::
 
 | `metadata`
 | xref:../objects/index.adoc#objectmeta-meta-v1[`ObjectMeta meta/v1`]
-| 
+| Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
 
 | `spec`
 | `object`

rest_api/authorization_apis/selfsubjectaccessreview-authorization-k8s-io-v1.adoc

@@ -36,7 +36,7 @@ Required::
 
 | `metadata`
 | xref:../objects/index.adoc#objectmeta-meta-v1[`ObjectMeta meta/v1`]
-| 
+| Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
 
 | `spec`
 | `object`

rest_api/authorization_apis/selfsubjectrulesreview-authorization-k8s-io-v1.adoc

@@ -36,11 +36,11 @@ Required::
 
 | `metadata`
 | xref:../objects/index.adoc#objectmeta-meta-v1[`ObjectMeta meta/v1`]
-| 
+| Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
 
 | `spec`
 | `object`
-| Spec holds information about the request being evaluated.
+| SelfSubjectRulesReviewSpec defines the specification for SelfSubjectRulesReview.
 
 | `status`
 | `object`
@@ -51,7 +51,7 @@ Required::
 Description::
 +
 --
-Spec holds information about the request being evaluated.
+SelfSubjectRulesReviewSpec defines the specification for SelfSubjectRulesReview.
 --
 
 Type::

rest_api/authorization_apis/subjectaccessreview-authorization-k8s-io-v1.adoc

@@ -36,7 +36,7 @@ Required::
 
 | `metadata`
 | xref:../objects/index.adoc#objectmeta-meta-v1[`ObjectMeta meta/v1`]
-| 
+| Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
 
 | `spec`
 | `object`

rest_api/authorization_apis/tokenreview-authentication-k8s-io-v1.adoc

@@ -36,7 +36,7 @@ Required::
 
 | `metadata`
 | xref:../objects/index.adoc#objectmeta-meta-v1[`ObjectMeta meta/v1`]
-| 
+| Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
 
 | `spec`
 | `object`

…s/tokenreview-oauth-openshift-io-v1.adoc …s/tokenreview-oauth-openshift-io-v1.adocrest_api/oauth_apis/tokenreview-oauth-openshift-io-v1.adoc renamed to rest_api/authorization_apis/tokenreview-oauth-openshift-io-v1.adoc rest_api/oauth_apis/tokenreview-oauth-openshift-io-v1.adoc renamed to rest_api/authorization_apis/tokenreview-oauth-openshift-io-v1.adoc

@@ -336,7 +336,7 @@ Description::
 | Parameter | Type | Description
 | `allowWatchBookmarks`
 | `boolean`
-| allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
+| allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.
 | `continue`
 | `string`
 | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".
@@ -393,7 +393,7 @@ Description::
 | Parameter | Type | Description
 | `allowWatchBookmarks`
 | `boolean`
-| allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
+| allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.
 | `continue`
 | `string`
 | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".

rest_api/autoscale_apis/clusterautoscaler-autoscaling-openshift-io-v1.adoc

@@ -187,7 +187,7 @@ The following API endpoints are available:
 | Parameter | Type | Description
 | `allowWatchBookmarks`
 | `boolean`
-| allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
+| allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.
 | `continue`
 | `string`
 | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".
@@ -345,7 +345,7 @@ Description::
 | Parameter | Type | Description
 | `allowWatchBookmarks`
 | `boolean`
-| allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
+| allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.
 | `continue`
 | `string`
 | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".