Was this page helpful?
Known issues¶
This page lists known issues, platform-specific caveats, and feature limitations in ScyllaDB Operator. For issues specific to Kubernetes environments, see Supported Kubernetes environments.
Platform-specific issues¶
TRUNCATE queries fail when hairpinning is disabled¶
TRUNCATE queries require hairpinning to be enabled on the container network bridge. On some environments this is disabled by default.
Learn more: #163
Workaround:
ip link set <bridge-interface> promisc on
ScyllaDB Manager fails to boot when hairpinning is disabled¶
If ScyllaDB Manager fails to apply the 8th migration (008_*), the cause is the same hairpinning issue. Apply the workaround above.
EKS: webhook connectivity with custom CNI¶
On EKS clusters using a custom CNI plugin, webhook connectivity can break because the API server may be unable to reach webhook pods. This is an upstream issue.
Reference: aws/containers-roadmap#1215
GKE: private clusters require a firewall rule¶
GKE private clusters restrict communication from the API server to node pods. A firewall rule must be added to allow the API server to reach the webhook pod on the serving port.
Reference: GKE private clusters — add firewall rules