Skip to content

Commit 7668707

Browse files
author
Yann Hamon
committed
Adding new schemas
1 parent f74bae3 commit 7668707

File tree

18,628 files changed

+7575476
-202
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

18,628 files changed

+7575476
-202
lines changed

master-local/_definitions.json

Lines changed: 100 additions & 10 deletions
Large diffs are not rendered by default.

master-local/all.json

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -528,6 +528,15 @@
528528
{
529529
"$ref": "_definitions.json#/definitions/io.k8s.api.certificates.v1alpha1.ClusterTrustBundleSpec"
530530
},
531+
{
532+
"$ref": "_definitions.json#/definitions/io.k8s.api.certificates.v1beta1.ClusterTrustBundle"
533+
},
534+
{
535+
"$ref": "_definitions.json#/definitions/io.k8s.api.certificates.v1beta1.ClusterTrustBundleList"
536+
},
537+
{
538+
"$ref": "_definitions.json#/definitions/io.k8s.api.certificates.v1beta1.ClusterTrustBundleSpec"
539+
},
531540
{
532541
"$ref": "_definitions.json#/definitions/io.k8s.api.coordination.v1.Lease"
533542
},
Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
{
2+
"description": "ClusterTrustBundle is a cluster-scoped container for X.509 trust anchors (root certificates).\n\nClusterTrustBundle objects are considered to be readable by any authenticated user in the cluster, because they can be mounted by pods using the `clusterTrustBundle` projection. All service accounts have read access to ClusterTrustBundles by default. Users who only have namespace-level access to a cluster can read ClusterTrustBundles by impersonating a serviceaccount that they have access to.\n\nIt can be optionally associated with a particular assigner, in which case it contains one valid set of trust anchors for that signer. Signers may have multiple associated ClusterTrustBundles; each is an independent set of trust anchors for that signer. Admission control is used to enforce that only users with permissions on the signer can create or modify the corresponding bundle.",
3+
"properties": {
4+
"apiVersion": {
5+
"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",
6+
"type": [
7+
"string",
8+
"null"
9+
],
10+
"enum": [
11+
"certificates.k8s.io/v1beta1"
12+
]
13+
},
14+
"kind": {
15+
"description": "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",
16+
"type": [
17+
"string",
18+
"null"
19+
],
20+
"enum": [
21+
"ClusterTrustBundle"
22+
]
23+
},
24+
"metadata": {
25+
"$ref": "_definitions.json#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta",
26+
"description": "metadata contains the object metadata."
27+
},
28+
"spec": {
29+
"$ref": "_definitions.json#/definitions/io.k8s.api.certificates.v1beta1.ClusterTrustBundleSpec",
30+
"description": "spec contains the signer (if any) and trust anchors."
31+
}
32+
},
33+
"required": [
34+
"spec"
35+
],
36+
"type": "object",
37+
"x-kubernetes-group-version-kind": [
38+
{
39+
"group": "certificates.k8s.io",
40+
"kind": "ClusterTrustBundle",
41+
"version": "v1beta1"
42+
}
43+
],
44+
"$schema": "http://json-schema.org/schema#"
45+
}

master-local/clustertrustbundle.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@
2323
"description": "metadata contains the object metadata."
2424
},
2525
"spec": {
26-
"$ref": "_definitions.json#/definitions/io.k8s.api.certificates.v1alpha1.ClusterTrustBundleSpec",
26+
"$ref": "_definitions.json#/definitions/io.k8s.api.certificates.v1beta1.ClusterTrustBundleSpec",
2727
"description": "spec contains the signer (if any) and trust anchors."
2828
}
2929
},
@@ -35,7 +35,7 @@
3535
{
3636
"group": "certificates.k8s.io",
3737
"kind": "ClusterTrustBundle",
38-
"version": "v1alpha1"
38+
"version": "v1beta1"
3939
}
4040
],
4141
"$schema": "http://json-schema.org/schema#"
Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
{
2+
"description": "ClusterTrustBundleList is a collection of ClusterTrustBundle objects",
3+
"properties": {
4+
"apiVersion": {
5+
"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",
6+
"type": [
7+
"string",
8+
"null"
9+
],
10+
"enum": [
11+
"certificates.k8s.io/v1beta1"
12+
]
13+
},
14+
"items": {
15+
"description": "items is a collection of ClusterTrustBundle objects",
16+
"items": {
17+
"$ref": "_definitions.json#/definitions/io.k8s.api.certificates.v1beta1.ClusterTrustBundle"
18+
},
19+
"type": [
20+
"array",
21+
"null"
22+
]
23+
},
24+
"kind": {
25+
"description": "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",
26+
"type": [
27+
"string",
28+
"null"
29+
],
30+
"enum": [
31+
"ClusterTrustBundleList"
32+
]
33+
},
34+
"metadata": {
35+
"$ref": "_definitions.json#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta",
36+
"description": "metadata contains the list metadata."
37+
}
38+
},
39+
"required": [
40+
"items"
41+
],
42+
"type": "object",
43+
"x-kubernetes-group-version-kind": [
44+
{
45+
"group": "certificates.k8s.io",
46+
"kind": "ClusterTrustBundleList",
47+
"version": "v1beta1"
48+
}
49+
],
50+
"$schema": "http://json-schema.org/schema#"
51+
}

master-local/clustertrustbundlelist.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@
1111
"items": {
1212
"description": "items is a collection of ClusterTrustBundle objects",
1313
"items": {
14-
"$ref": "_definitions.json#/definitions/io.k8s.api.certificates.v1alpha1.ClusterTrustBundle"
14+
"$ref": "_definitions.json#/definitions/io.k8s.api.certificates.v1beta1.ClusterTrustBundle"
1515
},
1616
"type": [
1717
"array",
@@ -41,7 +41,7 @@
4141
{
4242
"group": "certificates.k8s.io",
4343
"kind": "ClusterTrustBundleList",
44-
"version": "v1alpha1"
44+
"version": "v1beta1"
4545
}
4646
],
4747
"$schema": "http://json-schema.org/schema#"
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
{
2+
"description": "ClusterTrustBundleSpec contains the signer and trust anchors.",
3+
"properties": {
4+
"signerName": {
5+
"description": "signerName indicates the associated signer, if any.\n\nIn order to create or update a ClusterTrustBundle that sets signerName, you must have the following cluster-scoped permission: group=certificates.k8s.io resource=signers resourceName=<the signer name> verb=attest.\n\nIf signerName is not empty, then the ClusterTrustBundle object must be named with the signer name as a prefix (translating slashes to colons). For example, for the signer name `example.com/foo`, valid ClusterTrustBundle object names include `example.com:foo:abc` and `example.com:foo:v1`.\n\nIf signerName is empty, then the ClusterTrustBundle object's name must not have such a prefix.\n\nList/watch requests for ClusterTrustBundles can filter on this field using a `spec.signerName=NAME` field selector.",
6+
"type": [
7+
"string",
8+
"null"
9+
]
10+
},
11+
"trustBundle": {
12+
"description": "trustBundle contains the individual X.509 trust anchors for this bundle, as PEM bundle of PEM-wrapped, DER-formatted X.509 certificates.\n\nThe data must consist only of PEM certificate blocks that parse as valid X.509 certificates. Each certificate must include a basic constraints extension with the CA bit set. The API server will reject objects that contain duplicate certificates, or that use PEM block headers.\n\nUsers of ClusterTrustBundles, including Kubelet, are free to reorder and deduplicate certificate blocks in this file according to their own logic, as well as to drop PEM block headers and inter-block data.",
13+
"type": [
14+
"string",
15+
"null"
16+
]
17+
}
18+
},
19+
"required": [
20+
"trustBundle"
21+
],
22+
"type": "object",
23+
"$schema": "http://json-schema.org/schema#"
24+
}

master-local/endpoint-discovery-v1.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
"description": "Endpoint represents a single logical \"backend\" implementing a service.",
33
"properties": {
44
"addresses": {
5-
"description": "addresses of this endpoint. The contents of this field are interpreted according to the corresponding EndpointSlice addressType field. Consumers must handle different types of addresses in the context of their own capabilities. This must contain at least one address but no more than 100. These are all assumed to be fungible and clients may choose to only use the first element. Refer to: https://issue.k8s.io/106267",
5+
"description": "addresses of this endpoint. For EndpointSlices of addressType \"IPv4\" or \"IPv6\", the values are IP addresses in canonical form. The syntax and semantics of other addressType values are not defined. This must contain at least one address but no more than 100. EndpointSlices generated by the EndpointSlice controller will always have exactly 1 address. No semantics are defined for additional addresses beyond the first, and kube-proxy does not look at them.",
66
"items": {
77
"type": [
88
"string",

master-local/endpoint.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
"description": "Endpoint represents a single logical \"backend\" implementing a service.",
33
"properties": {
44
"addresses": {
5-
"description": "addresses of this endpoint. The contents of this field are interpreted according to the corresponding EndpointSlice addressType field. Consumers must handle different types of addresses in the context of their own capabilities. This must contain at least one address but no more than 100. These are all assumed to be fungible and clients may choose to only use the first element. Refer to: https://issue.k8s.io/106267",
5+
"description": "addresses of this endpoint. For EndpointSlices of addressType \"IPv4\" or \"IPv6\", the values are IP addresses in canonical form. The syntax and semantics of other addressType values are not defined. This must contain at least one address but no more than 100. EndpointSlices generated by the EndpointSlice controller will always have exactly 1 address. No semantics are defined for additional addresses beyond the first, and kube-proxy does not look at them.",
66
"items": {
77
"type": [
88
"string",

master-local/endpointconditions-discovery-v1.json

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,21 +2,21 @@
22
"description": "EndpointConditions represents the current condition of an endpoint.",
33
"properties": {
44
"ready": {
5-
"description": "ready indicates that this endpoint is prepared to receive traffic, according to whatever system is managing the endpoint. A nil value indicates an unknown state. In most cases consumers should interpret this unknown state as ready. For compatibility reasons, ready should never be \"true\" for terminating endpoints, except when the normal readiness behavior is being explicitly overridden, for example when the associated Service has set the publishNotReadyAddresses flag.",
5+
"description": "ready indicates that this endpoint is ready to receive traffic, according to whatever system is managing the endpoint. A nil value should be interpreted as \"true\". In general, an endpoint should be marked ready if it is serving and not terminating, though this can be overridden in some cases, such as when the associated Service has set the publishNotReadyAddresses flag.",
66
"type": [
77
"boolean",
88
"null"
99
]
1010
},
1111
"serving": {
12-
"description": "serving is identical to ready except that it is set regardless of the terminating state of endpoints. This condition should be set to true for a ready endpoint that is terminating. If nil, consumers should defer to the ready condition.",
12+
"description": "serving indicates that this endpoint is able to receive traffic, according to whatever system is managing the endpoint. For endpoints backed by pods, the EndpointSlice controller will mark the endpoint as serving if the pod's Ready condition is True. A nil value should be interpreted as \"true\".",
1313
"type": [
1414
"boolean",
1515
"null"
1616
]
1717
},
1818
"terminating": {
19-
"description": "terminating indicates that this endpoint is terminating. A nil value indicates an unknown state. Consumers should interpret this unknown state to mean that the endpoint is not terminating.",
19+
"description": "terminating indicates that this endpoint is terminating. A nil value should be interpreted as \"false\".",
2020
"type": [
2121
"boolean",
2222
"null"

0 commit comments

Comments
 (0)