v0.27.2-rc.3

Changelog

• 11d445a chore: update go.mod go.sum
• ffe9ec7 fix: added new fields
• 28d6075 fix: removed error when upgrading with reducer

v0.27.2-rc.2

Changelog

• e459e6f chore: go mod tidy
• d1d6873 chore: update README file
• 7f12590 feat: added new kfd 1.27.2 e2e tests
• f7d39e0 feat: added safe rules (#466)
• 8edcce6 feat: added upgrade paths to 1.27.2
• 8e20df6 fix: added support to any type

v0.27.2-rc.1

Changelog

• de6a218 chore: added tests
• e567fd7 feat: added safe rules
• d42ae88 feat: changed from and to in safe rules to optional
• 8e20df6 fix: added support to any type

v0.27.2-rc.0

Changelog

• 9a8e905 fix: added support to any type

v0.27.1

This release is a bufgix realase, details below:

Changelog

• a7a152f feat: add warning message if storageClass is not available also for tracing module
• e649529 hotfix: fix velero patches when using EKS provider on all the latest KFD versions: v1.25.9,v1.26.4,v1.27.0,v1.27.1

v0.27.0

Main changes

cluster upgrade

With this release, we introduced the ability to run cluster upgrades with furyctl. The command is furyctl apply --upgrade and it will upgrade the cluster from the currently applied version to the one specified in the furyctl.yaml file.
Check out the docs for more details about the supported upgrade paths.

workload migrations

We introduced the support for running automated migrations, enabling users to move from one workload to another when applying the furyctl.yaml file.

diff state

We introduced the ability for furyctl to diff the wanted furyctl.yaml with the one that is currently applied in the cluster.
The functionality is also available as a standalone command furyctl diff.

ephemeral local files

Furyctl is now able to be fully-independent from the local files stored in the ~/.furyctl directory. This means that the furyctl apply command is now fully portable, with no local state attached.

improved fury-distribution support

We introduced a new compatibility layer that makes furyctl compatible with all the supported versions of the fury-distribution. This means that you can now use the latest version of furyctl with older versions of the fury-distribution(v1.25+)

## A host of bugfixes and improvements

• added --start-from cli option to furyctl apply command, to allow users to start applying from a specific, more granular point in the lifecycle of the run.
• improved error handling and error messages
• introduced --force flag to furyctl apply command, to allow users to skip some error conditions during the execution.
• added --upgrade-path-location cli option to allow for custom upgrade paths to be specified.

Full Changelog: v0.26.3...v0.27.0

v0.27.0-rc.3

Full Changelog: v0.27.0-rc.2...v0.27.0-rc.3

v0.27.0-rc.2

Full Changelog: v0.27.0-rc.1...v0.27.0-rc.2

v0.27.0-rc.1

Full Changelog: v0.26.3...v0.27.0-rc.1

v0.26.3

Important Changes

• feat: introduce support to max pods in node pools instances
• fix: perform dns query check during eks creation only if vpn is set and cluster is private

Changelog

• dc4896d chore: fix linting issues
• 6a80b9d chore: tidy up go modules
• 7a3b4fe chore: update fury refs in doc
• b4c8113 chore: update fury-distribution dependency
• fa15c79 chore: update fury-distribution dependency
• ff9607a chore: update fury-distribution dependency
• b7a3f9e chore: update goreleaser to v1.22.1
• cefcb9f feat: add plugins docs (#436)
• 2d46783 feat: bump golang image to 1.21.4.
• 0c7c42d feat: introduce support to max pods in node pools instances.
• 3ed21c3 fix: perform dns query check during eks creation only if vpn is set and cluster is private
• 9e8efc1 chore: update distribution dep to v1.26.3
• 8998158 fix: add guard against null attribute access
• eb3f207 fix: maxPods value rendering in generated tfvars