# Panfactum Changelog — edge.24-09-30

> Adds self-hosted GitHub Action runners addon and EKS cluster suspend/resume commands, while fixing voluntary disruption window namespace limitations.

## Highlights

- New [GitHub Action runners addon](https://panfactum.com/docs/edge/guides/addons/github-actions/installing) for self-hosted CI
- New `pf-eks-suspend` and `pf-eks-resume` commands for cluster lifecycle management
- Fixed disruption windows to work in all namespaces (previously only worked in `argo`)

## Additions

- Adds a [new addon for self-hosted GitHub Action runners.](https://panfactum.com/docs/edge/guides/addons/github-actions/installing)
  - Impacts: iac-module `kube_gha` — New module for self-hosted GitHub Action runner infrastructure
  - Impacts: iac-module `kube_gha_runners` — New module for configuring GitHub Action runner workloads
- Adds the `pf-eks-suspend` and `pf-eks-resume` commands to [suspend and resume the EKS cluster](https://panfactum.com/docs/main/guides/bootstrapping/suspend-kubernetes-cluster).
  - Impacts: cli `kube cluster-suspend` — New command to suspend an EKS cluster
  - Impacts: cli `kube cluster-resume` — New command to resume a suspended EKS cluster

## Fixes

- Fixes an issue where voluntary disruption windows created by [`kube_disruption_window_controller`](https://panfactum.com/docs/edge/reference/infrastructure-modules/submodule/kubernetes/kube_disruption_window_controller) would only work for the `argo` namespace. They will now
  - Impacts: iac-module `kube_disruption_window_controller` — Fixed disruption windows to apply across all namespaces
  - Reference (issue-report): [Disruption windows only working in argo namespace](https://github.com/Panfactum/stack/issues/137)

## Related Resources

- [JSON Data](https://panfactum.com/docs/changelog/edge.24-09-30.json): Machine-readable data
- [Channel Release List](https://panfactum.com/docs/changelog/edge.json): All releases in this channel