Managed Add-ons
Managed Add-ons extend a Managed Kubernetes cluster with NetActuate-operated capabilities that you turn on from the portal instead of installing and maintaining yourself. Once enabled, NetActuate installs the add-on into your cluster, keeps it running, and reconciles it, so you get storage, DNS, and load balancing that are integrated with the platform without hand-managing controllers or CRDs. Manage them from the Managed Add-ons tab of your cluster in the portal.
What Managed Add-ons are
Each add-on is a controller or driver that NetActuate installs and owns inside your cluster. You request an add-on and provide any inputs it needs; NetActuate handles the installation, upgrades, and health. Because the platform owns the add-on, you should not hand-edit the resources it manages: change configuration through the portal, and use the resource's own Kubernetes API (a StorageClass, a Service annotation, an Ingress) as documented on each add-on page.
The available add-ons are:
- Storage - dynamic block volumes backed by NetActuate Ceph, via a managed StorageClass
- DNS - automatic DNS records for Services and Ingresses in a zone you own
- Load Balancing - Layer 4 and Layer 7 load balancing through the VPC gateway (in-VPC clusters only)
Add-on lifecycle
An add-on moves through a small set of states, surfaced on the Managed Add-ons tab:
- requested - you have enabled the add-on and NetActuate has accepted the request.
- installing - the controller or driver and its resources are being applied to the cluster.
- ready - the add-on is installed and healthy, and you can use it.
- degraded - the add-on is installed but not fully healthy; it may be partially working while it recovers.
- failed - installation or reconciliation could not complete.
When an add-on is degraded or failed, the tab shows a Repair action that re-runs installation and reconciliation to bring it back to ready. Repair is safe to run more than once; it converges the add-on toward its intended state rather than recreating your data or configuration.
Availability
Add-on availability depends on the cluster type. Storage works on any cluster. DNS works on both edge and in-VPC clusters. Load Balancing depends on the VPC gateway and is available only on in-VPC clusters.
| Add-on | Edge cluster | In-VPC cluster |
|---|---|---|
| Storage | Available | Available |
| DNS | Available | Available |
| Load Balancing | Not available | Available |
See Kubernetes in a VPC for the difference between edge and in-VPC clusters.
Need Help?
Contact support@netactuate.com or open a support ticket from the portal.