Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat/add node pool common #353

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions docs/releases/unreleased.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,15 +20,14 @@ The distribution is maintained with ❤️ by the team [SIGHUP](https://sighup.i

## New features 🌟

- TBD
- [[#353](https://github.com/sighupio/fury-distribution/pull/353)] **Add EKS self-managed node pool default override options for IDMS**: add a variable to override the default properies for EKS self-managed node pools. Currently support only the IDMS ones.

## Fixes 🐞

- [[#334](https://github.com/sighupio/fury-distribution/pull/334)] **Fix to policy module templates**: setting the policy module type to `gatekeeper` and the `additionalExcludedNamespaces` option for Kyverno at the same time resulted in an error do to an bug in the templates logic, this has been fixed.
- [[#336](https://github.com/sighupio/fury-distribution/pull/336)] **Fix race condition when deleting Kyverno**: changing the policy module type from `kyverno` to `none` could, sometimes, end up in a race condition where the API for ClusterPolicy CRD is unregistered before the deletion of the ClusterPolicy objects, resulting in an error in the deletion command execution. The deletion command has been tweaked to avoid this condition.
- [[#344](https://github.com/sighupio/fury-distribution/pull/344)] **Fix Cidr Block additional firewall rule in EKS Cluster**: remove the limitation to have a single CIDR Block additional firewall rule as the EKS installer supports a list.
- [[#348](https://github.com/sighupio/fury-distribution/pull/348)] **Fix `Get previous cluster configuration` failure on first apply**: fixed an issue on `furyctl apply` for on-premises clusters that made it fail with an `ansible-playbook create-playbook.yaml: command failed - exit status 2` error on the very first time it was executed.

## Upgrade procedure

Check the [upgrade docs](https://docs.kubernetesfury.com/docs/installation/upgrades) for the detailed procedure.
51 changes: 51 additions & 0 deletions docs/schemas/ekscluster-kfd-v1alpha2.md
Original file line number Diff line number Diff line change
Expand Up @@ -5024,6 +5024,7 @@ The network CIDR that will be used to assign IP addresses to the VPN clients whe
| [nodeAllowedSshPublicKey](#speckubernetesnodeallowedsshpublickey) | `object` | Required |
| [nodePoolGlobalAmiType](#speckubernetesnodepoolglobalamitype) | `string` | Required |
| [nodePools](#speckubernetesnodepools) | `array` | Required |
| [nodePoolsCommon](#speckubernetesnodepoolscommon) | `object` | Optional |
| [nodePoolsLaunchKind](#speckubernetesnodepoolslaunchkind) | `string` | Required |
| [serviceIpV4Cidr](#speckubernetesserviceipv4cidr) | `string` | Optional |
| [subnetIds](#speckubernetessubnetids) | `array` | Optional |
Expand Down Expand Up @@ -5775,6 +5776,56 @@ The type of Node Pool, can be `self-managed` for using customization like custom
|`"eks-managed"` |
|`"self-managed"`|

## .spec.kubernetes.nodePoolsCommon

### Properties

| Property | Type | Required |
|:-------------------------------------------------------------------------------------------------|:----------|:---------|
| [metadataHttpEndpoint](#speckubernetesnodepoolscommonmetadatahttpendpoint) | `string` | Optional |
| [metadataHttpPutResponseHopLimit](#speckubernetesnodepoolscommonmetadatahttpputresponsehoplimit) | `integer` | Optional |
| [metadataHttpTokens](#speckubernetesnodepoolscommonmetadatahttptokens) | `string` | Optional |

### Description

All the common self-managed node pool definitions. Currently supports only the IMDS properties.

## .spec.kubernetes.nodePoolsCommon.metadataHttpEndpoint

### Description

Specifies whether the instance metadata service (IMDS) is enabled or disabled. When set to 'disabled', instance metadata is not accessible.

### Constraints

**enum**: the value of this property must be equal to one of the following string values:

| Value |
|:-----------|
|`"enabled"` |
|`"disabled"`|

## .spec.kubernetes.nodePoolsCommon.metadataHttpPutResponseHopLimit

### Description

Specifies the maximum number of network hops allowed for instance metadata PUT response packets. This helps control access to instance metadata across different network layers.

## .spec.kubernetes.nodePoolsCommon.metadataHttpTokens

### Description

Defines whether the use of IMDS session tokens is required. When set to 'required', all metadata requests must include a valid session token.

### Constraints

**enum**: the value of this property must be equal to one of the following string values:

| Value |
|:-----------|
|`"optional"`|
|`"required"`|

## .spec.kubernetes.nodePoolsLaunchKind

### Description
Expand Down
Loading