change log for package release 08-19-2025 #10019
+175
−1
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,43 @@ | ||
| --- | ||
| title: "v9.47.0" | ||
| linkTitle: "v9.47.0" | ||
| weight: 30 | ||
| aliases: | ||
| /docs/reference/packagespec/cluster-autoscaler/v9.47.0/ | ||
| description: > | ||
| --- | ||
|
|
||
| ### Configuring Cluster Autoscaler in EKS Anywhere package spec | ||
|
|
||
| | Parameter | Description | Default | | ||
| |---|---|---| | ||
| |**General**||| | ||
| | cloudProvider | Cluster Autoscaler cloud provider. This should always be clusterapi. <br/>Example:<br/> <pre>cloudProvider: "clusterapi"</pre>| "clusterapi" | ||
| | autoDiscovery.clusterName | Name of the kubernetes cluster this autoscaler package should autoscale. <br/>Example:<br/> <pre>autoDiscovery.clusterName: "mgmt-cluster"</pre>| false | ||
| | clusterAPIMode | Where Cluster Autoscaler should look for a kubeconfig to communicate with the cluster it will manage. See https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/clusterapi/README.md#connecting-cluster-autoscaler-to-cluster-api-management-and-workload-clusters <br/>Example:<br/> <pre>clusterAPIMode: "incluster-kubeconfig"</pre>| "incluster-incluster" | ||
| | clusterAPICloudConfigPath | Path to kubeconfig for connecting to Cluster API Management Cluster, only used if `clusterAPIMode=kubeconfig-kubeconfig or incluster-kubeconfig` <br/>Example:<br/> <pre>clusterAPICloudConfigPath: "/etc/kubernetes/value"</pre>| "/etc/kubernetes/mgmt-kubeconfig" | ||
| | extraVolumeSecrets | Additional volumes to mount from Secrets. <br/>Example:<br/> <pre>extraVolumeSecrets: {}</pre>| {} | ||
| | extraArgs | Additional arguments to configure. See [upstream](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#what-are-the-parameters-to-ca)| None | | ||
|
|
||
| ### Example | ||
| ```yaml | ||
| apiVersion: packages.eks.amazonaws.com/v1alpha1 | ||
| kind: Package | ||
| metadata: | ||
| name: generated-cluster-autoscaler | ||
| namespace: eksa-packages-<cluster-name> | ||
| spec: | ||
| packageName: cluster-autoscaler | ||
| targetNamespace: default | ||
| config: |- | ||
| cloudProvider: "clusterapi" | ||
| autoDiscovery: | ||
| clusterName: "<cluster-name>" | ||
| extraArgs: | ||
| scale-down-delay-after-add: 2m | ||
| scale-down-delay-after-failure: 3m | ||
| scale-down-unneeded-time: 2m | ||
| ``` | ||
|
|
||
| --- | ||
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,102 @@ | ||
| --- | ||
| title: "v0.4.8" | ||
| linkTitle: "v0.4.8" | ||
| weight: 30 | ||
| aliases: | ||
| /docs/reference/packagespec/credential-provider-package/v0.4.8/ | ||
| description: > | ||
| --- | ||
|
|
||
| ### Configuring Credential Provider Package in EKS Anywhere package spec | ||
|
|
||
| #### Example | ||
|
|
||
| The following is the sample configuration for the credential provider package that is installed by default with the package controller. | ||
| Please refer to [Credential Provider Package with IAM Roles Anywhere.]({{< relref "iam_roles_anywhere" >}}) | ||
|
|
||
| If you are using proxy, please also set `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` under proxy configuration. | ||
|
|
||
| ```yaml | ||
| apiVersion: packages.eks.amazonaws.com/v1alpha1 | ||
| kind: Package | ||
| metadata: | ||
| name: ecr-credential-provider-package | ||
| namespace: eksa-packages-<clusterName> | ||
| annotations: | ||
| "helm.sh/resource-policy": keep | ||
| "anywhere.eks.aws.com/internal": "true" | ||
| spec: | ||
| packageName: credential-provider-package | ||
| targetNamespace: eksa-packages | ||
| config: |- | ||
| proxy: | ||
| HTTP_PROXY: "" | ||
| HTTPS_PROXY: "" | ||
| NO_PROXY: "" | ||
| tolerations: | ||
| - key: "node-role.kubernetes.io/master" | ||
| operator: "Exists" | ||
| effect: "NoSchedule" | ||
| - key: "node-role.kubernetes.io/control-plane" | ||
| operator: "Exists" | ||
| effect: "NoSchedule" | ||
| sourceRegistry: public.ecr.aws/eks-anywhere | ||
| credential: | ||
| - matchImages: | ||
| - 783794618700.dkr.ecr.us-west-2.amazonaws.com | ||
| profile: "default" | ||
| secretName: aws-secret | ||
| defaultCacheDuration: "5h" | ||
| ``` | ||
|
|
||
| In this example, the credential provider will use the secret provided in aws-secret (created automatically on cluster creation) to authenticate to the repository from which curated package images are pulled. Tolerations were also added so that the control plane nodes would also be configured with authentication. | ||
|
|
||
| The secret can exist in two forms: either a base64 encoding of a credential config or individual keys for fields. | ||
|
|
||
| Example credential | ||
| ``` | ||
| [default] | ||
| aws_access_key_id=EXAMPLE_ACCESS_KEY | ||
| aws_secret_access_key=EXAMPLE_SECRET_KEY | ||
| region=us-west-2 | ||
| ``` | ||
|
|
||
| ##### Example secret with separate keys | ||
| ``` | ||
| apiVersion: v1 | ||
| kind: Secret | ||
| metadata: | ||
| name: aws-secret | ||
| namespace: eksa-packages | ||
| data: | ||
| AWS_ACCESS_KEY_ID: "QUtJQUlPU0ZPRE5ON0VYQU1QTEUK" | ||
| AWS_SECRET_ACCESS_KEY: "d0phbHJYVXRuRkVNSS9LN01ERU5HL2JQeFJmaUNZRVhBTVBMRUtFWQo=" | ||
| REGION: dXMtd2VzdC0yCg== | ||
| ``` | ||
|
|
||
| ##### Example secret in config form | ||
| ``` | ||
| apiVersion: v1 | ||
| kind: Secret | ||
| metadata: | ||
| name: aws-secret | ||
| namespace: eksa-packages | ||
| data: | ||
| config: W2RlZmF1bHRdCmF3c19hY2Nlc3Nfa2V5X2lkPUFLSUFJT1NGT0ROTjdFWEFNUExFCmF3c19zZWNyZXRfYWNjZXNzX2tleT13SmFsclhVdG5GRU1JL0s3TURFTkcvYlB4UmZpQ1lFWEFNUExFS0VZCnJlZ2lvbj11cy13ZXN0LTI= | ||
| type: Opaque | ||
| ``` | ||
|
|
||
| #### Configurable parameters and default values under `spec.config` | ||
|
|
||
| | Parameter | Description | Default | | ||
| |----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------| | ||
| | **General** | | | | ||
| | image.pullPolicy | Specifies image pull policy: `IfNotPresent`, `Always`, `Never`. | `"IfNotPresent"` | | ||
| | tolerations | [Kubernetes tolerations](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/) for pod scheduling | `{}` | | ||
| | **Credential** | | | | ||
| | credential | List of credential providers for authenticating with ECR. Currently only one is supported | <pre>credential: <br/> - secretName: "aws-secret"<br/> matchImages: []<br/> defaultCacheDuration: "1h"<br/> profile: "default</pre> | | ||
| | secretName | Name of secret that contains the aws credentials | `"aws-secret"` | | ||
| | profile | AWS Profile for secretName | `"default"` | | ||
| | matchImages | List of strings used to match against images. See [here](https://kubernetes.io/docs/tasks/administer-cluster/kubelet-credential-provider/#configure-image-matching) for more info <br/>Example to match against any account across multiple regions for ECR:<br/></pre>`"*.dkr.ecr.*.amazonaws.com"`</pre> | `"[]"` | | ||
| | defaultCacheDuration | Duration the kubelet will cache credentials in-memory. For ECR it is recommended to keep this value less then 12 hours. | `"5h"` | | ||
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -5,6 +5,16 @@ weight: 7 | |
| description: > | ||
| Changelog for Curated packages release | ||
| --- | ||
| ## Package Bundle Release (08-19-2025) | ||
| #### Changed | ||
| - Upgrade helm version `0.17.2` to `0.18.0` | ||
|
||
| - Credential-Provider-Package `0.4.6` to `0.4.8` | ||
| - Enable proxy configuration [#1216](https://github.com/aws/eks-anywhere-packages/pull/1216) | ||
| - Cluster-Autoscaler `9.46.6` to `9.47.0` for Kubernetes version 1.33 | ||
| - Metallb | ||
| - Enable configuration for flag `ignoreExcludeLB` | ||
|
|
||
|
|
||
| ## Package Bundle Release (05-22-2025) | ||
|
|
||
| #### Changed | ||
|
|
||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.