Catalyst Cloud incident

CCKS cluster creation not completing

Minor Resolved View vendor source →

Catalyst Cloud experienced a minor incident on January 29, 2026 affecting Kubernetes (nz-hlz-1) and Kubernetes (nz-por-1), lasting 3d 23h. The incident has been resolved; the full update timeline is below.

Started
Jan 29, 2026, 01:06 AM UTC
Resolved
Feb 02, 2026, 12:11 AM UTC
Duration
3d 23h
Detected by Pingoru
Jan 29, 2026, 01:06 AM UTC

Affected components

Kubernetes (nz-hlz-1)Kubernetes (nz-por-1)

Update timeline

  1. investigating Jan 29, 2026, 01:06 AM UTC

    We are aware of an issue that is affecting newly created CCKS clusters completing their creation phase. This issue may be worked around by providing the label `kube_dashboard_enabled=false` on creation. For more details on labels see https://docs.catalystcloud.nz/kubernetes/appendix.html#k8s-cluster-labels We are working on a resolution to this and will update this statuspage message when the problem is resolved. This issue is not expected to impact running clusters.

  2. identified Jan 29, 2026, 01:06 AM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Jan 29, 2026, 03:31 AM UTC

    A fix has been tested and we expect to deploy this for customers on Friday 2026-01-30. Until then, providing label `kube_dashboard_enabled=false` during cluster creation continues to be the recommended workaround.

  4. identified Jan 29, 2026, 08:40 PM UTC

    Fix has been rescheduled for Monday 2026-02-02.

  5. resolved Feb 02, 2026, 12:11 AM UTC

    This issue has been resolved.