Skip to content
This repository was archived by the owner on Dec 6, 2024. It is now read-only.

Commit a581c87

Browse files
thotzthotz
committed
codegen update to the code
Signed-off-by: Jiffin Tony Thottan <[email protected]>
1 parent 18f05e9 commit a581c87

6 files changed

+196
-34
lines changed

Diff for: ‎crds/objectstorage.k8s.io_bucketaccessclasses.yaml

+41-6
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ apiVersion: apiextensions.k8s.io/v1
44
kind: CustomResourceDefinition
55
metadata:
66
annotations:
7-
controller-gen.kubebuilder.io/version: v0.5.0
7+
controller-gen.kubebuilder.io/version: v0.4.1
88
creationTimestamp: null
99
name: bucketaccessclasses.objectstorage.k8s.io
1010
spec:
@@ -21,10 +21,14 @@ spec:
2121
openAPIV3Schema:
2222
properties:
2323
apiVersion:
24-
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'
24+
description: 'APIVersion defines the versioned schema of this representation
25+
of an object. Servers should convert recognized schemas to the latest
26+
internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources'
2527
type: string
2628
kind:
27-
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'
29+
description: 'Kind is a string value representing the REST resource this
30+
object represents. Servers may infer this from the endpoint the client
31+
submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
2832
type: string
2933
metadata:
3034
type: object
@@ -33,13 +37,43 @@ spec:
3337
type: string
3438
type: object
3539
policyActionsConfigMap:
36-
description: 'ObjectReference contains enough information to let you inspect or modify the referred object. --- New uses of this type are discouraged because of difficulty describing its usage when embedded in APIs. 1. Ignored fields. It includes many fields which are not generally honored. For instance, ResourceVersion and FieldPath are both very rarely valid in actual usage. 2. Invalid usage help. It is impossible to add specific help for individual usage. In most embedded usages, there are particular restrictions like, "must refer only to types A and B" or "UID not honored" or "name must be restricted". Those cannot be well described when embedded. 3. Inconsistent validation. Because the usages are different, the validation rules are different by usage, which makes it hard for users to predict what will happen. 4. The fields are both imprecise and overly precise. Kind is not a precise mapping to a URL. This can produce ambiguity during interpretation and require a REST mapping. In most cases, the dependency is on the group,resource tuple and the version of the actual struct is irrelevant. 5. We cannot easily change it. Because this type is embedded in many locations, updates to this type will affect numerous schemas. Don''t make new APIs embed an underspecified API type they do not control. Instead of using this type, create a locally provided and used type that is well-focused on your reference. For example, ServiceReferences for admission registration: https://github.com/kubernetes/api/blob/release-1.17/admissionregistration/v1/types.go#L533 .'
40+
description: 'ObjectReference contains enough information to let you inspect
41+
or modify the referred object. --- New uses of this type are discouraged
42+
because of difficulty describing its usage when embedded in APIs. 1.
43+
Ignored fields. It includes many fields which are not generally honored. For
44+
instance, ResourceVersion and FieldPath are both very rarely valid in
45+
actual usage. 2. Invalid usage help. It is impossible to add specific
46+
help for individual usage. In most embedded usages, there are particular restrictions
47+
like, "must refer only to types A and B" or "UID not honored" or "name
48+
must be restricted". Those cannot be well described when embedded. 3.
49+
Inconsistent validation. Because the usages are different, the validation
50+
rules are different by usage, which makes it hard for users to predict
51+
what will happen. 4. The fields are both imprecise and overly precise. Kind
52+
is not a precise mapping to a URL. This can produce ambiguity during
53+
interpretation and require a REST mapping. In most cases, the dependency
54+
is on the group,resource tuple and the version of the actual struct
55+
is irrelevant. 5. We cannot easily change it. Because this type is
56+
embedded in many locations, updates to this type will affect numerous
57+
schemas. Don''t make new APIs embed an underspecified API type they
58+
do not control. Instead of using this type, create a locally provided
59+
and used type that is well-focused on your reference. For example, ServiceReferences
60+
for admission registration: https://github.com/kubernetes/api/blob/release-1.17/admissionregistration/v1/types.go#L533
61+
.'
3762
properties:
3863
apiVersion:
3964
description: API version of the referent.
4065
type: string
4166
fieldPath:
42-
description: 'If referring to a piece of an object instead of an entire object, this string should contain a valid JSON/Go field access statement, such as desiredState.manifest.containers[2]. For example, if the object reference is to a container within a pod, this would take on a value like: "spec.containers{name}" (where "name" refers to the name of the container that triggered the event) or if no container name is specified "spec.containers[2]" (container with index 2 in this pod). This syntax is chosen only to have some well-defined way of referencing a part of an object. TODO: this design is not final and this field is subject to change in the future.'
67+
description: 'If referring to a piece of an object instead of an entire
68+
object, this string should contain a valid JSON/Go field access
69+
statement, such as desiredState.manifest.containers[2]. For example,
70+
if the object reference is to a container within a pod, this would
71+
take on a value like: "spec.containers{name}" (where "name" refers
72+
to the name of the container that triggered the event) or if no
73+
container name is specified "spec.containers[2]" (container with
74+
index 2 in this pod). This syntax is chosen only to have some well-defined
75+
way of referencing a part of an object. TODO: this design is not
76+
final and this field is subject to change in the future.'
4377
type: string
4478
kind:
4579
description: 'Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
@@ -51,7 +85,8 @@ spec:
5185
description: 'Namespace of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/'
5286
type: string
5387
resourceVersion:
54-
description: 'Specific resourceVersion to which this reference is made, if any. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency'
88+
description: 'Specific resourceVersion to which this reference is
89+
made, if any. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency'
5590
type: string
5691
uid:
5792
description: 'UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids'

0 commit comments

Comments
 (0)