@@ -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
@@ -858,24 +841,18 @@ spec:
858
841
gp2 volumes, this represents the baseline performance of the volume and the
859
842
rate at which the volume accumulates I/O credits for bursting.
860
843
861
-
862
844
The following are the supported values for each volume type:
863
845
864
-
865
846
* gp3: 3,000-16,000 IOPS
866
847
867
-
868
848
* io1: 100-64,000 IOPS
869
849
870
-
871
850
* io2: 100-64,000 IOPS
872
851
873
-
874
852
For io1 and io2 volumes, we guarantee 64,000 IOPS only for Instances built
875
853
on the Nitro System (https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-types.html#ec2-nitro-instances).
876
854
Other instance families guarantee performance up to 32,000 IOPS.
877
855
878
-
879
856
This parameter is supported for io1, io2, and gp3 volumes only. This parameter
880
857
is not supported for gp2, st1, sc1, or standard volumes.
881
858
format : int64
@@ -904,16 +881,12 @@ spec:
904
881
a volume size. The following are the supported volumes sizes for each volume
905
882
type:
906
883
907
-
908
884
* gp2 and gp3: 1-16,384
909
885
910
-
911
886
* io1 and io2: 4-16,384
912
887
913
-
914
888
* st1 and sc1: 125-16,384
915
889
916
-
917
890
* standard: 1-1,024
918
891
x-kubernetes-int-or-string : true
919
892
volumeType :
@@ -939,6 +912,9 @@ spec:
939
912
RootVolume is a flag indicating if this device is mounted as kubelet root dir. You can
940
913
configure at most one root volume in BlockDeviceMappings.
941
914
type : boolean
915
+ required :
916
+ - deviceName
917
+ - ebs
942
918
type : object
943
919
maxItems : 50
944
920
type : array
@@ -977,14 +953,12 @@ spec:
977
953
description : |-
978
954
MetadataOptions for the generated launch template of provisioned nodes.
979
955
980
-
981
956
This specifies the exposure of the Instance Metadata Service to
982
957
provisioned EC2 nodes. For more information,
983
958
see Instance Metadata and User Data
984
959
(https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html)
985
960
in the Amazon Elastic Compute Cloud User Guide.
986
961
987
-
988
962
Refer to recommended, security best practices
989
963
(https://aws.github.io/aws-eks-best-practices/security/docs/iam/#restrict-access-to-the-instance-profile-assigned-to-the-worker-node)
990
964
for limiting exposure of Instance Metadata and User Data to pods.
@@ -999,7 +973,6 @@ spec:
999
973
nodes. If metadata options is non-nil, but this parameter is not specified,
1000
974
the default state is "enabled".
1001
975
1002
-
1003
976
If you specify a value of "disabled", instance metadata will not be accessible
1004
977
on the node.
1005
978
enum :
@@ -1035,14 +1008,12 @@ spec:
1035
1008
requests. If metadata options is non-nil, but this parameter is not
1036
1009
specified, the default state is "required".
1037
1010
1038
-
1039
1011
If the state is optional, one can choose to retrieve instance metadata with
1040
1012
or without a signed token header on the request. If one retrieves the IAM
1041
1013
role credentials without a token, the version 1.0 role credentials are
1042
1014
returned. If one retrieves the IAM role credentials using a valid signed
1043
1015
token, the version 2.0 role credentials are returned.
1044
1016
1045
-
1046
1017
If the state is "required", one must send a signed token header with any
1047
1018
instance metadata retrieval requests. In this state, retrieving the IAM
1048
1019
role credentials always returns the version 2.0 credentials; the version
0 commit comments