ref Issue: https://github.com/datastax/cass-operator/issues/390
Why it is not supported?
ref Issue: https://github.com/datastax/cass-operator/issues/390
Why it is not supported?
Jim Dickinson already answered this question in issue #390 you referenced so I'm going to re-post his answer here.
Attempts to change StorageConfig
is blocked because the StatefulSet
also doesn't allow changes to the PersistentVolumeClaim
.
If a pod has run out of disk space, it is possible to workaround it by resizing the underlying volume provided it is supported in your environment. For example, public cloud providers allow volumes to be resized in certain configurations. You will need to consult the documentation of the relevant cloud provider for details.
Be aware that this workaround can be risky since it means that the underlying volume will be out of sync with the CassandraDatacenter, StatefulSet and/or PersistentVolumeClaim definitions. When you scale up the DC at a later date, the volume will be the originally defined size. Cheers!
6 People are following this question.
How do we expose metrics in Cassandra using the cass-operator?
How do I start processes as cassandra user instead of root with the cass-operator securityContext?
Why does the C++ driver connect to an IP not in the Kubernetes cluster?
Is it possible to set annotations to images deployed with the cass-operator?
DataStax Enterprise is powered by the best distribution of Apache Cassandra ™
© 2023 DataStax, Titan, and TitanDB are registered trademarks of DataStax, Inc. and its subsidiaries in the United States and/or other countries.
Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries.
Privacy Policy Terms of Use