Feature Ideas

I want to be able to pause (scale to 0) environments when they are not in use, to save on hosting costs. I may do this manually, or on a schedule (e.g. scale down certain non-production environments out of hours) I want to be able to do this for an App (on a particular environment) I want to be able to do this on a Cluster I want to see potential cost savings by scaling down an App or Cluster

Be able to deploy developer packages and expose them as normal applications would be exposed, so they can be consumed easily by developers. These services would be things like kube-costs or an ELK stack etc.

Be able to validate cloud modules before they are imported into Wayfinder, so that there are known working modules available for self-service

Be able to bring your own tags to Wayfinder, so that resources can be tagged inline with organisations tagging best practices.

Have Wayfinder secrets managed by an integrated secret store such as Cloud providers key-vaults or hashicorp vault.

Be able to see the license usage inside of Wayfinder as well as the license type purchased, expiration date and other useful information.

Make the cloud resource plans into a new spec, so that it is easier to define developer inputs and also use system information that wayfinder holds. This means you can feed in dynamic information from other resources such as subnets, vpc, route tables etc. Into the terraform modules as templated variables. When developers then self-serve, these will be universal and looked up and dynamically assigned based on the infrastructure that exists for that team and the environment the application cloud resource is being deployed to

I want to be able to provide an override for custom DNS servers when using a cloud landing zone. This means passing these as part of the networkplan in Wayfinder or enabling the usage of the rules ID for a shared resource in AWS.

Move Terranetes into the management cluster and management API of Wayfinder

EKS Pod identity is the direction AWS are going in for kubernetes workloads that need cloud API access. We need to migrate over to this once it is supported across all regions and GA.

Currently, the cluster plans have authorised networks associated with the Kubernetes cluster to allow specific networks through. We should move this to a more global configuration setting that can be used as a variable and be overridden at infrastructure deployment time.

Provide platform engineers with a way of having additional tests and healthchecks to a package. This gives engineers faster feedback and constant assurances that the package will work as expected.

Integrate into the Cloud managed secret solutions so that we have a first-class integration into the Cloud for Wayfinder for secret management.

be able to override helm packages with health checks that upstream packages can sometimes lack. This is to be able to validate that the package is healthy when iterating but also when it is running.

Be able to destroy clusters automatically when they are no longer in use so that costs can stay low.