ScyllaDB University Live | Free Virtual Training Event
Learn more
ScyllaDB Documentation Logo Documentation
  • Server
    • ScyllaDB Open Source
    • ScyllaDB Enterprise
    • ScyllaDB Alternator
  • Cloud
  • Tools
    • ScyllaDB Manager
    • ScyllaDB Monitoring Stack
    • ScyllaDB Operator
  • Drivers
    • CQL Drivers
    • DynamoDB Drivers
Download
Menu

Caution

You're viewing documentation for an unstable version of Scylla Operator. Switch to the latest stable version.

ScyllaDB Docs Scylla Operator Support Troubleshooting Troubleshooting installation issues

Troubleshooting installation issues¶

Webhooks¶

Scylla Operator provides several custom API resources that use webhooks to function properly.

Unfortunately, it is often the case that user’s clusters have modified SDN, that doesn’t extend to the control plane, and Kubernetes apiserver is not able to reach the pods that serve the webhook traffic. Another common case are firewall rules that block the webhook traffic.

Note

To be called a Kubernetes cluster, clusters are required to pass Kubernetes conformance test suite. This suite includes tests that require Kubernetes apiserver to be able to reach webhook services.

Note

Before filing an issue, please make sure your cluster webhook traffic can reach your webhook services, independently of Scylla Operator resources.

EKS¶

Custom CNI¶

EKS is currently breaking Kubernetes webhooks when used with custom CNI networking.

Note

We advise you to avoid using such setups and use a conformant Kubernetes cluster that supports webhooks.

There are some workarounds where you can reconfigure the webhook to use Ingress or hostNetwork instead, but it’s beyond a standard configuration that we support and not specific to the Scylla Operator.

GKE¶

Private clusters¶

If you use GKE private clusters you need to manually configure the firewall to allow webhook traffic. You can find more information on how to do that in GKE private clusters docs.

Was this page helpful?

PREVIOUS
Troubleshooting
NEXT
Gathering data with must-gather
Scylla Operator
  • master
    • v1.11
    • v1.10
    • v1.9
    • master
  • Deploying Scylla on a Kubernetes Cluster
  • Deploying Scylla on EKS
  • Deploying Scylla on GKE
  • Deploying Scylla stack using Helm Charts
  • Results
  • Monitoring
  • Cleanup
  • Deploying Scylla Manager on a Kubernetes Cluster
  • Monitoring
  • Version migrations
  • Node operations using Scylla Operator
    • Upgrading version of Scylla
    • Replacing a Scylla node
    • Automatic cleanup and replacement in case when k8s node is lost
    • Maintenance mode
    • Restore from backup
  • Exposing ScyllaCluster
  • Deploying multi-datacenter ScyllaDB clusters in Kubernetes
    • Build multiple Amazon EKS clusters with inter-Kubernetes networking
    • Build multiple GKE clusters with inter-Kubernetes networking
    • Deploy a multi-datacenter ScyllaDB cluster in multiple interconnected Kubernetes clusters
  • Performance tuning
  • Upgrade of Scylla Operator
  • Releases
  • Support
    • Support overview
    • Known issues
    • Troubleshooting
      • Troubleshooting installation issues
    • Gathering data with must-gather
  • Scylla Cluster CRD
  • Contributing to Scylla Operator
  • Create an issue
  • Edit this page

On this page

  • Troubleshooting installation issues
    • Webhooks
      • EKS
        • Custom CNI
      • GKE
        • Private clusters
Logo
Docs University Contact Us About Us
Mail List Icon Slack Icon Forum Icon
© 2023, ScyllaDB. All rights reserved.
Last updated on 29 November 2023.
Powered by Sphinx 7.2.6 & ScyllaDB Theme 1.6.1