Skip to content

v2.8.7-tf.1
Compare
Choose a tag to compare
@KashifSaadat KashifSaadat released this 12 Sep 12:17
· 19 commits to main since this release
v2.8.7-tf.1
f3cda98

Release v2.8.7-tf.1

Upgradeable Versions: v2.7.4-tf.2
Full Wayfinder Changelog: https://docs.appvia.io/wayfinder/releases

Major New Features in v2.8

Cluster Plan Versioning

In this release, Wayfinder now supports immutable versioning of Cluster Plans, allowing you to roll out changes to cluster plans across your fleet in a testable and deterministic way.

Clusters now refer to a plan and version and Wayfinder uses the details of the plan directly to build and manage the cluster. Creating a new plan version gives you a testable upgrade path for each plan, meaning you can use the exact same upgrade across all clusters on that plan, reducing bespoke per-cluster testing needs.

This release also introduces Compute Templates, which contain suggested node pool configurations that application teams can select from when self-serving clusters.

Provisioning Policies

Along with versioned cluster plans, this release introduces a new Provisioning Policy resource allowing you to restrict self-service of clusters, replacing the 'policy' construct on older cluster plans.

Limits can be configured for the maximum estimated costs for a cluster, along with what regions, instance types, number of nodes and the number of clusters can be provisioned.

A UI to manage provisioning policies will be available in a future release.

Changelog

Wayfinder changes:

Terraform Infrastructure changes:

  • Updated EKS management cluster to v1.30 and related EKS addons
  • Switched to a supported version of the kubectl provider for Terraform

Required Actions

With the introduction of versioned Cluster Plans and Packages, the following manual updates should be made within your Wayfinder instance and manifest repositories:

  1. Authenticate with AWS (with permissions to modify the Terraform remote state) and run terraform state replace-provider gavinbunney/kubectl alekc/kubectl prior to upgrading to this version.
  2. Next steps to be performed post-upgrade:
    1. Copy any default Packages you require from the wayfinder-defaults repository into your own Wayfinder Platform configuration repository. This is no longer shipped or applied by default on Wayfinder upgrades, to prevent overwriting user customisations.
    2. Update any of your own custom Packages to the new versioned Package spec. Examples available in the wayfinder-defaults repository.
    3. Update any of your own custom ClusterPlans to the new versioned ClusterPlan spec. Examples available in the wayfinder-defaults repository.
    4. Update existing Clusters (ClusterSpec objects) to point at the new ClusterPlan version you have created (see Cluster YAML spec.planRef)
Assets 2
Loading