update: remove cassndra docs due to EOL (#1327)

Author: wojcik-dorota

.github/workflow-config/labeling-rules.yaml

@@ -9,10 +9,6 @@ service/alloydbomni:
   - changed-files:
       - any-glob-to-any-file: 'docs/products/alloydbomni/**'
 
-service/cassandra:
-  - changed-files:
-      - any-glob-to-any-file: 'docs/products/cassandra/**'
-
 service/clickhouse:
   - changed-files:
       - any-glob-to-any-file: 'docs/products/clickhouse/**'

.github/workflows/update-adv-params-all.yaml

@@ -6,12 +6,6 @@ on:
   workflow_dispatch:
 
 jobs:
-  update-adv-params-cassandra:
-    name: Update parameters - Cassandra
-    uses: ./.github/workflows/update-adv-params.yaml
-    with:
-      service-name: cassandra
-
   update-adv-params-clickhouse:
     name: Update parameters - Clickhouse
     uses: ./.github/workflows/update-adv-params.yaml

Makefile

@@ -2,10 +2,7 @@ SCRIPTS         = ./scripts
 INCLUDESDIR      = ./static/includes
 
 # Generate config listing for a service type
-all-service-type-configs: service-type-config-cassandra service-type-config-clickhouse service-type-config-flink service-type-config-grafana service-type-config-kafka_mirrormaker service-type-config-kafka_connect service-type-config-kafka service-type-config-mysql service-type-config-opensearch service-type-config-pg service-type-config-dragonfly service-type-config-valkey service-type-config-alloydbomni
-
-service-type-config-cassandra:
-	node "$(SCRIPTS)/service_type_parser.js" "cassandra" "$(INCLUDESDIR)/config-cassandra.md"
+all-service-type-configs: service-type-config-clickhouse service-type-config-flink service-type-config-grafana service-type-config-kafka_mirrormaker service-type-config-kafka_connect service-type-config-kafka service-type-config-mysql service-type-config-opensearch service-type-config-pg service-type-config-dragonfly service-type-config-valkey service-type-config-alloydbomni
 
 service-type-config-clickhouse:
 	node "$(SCRIPTS)/service_type_parser.js" "clickhouse" "$(INCLUDESDIR)/config-clickhouse.md"

docs/get-started.md

@@ -8,7 +8,6 @@ import {ButtonSecondary} from "@site/src/components/Buttons";
 import Card from "@site/src/components/Card";
 import Overview from "@site/static/images/content/platform/platform-overview.png";
 import GridContainer from "@site/src/components/GridContainer";
-import Cassandra from "@site/static/images/logos/cassandra.svg";
 import ClickHouse from "@site/static/images/logos/clickhouse.svg";
 import Dragonfly from "@site/static/images/logos/dragonfly.svg";
 import Opensearch from "@site/static/images/logos/opensearch.svg";

docs/platform/concepts/service-forking.md

@@ -24,8 +24,6 @@ Common use cases for forking include:
 
 You can fork the following Aiven services:
 
--   Apache Cassandra®
--   Caching
 -   ClickHouse®
 -   Grafana®
 -   Metrics
@@ -42,7 +40,7 @@ and connection pools are copied to the new service.
   [backup](/docs/platform/concepts/service_backups).
 - Service integrations are not copied over to the forked versions.
 - You cannot [fork Aiven for ClickHouse®](/docs/products/clickhouse/howto/restore-backup)
-  or Aiven for Apache Cassandra® services to a lower amount of nodes.
+  services to a lower amount of nodes.
 - Single sign-on (SSO) methods are not copied over to forked Aiven for OpenSearch® services
   because they are linked to specific URLs and endpoints, which change during
   forking. If you don't configure the SSO methods for the forked service, this can

docs/platform/concepts/service_backups.md

@@ -36,10 +36,6 @@ backups with the appropriate tooling:
     - `mysqldump` for small or medium-sized databases
     - [`mydumper`](https://github.com/mydumper/mydumper) <EarlyBadge/> for large databases
 
--   [Caching](https://redis.io/docs/connect/cli/#remote-backups-of-rdb-files):
-    `redis-cli`
--   [Cassandra®](https://docs.datastax.com/en/cql-oss/3.1/cql/cql_reference/copy_r.html)
-    `cqlsh`
 -   [OpenSearch®](https://github.com/elasticsearch-dump/elasticsearch-dump):
     `elasticdump`
 -   [Dragonfly®](https://redis.io/docs/latest/operate/rs/references/cli-utilities/redis-cli/): `redis-cli`
@@ -109,14 +105,6 @@ There are specific backup strategies for particular service types.
       <td>Hourly backup for 24 hours and Daily backup for 14 days</td>
       <td>Hourly backup for 24 hours and Daily backup for 30 days</td>
     </tr>
-    <tr>
-      <td>Aiven for Apache Cassandra®</td>
-      <td>Plan not available</td>
-      <td>Plan not available</td>
-      <td>Single day backup</td>
-      <td>Single day backup</td>
-      <td>Single day backup</td>
-    </tr>
     <tr>
       <td>Aiven for Caching</td>
       <td>Plan not available</td>
@@ -313,25 +301,6 @@ backups or hourly backups from the previous day.
 Find out more about using your backups in our guide:
 [Restore an OpenSearch® backup](/docs/products/opensearch/howto/restore_opensearch_backup)
 
-### Aiven for Apache Cassandra®
-
-Aiven for Apache Cassandra backups are taken every 24 hours. You can choose when a
-backup starts within the 24 hours and, for example, move the backup outside peak hours to
-save resources. To configure the `backup_hour` and `backup_minute` settings, go to
-the [Aiven Console](https://console.aiven.io) > your Aiven for Apache Cassandra service >
-<ConsoleLabel name="backups"/> > <ConsoleLabel name="actions"/> > **Configure backup settings**.
-
-:::note
-The point-in-time recovery (PITR) feature is not available. To be notified once the PITR
-feature is available for Aiven for Apache Cassandra, contact
-[support@aiven.io](mailto:support@aiven.io).
-:::
-
-### Aiven for Caching
-
-Aiven for Caching automatically backs up data every 12 hours and supports configurable
-data persistence using Redis Database Backup (RDB).
-
 #### Persistence settings
 
 You can configure the `redis_persistence` settings from <ConsoleLabel name="actions"/> >

docs/platform/howto/add-storage-space.md

@@ -15,20 +15,20 @@ additional storage instead of upgrading the compute resources.
 :::note[Availability]
 DDS is available for the following services:
 
-- Aiven for Apache Cassandra®
 - Aiven for Apache Kafka®
 - Aiven for ClickHouse®
 - Aiven for Grafana®
 - Aiven for Metrics
 - Aiven for MySQL®
 - Aiven for OpenSearch®
 - Aiven for PostgreSQL®
+
 :::
 
 When you add storage to your service, the Aiven platform provisions the
 extra disk space and dynamically adds it to your running instances.
 
-In a clustered service such as Apache Cassandra or Apache Kafka, the
+In a clustered service such as Apache Kafka, the
 additional storage is equally divided between the nodes. In a shared
 service, each node receives the total shared capacity of the added
 storage.

docs/platform/howto/btar/enable-backup-to-another-region.md

@@ -148,7 +148,7 @@ curl --request POST                                                    \
         "cloud": "string",
         "plan": "string",
         "service_name": "service_2_name",
-        "service_type": "cassandra",
+        "service_type": "pg",
         "user_config": {
             "additional_backup_regions": ["cloud-region-name"]
         }

docs/platform/howto/byoc/create-cloud/create-custom-cloud.md

@@ -8,7 +8,6 @@ import DocCardList from '@theme/DocCardList';
 import ConsoleLabel from "@site/src/components/ConsoleIcons";
 import Card from "@site/src/components/Card";
 import GridContainer from "@site/src/components/GridContainer";
-import Cassandra from "@site/static/images/logos/cassandra.svg";
 import RelatedPages from "@site/src/components/RelatedPages";
 
 To create custom clouds in Aiven using self-service, select your cloud provider to integrate with.

docs/platform/howto/create_new_service_user.md

@@ -20,8 +20,6 @@ By default, Aiven-managed services allow up to 50 users.
 This limit does not apply to the following services:
 
 - Aiven for AlloyDB Omni
-- Aiven for Apache Cassandra®
-- Aiven for Caching
 - Aiven for Dragonfly
 - Aiven for MySQL®
 - Aiven for PostgreSQL®