@@ -3,7 +3,7 @@ apiVersion: apiextensions.k8s.io/v1
3
3
kind : CustomResourceDefinition
4
4
metadata :
5
5
annotations :
6
- controller-gen.kubebuilder.io/version : v0.15.0
6
+ controller-gen.kubebuilder.io/version : v0.16.3
7
7
name : ec2nodeclasses.karpenter.k8s.aws
8
8
spec :
9
9
group : karpenter.k8s.aws
@@ -162,24 +162,18 @@ spec:
162
162
gp2 volumes, this represents the baseline performance of the volume and the
163
163
rate at which the volume accumulates I/O credits for bursting.
164
164
165
-
166
165
The following are the supported values for each volume type:
167
166
168
-
169
167
* gp3: 3,000-16,000 IOPS
170
168
171
-
172
169
* io1: 100-64,000 IOPS
173
170
174
-
175
171
* io2: 100-64,000 IOPS
176
172
177
-
178
173
For io1 and io2 volumes, we guarantee 64,000 IOPS only for Instances built
179
174
on the Nitro System (https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-types.html#ec2-nitro-instances).
180
175
Other instance families guarantee performance up to 32,000 IOPS.
181
176
182
-
183
177
This parameter is supported for io1, io2, and gp3 volumes only. This parameter
184
178
is not supported for gp2, st1, sc1, or standard volumes.
185
179
format : int64
@@ -202,16 +196,12 @@ spec:
202
196
a volume size. The following are the supported volumes sizes for each volume
203
197
type:
204
198
205
-
206
199
* gp2 and gp3: 1-16,384
207
200
208
-
209
201
* io1 and io2: 4-16,384
210
202
211
-
212
203
* st1 and sc1: 125-16,384
213
204
214
-
215
205
* standard: 1-1,024
216
206
pattern : ^((?:[1-9][0-9]{0,3}|[1-4][0-9]{4}|[5][0-8][0-9]{3}|59000)Gi|(?:[1-9][0-9]{0,3}|[1-5][0-9]{4}|[6][0-3][0-9]{3}|64000)G|([1-9]||[1-5][0-7]|58)Ti|([1-9]||[1-5][0-9]|6[0-3]|64)T)$
217
207
type : string
@@ -238,6 +228,9 @@ spec:
238
228
RootVolume is a flag indicating if this device is mounted as kubelet root dir. You can
239
229
configure at most one root volume in BlockDeviceMappings.
240
230
type : boolean
231
+ required :
232
+ - deviceName
233
+ - ebs
241
234
type : object
242
235
maxItems : 50
243
236
type : array
@@ -390,14 +383,12 @@ spec:
390
383
description : |-
391
384
MetadataOptions for the generated launch template of provisioned nodes.
392
385
393
-
394
386
This specifies the exposure of the Instance Metadata Service to
395
387
provisioned EC2 nodes. For more information,
396
388
see Instance Metadata and User Data
397
389
(https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html)
398
390
in the Amazon Elastic Compute Cloud User Guide.
399
391
400
-
401
392
Refer to recommended, security best practices
402
393
(https://aws.github.io/aws-eks-best-practices/security/docs/iam/#restrict-access-to-the-instance-profile-assigned-to-the-worker-node)
403
394
for limiting exposure of Instance Metadata and User Data to pods.
@@ -412,7 +403,6 @@ spec:
412
403
nodes. If metadata options is non-nil, but this parameter is not specified,
413
404
the default state is "enabled".
414
405
415
-
416
406
If you specify a value of "disabled", instance metadata will not be accessible
417
407
on the node.
418
408
enum :
@@ -448,14 +438,12 @@ spec:
448
438
requests. If metadata options is non-nil, but this parameter is not
449
439
specified, the default state is "required".
450
440
451
-
452
441
If the state is optional, one can choose to retrieve instance metadata with
453
442
or without a signed token header on the request. If one retrieves the IAM
454
443
role credentials without a token, the version 1.0 role credentials are
455
444
returned. If one retrieves the IAM role credentials using a valid signed
456
445
token, the version 2.0 role credentials are returned.
457
446
458
-
459
447
If the state is "required", one must send a signed token header with any
460
448
instance metadata retrieval requests. In this state, retrieving the IAM
461
449
role credentials always returns the version 2.0 credentials; the version
@@ -691,12 +679,7 @@ spec:
691
679
- Unknown
692
680
type : string
693
681
type :
694
- description : |-
695
- type of condition in CamelCase or in foo.example.com/CamelCase.
696
- ---
697
- Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be
698
- useful (see .node.status.conditions), the ability to deconflict is important.
699
- The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt)
682
+ description : type of condition in CamelCase or in foo.example.com/CamelCase.
700
683
maxLength : 316
701
684
pattern : ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$
702
685
type : string
@@ -862,24 +845,18 @@ spec:
862
845
gp2 volumes, this represents the baseline performance of the volume and the
863
846
rate at which the volume accumulates I/O credits for bursting.
864
847
865
-
866
848
The following are the supported values for each volume type:
867
849
868
-
869
850
* gp3: 3,000-16,000 IOPS
870
851
871
-
872
852
* io1: 100-64,000 IOPS
873
853
874
-
875
854
* io2: 100-64,000 IOPS
876
855
877
-
878
856
For io1 and io2 volumes, we guarantee 64,000 IOPS only for Instances built
879
857
on the Nitro System (https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-types.html#ec2-nitro-instances).
880
858
Other instance families guarantee performance up to 32,000 IOPS.
881
859
882
-
883
860
This parameter is supported for io1, io2, and gp3 volumes only. This parameter
884
861
is not supported for gp2, st1, sc1, or standard volumes.
885
862
format : int64
@@ -908,16 +885,12 @@ spec:
908
885
a volume size. The following are the supported volumes sizes for each volume
909
886
type:
910
887
911
-
912
888
* gp2 and gp3: 1-16,384
913
889
914
-
915
890
* io1 and io2: 4-16,384
916
891
917
-
918
892
* st1 and sc1: 125-16,384
919
893
920
-
921
894
* standard: 1-1,024
922
895
x-kubernetes-int-or-string : true
923
896
volumeType :
@@ -943,6 +916,9 @@ spec:
943
916
RootVolume is a flag indicating if this device is mounted as kubelet root dir. You can
944
917
configure at most one root volume in BlockDeviceMappings.
945
918
type : boolean
919
+ required :
920
+ - deviceName
921
+ - ebs
946
922
type : object
947
923
maxItems : 50
948
924
type : array
@@ -981,14 +957,12 @@ spec:
981
957
description : |-
982
958
MetadataOptions for the generated launch template of provisioned nodes.
983
959
984
-
985
960
This specifies the exposure of the Instance Metadata Service to
986
961
provisioned EC2 nodes. For more information,
987
962
see Instance Metadata and User Data
988
963
(https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html)
989
964
in the Amazon Elastic Compute Cloud User Guide.
990
965
991
-
992
966
Refer to recommended, security best practices
993
967
(https://aws.github.io/aws-eks-best-practices/security/docs/iam/#restrict-access-to-the-instance-profile-assigned-to-the-worker-node)
994
968
for limiting exposure of Instance Metadata and User Data to pods.
@@ -1003,7 +977,6 @@ spec:
1003
977
nodes. If metadata options is non-nil, but this parameter is not specified,
1004
978
the default state is "enabled".
1005
979
1006
-
1007
980
If you specify a value of "disabled", instance metadata will not be accessible
1008
981
on the node.
1009
982
enum :
@@ -1039,14 +1012,12 @@ spec:
1039
1012
requests. If metadata options is non-nil, but this parameter is not
1040
1013
specified, the default state is "required".
1041
1014
1042
-
1043
1015
If the state is optional, one can choose to retrieve instance metadata with
1044
1016
or without a signed token header on the request. If one retrieves the IAM
1045
1017
role credentials without a token, the version 1.0 role credentials are
1046
1018
returned. If one retrieves the IAM role credentials using a valid signed
1047
1019
token, the version 2.0 role credentials are returned.
1048
1020
1049
-
1050
1021
If the state is "required", one must send a signed token header with any
1051
1022
instance metadata retrieval requests. In this state, retrieving the IAM
1052
1023
role credentials always returns the version 2.0 credentials; the version
0 commit comments