Troubleshooting and support
What the statuses mean
Clusters, node groups, storages and databases share these statuses:
| Status | Meaning |
|---|---|
| Scheduled | Accepted and waiting to start, such as a cluster's first node group while the cluster itself is being built. |
| Creating | Being built in your cloud account. Click the badge (👁) to follow the progress log. |
| Running | Ready to use. |
| Upgrading (clusters) / Scaling (node groups) | A change is being applied. Click the badge to follow it. |
| Deleting | Being removed from your cloud account. |
| Error | The last operation failed. Nothing was marked as done that the cloud did not confirm. |
Pages with something in progress check for updates every 30 seconds and refresh by themselves. You can leave the page and come back.
Common messages
| Message | What it means | What to do |
|---|---|---|
| Credentials are not valid | The cloud provider rejected the credential's keys, for example because they were deleted or rotated. | Edit the credential and enter current keys. |
| This Cluster is Already being Modified / A cluster is Already being modified in your Teams | Another operation is running on the cluster. Only one runs at a time. | Wait for the current operation to finish, then try again. |
| You have reached your Billing Plan limit … | The team owner's plan allows no more teams, clusters, projects or virtual services. | Delete something unused, or change the plan. |
| You don't have an active Billing Plan | The team owner has no plan. | The owner picks a plan from Billing. |
| You're not authorized to perform this action / You don't have admin access to the Cluster Team … | Your role in the cluster's team does not allow it. | Ask a team Admin to change your role. See Teams and access. |
| Delete protection is enabled … | The cluster, storage or database is protected. | Edit it and turn delete protection off first. |
| Cannot Delete Cluster with Databases / Storage | The cluster still has data services. | Delete its databases and storages first. |
| This credential cannot be deleted since it is associated with a cluster | A cluster still uses the credential. | Delete the cluster first, or keep the credential. |
| This team has active clusters … | A team with clusters cannot be deleted. | Delete or move its clusters first. |
| DNS Check failed for Domain … | A custom domain with HTTPS does not point at the cluster yet. | See Virtual services. |
| Availability Zones String is invalid … | The zones are not a JSON list of zones in the chosen region. | Use the form ["ap-south-1a","ap-south-1b"], or leave the field empty. |
When something shows Error
- Cluster creation failed. Click the cluster's status badge to read the provisioning log; you also receive an email. Common causes are missing IAM permissions and cloud account limits, such as the number of VPCs or Elastic IPs in a region. Fix the cause, delete the failed cluster and create it again.
- Cluster deletion failed. The cluster stays listed with Error so nothing is left behind unnoticed. Choose Delete again to retry.
- Storage or database deletion failed. It stays listed with Error, often because the cloud resource was still in use. Wait a few minutes and delete it again.
- A workload will not start. Open the cluster and click Events (team Admins) for Kubernetes' own messages, such as image pull errors, failed health checks or no room on any node. For your application's logs and pipeline output, use CI/CD and Grafana from the cluster's Overview tab.
- The CI/CD dashboard is not responding. Open the cluster's Settings and run Restart. If its certificate has expired, run ReIssue-CICD-Certs.
Contact support
If you are stuck, contact us with your cluster ID (shown as #42 on the cluster card) and the exact message you saw:
- Support in the left rail opens our community channel.
- Email k8s@kstych.com.
Contact support before upgrading a busy production cluster. We can help you plan the upgrade.