Kubernetes Edge Limitations
This page lists the limitations of the Kubernetes edge in the current version. Review them before you install to understand what the Kubernetes edge can be used for and what your deployment needs to provide.
Deployment and operations
-
Air-gapped deployment is not supported. The Kubernetes edge needs outbound connectivity to the Ataccama control plane and to the required Azure services; no inbound connection is required. For the full list of required outbound connections, see Kubernetes Edge Network Access Requirements.
-
Moving a running edge between clouds or regions is not available, including migration from the edge on AWS, which runs on Amazon ECS on Fargate, to the Kubernetes edge.
-
There is no published sizing guidance for Kubernetes. We don’t recommend transferring the ECS sizing guidelines. If you need sizing advice now, contact Ataccama Support or your Customer Success Manager.
-
Configuration promotion between environments is not available. Each Kubernetes edge instance is configured separately; there is no supported workflow for promoting a development configuration to production.
-
The Kubernetes edge can’t be placed on a dedicated node pool from the chart. The chart has no pod-scheduling values, such as node selectors, tolerations, or affinity. Isolation is at the namespace level, so if edge pods share nodes with your other workloads, a container escape can reach those workloads.
Feature availability
The following connectors and features are not available on the Kubernetes edge:
-
Generic Connector connections, which use your own JDBC driver.
-
Power BI, Salesforce, and Teradata connections.
-
Secret management service with AWS Secrets Manager.
Was this page useful?