The Aerospike Knowledge Base has moved to https://support.aerospike.com. Content on https://discuss.aerospike.com is being migrated to either https://support.aerospike.com or https://docs.aerospike.com. Maintenance on articles stored in this repository ceased on December 31st 2022 and this article may be stale. If you have any questions, please do not hesitate to raise a case via https://support.aerospike.com.
FAQ - Kubernetes Related Errors
Error messages similar to the following may be encountered while setting up various Aerospike components using Kubernetes. Specific device names, interface names, etc may vary between installations. This list will be updated over time as more errors are encountered.
In the Aerospike log file
-
failed to resolve mounted device /dev/dsk1: 2 (No such file or directory)
- parent device not visible inside container - see specific KB article for details and remediation
-
Too many addresses for interface kube-ipvs0
- using IPVS for kube-proxy with hostNetwork- see this specific KB article for details and remediation
In kubectl output
-
error: unable to recognize “aerospike-cluster.yaml”: no matches for kind “AerospikeCluster” in version “aerospike.com/v1alpha1”
- CRDs were not registered before deploying the operator
- apply aerospike.com_aerospikeclusters_crd.yaml and then deploy the operator again
Notes
Carefully following the instructions for deploying Aerospike via the Operator will avoid many of these errors.
Keywords
KUBERNETES ERROR HOST NETWORKING
Timestamp
July 2021