Infrastructure Update
An infrastructure update re-applies the underlying cloud configuration for a cluster you run in your own AWS account. It’s how Ownkube rolls out improvements to the AWS-level resources behind a Starter (K3s) or Production (EKS) cluster, such as networking, node configuration, or new capabilities a cluster’s infrastructure needs before a feature can work.
Infrastructure updates only apply to clusters running in your own cloud, not to Ownkube-managed compute, where there is no cluster for you to manage. If a pending infrastructure update is available for a cluster, its detail page surfaces it, and applying the update brings the cluster’s cloud resources in line with the latest configuration Ownkube ships. As one example, automated database backups on a Starter cluster need a recent infrastructure version; if backups aren’t available yet on an older Starter cluster, applying the pending infrastructure update is what unlocks them.
Infrastructure update and platform version are two separate upgrade axes. Infrastructure update is about the cloud resources underneath a cluster, the AWS-level configuration for compute, networking, and storage. Platform version is about the software Ownkube ships on top of that infrastructure, like a database engine version or deployment runtime. A cluster can need one, the other, or both, and each has its own upgrade control in the dashboard.