You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[deps] Kubernetes dep upgrades and go version upgrade (#557)
* upgrade kubenetes dependencies to latest
* Upgrade to go 1.23 & switch to using v0.32.0-alpha.3 for conversion-gen since that is the only release ver that supports go 1.23
* switch chainsaw version to 0.2.11
* Update devbox json
* updated devbox.lock
---------
Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
ObjectReference contains enough information to let you inspect or modify the referred object.
125
-
---
126
-
New uses of this type are discouraged because of difficulty describing its usage when embedded in APIs.
127
-
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.
128
-
2. Invalid usage help. It is impossible to add specific help for individual usage. In most embedded usages, there are particular
129
-
restrictions like, "must refer only to types A and B" or "UID not honored" or "name must be restricted".
130
-
Those cannot be well described when embedded.
131
-
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.
132
-
4. The fields are both imprecise and overly precise. Kind is not a precise mapping to a URL. This can produce ambiguity
133
-
during interpretation and require a REST mapping. In most cases, the dependency is on the group,resource tuple
134
-
and the version of the actual struct is irrelevant.
135
-
5. We cannot easily change it. Because this type is embedded in many locations, updates to this type
136
-
will affect numerous schemas. Don't make new APIs embed an underspecified API type they do not control.
137
-
138
-
139
-
Instead of using this type, create a locally provided and used type that is well-focused on your reference.
140
-
For example, ServiceReferences for admission registration: https://github.com/kubernetes/api/blob/release-1.17/admissionregistration/v1/types.go#L533 .
123
+
description: ObjectReference contains enough information to let you
124
+
inspect or modify the referred object.
141
125
properties:
142
126
apiVersion:
143
127
description: API version of the referent.
@@ -151,7 +135,6 @@ spec:
151
135
the event) or if no container name is specified "spec.containers[2]" (container with
152
136
index 2 in this pod). This syntax is chosen only to have some well-defined way of
153
137
referencing a part of an object.
154
-
TODO: this design is not final and this field is subject to change in the future.
155
138
type: string
156
139
kind:
157
140
description: |-
@@ -432,7 +415,6 @@ spec:
432
415
the event) or if no container name is specified "spec.containers[2]" (container with
433
416
index 2 in this pod). This syntax is chosen only to have some well-defined way of
434
417
referencing a part of an object.
435
-
TODO: this design is not final and this field is subject to change in the future.
436
418
type: string
437
419
kind:
438
420
description: |-
@@ -468,24 +450,8 @@ spec:
468
450
description: The Linode Region the LinodeCluster lives in.
469
451
type: string
470
452
vpcRef:
471
-
description: |-
472
-
ObjectReference contains enough information to let you inspect or modify the referred object.
473
-
---
474
-
New uses of this type are discouraged because of difficulty describing its usage when embedded in APIs.
475
-
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.
476
-
2. Invalid usage help. It is impossible to add specific help for individual usage. In most embedded usages, there are particular
477
-
restrictions like, "must refer only to types A and B" or "UID not honored" or "name must be restricted".
478
-
Those cannot be well described when embedded.
479
-
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.
480
-
4. The fields are both imprecise and overly precise. Kind is not a precise mapping to a URL. This can produce ambiguity
481
-
during interpretation and require a REST mapping. In most cases, the dependency is on the group,resource tuple
482
-
and the version of the actual struct is irrelevant.
483
-
5. We cannot easily change it. Because this type is embedded in many locations, updates to this type
484
-
will affect numerous schemas. Don't make new APIs embed an underspecified API type they do not control.
485
-
486
-
487
-
Instead of using this type, create a locally provided and used type that is well-focused on your reference.
488
-
For example, ServiceReferences for admission registration: https://github.com/kubernetes/api/blob/release-1.17/admissionregistration/v1/types.go#L533 .
453
+
description: ObjectReference contains enough information to let you
454
+
inspect or modify the referred object.
489
455
properties:
490
456
apiVersion:
491
457
description: API version of the referent.
@@ -499,7 +465,6 @@ spec:
499
465
the event) or if no container name is specified "spec.containers[2]" (container with
500
466
index 2 in this pod). This syntax is chosen only to have some well-defined way of
501
467
referencing a part of an object.
502
-
TODO: this design is not final and this field is subject to change in the future.
ObjectReference contains enough information to let you inspect or modify the referred object.
119
-
---
120
-
New uses of this type are discouraged because of difficulty describing its usage when embedded in APIs.
121
-
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.
122
-
2. Invalid usage help. It is impossible to add specific help for individual usage. In most embedded usages, there are particular
123
-
restrictions like, "must refer only to types A and B" or "UID not honored" or "name must be restricted".
124
-
Those cannot be well described when embedded.
125
-
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.
126
-
4. The fields are both imprecise and overly precise. Kind is not a precise mapping to a URL. This can produce ambiguity
127
-
during interpretation and require a REST mapping. In most cases, the dependency is on the group,resource tuple
128
-
and the version of the actual struct is irrelevant.
129
-
5. We cannot easily change it. Because this type is embedded in many locations, updates to this type
130
-
will affect numerous schemas. Don't make new APIs embed an underspecified API type they do not control.
131
-
132
-
133
-
Instead of using this type, create a locally provided and used type that is well-focused on your reference.
134
-
For example, ServiceReferences for admission registration: https://github.com/kubernetes/api/blob/release-1.17/admissionregistration/v1/types.go#L533 .
117
+
description: ObjectReference contains enough information to
118
+
let you inspect or modify the referred object.
135
119
properties:
136
120
apiVersion:
137
121
description: API version of the referent.
@@ -145,7 +129,6 @@ spec:
145
129
the event) or if no container name is specified "spec.containers[2]" (container with
146
130
index 2 in this pod). This syntax is chosen only to have some well-defined way of
147
131
referencing a part of an object.
148
-
TODO: this design is not final and this field is subject to change in the future.
149
132
type: string
150
133
kind:
151
134
description: |-
@@ -360,7 +343,6 @@ spec:
360
343
the event) or if no container name is specified "spec.containers[2]" (container with
361
344
index 2 in this pod). This syntax is chosen only to have some well-defined way of
362
345
referencing a part of an object.
363
-
TODO: this design is not final and this field is subject to change in the future.
364
346
type: string
365
347
kind:
366
348
description: |-
@@ -396,24 +378,8 @@ spec:
396
378
description: The Linode Region the LinodeCluster lives in.
397
379
type: string
398
380
vpcRef:
399
-
description: |-
400
-
ObjectReference contains enough information to let you inspect or modify the referred object.
401
-
---
402
-
New uses of this type are discouraged because of difficulty describing its usage when embedded in APIs.
403
-
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.
404
-
2. Invalid usage help. It is impossible to add specific help for individual usage. In most embedded usages, there are particular
405
-
restrictions like, "must refer only to types A and B" or "UID not honored" or "name must be restricted".
406
-
Those cannot be well described when embedded.
407
-
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.
408
-
4. The fields are both imprecise and overly precise. Kind is not a precise mapping to a URL. This can produce ambiguity
409
-
during interpretation and require a REST mapping. In most cases, the dependency is on the group,resource tuple
410
-
and the version of the actual struct is irrelevant.
411
-
5. We cannot easily change it. Because this type is embedded in many locations, updates to this type
412
-
will affect numerous schemas. Don't make new APIs embed an underspecified API type they do not control.
413
-
414
-
415
-
Instead of using this type, create a locally provided and used type that is well-focused on your reference.
416
-
For example, ServiceReferences for admission registration: https://github.com/kubernetes/api/blob/release-1.17/admissionregistration/v1/types.go#L533 .
381
+
description: ObjectReference contains enough information to
382
+
let you inspect or modify the referred object.
417
383
properties:
418
384
apiVersion:
419
385
description: API version of the referent.
@@ -427,7 +393,6 @@ spec:
427
393
the event) or if no container name is specified "spec.containers[2]" (container with
428
394
index 2 in this pod). This syntax is chosen only to have some well-defined way of
429
395
referencing a part of an object.
430
-
TODO: this design is not final and this field is subject to change in the future.
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?v=4&size=40){kind=avatar}
0 commit comments