Upgrading to OpenCloud 8.x.x

OpenCloud 8.x.x changes how resources are indexed and creates a new search index. Complete the regular upgrade first by following the Standard Upgrade Guide.

important

OpenCloud 8.x.x is a Rolling release and is not intended for production environments. For more information, see the Release Lifecycle.

Quick upgrade

After OpenCloud has been upgraded, rebuild the search index using the commands for your search backend.

Bleve (default)

docker compose exec opencloud opencloud search index --all-spaces --force-rescan --insecure

Verify that older files can be found in the Web Client. Then remove the old index:

docker compose exec opencloud sh -c 'rm -r "$OC_BASE_DATA_PATH/search/bleve"'

OpenSearch

docker compose exec opencloud opencloud search index --all-spaces --force-rescan --insecure

Verify that older files can be found in the Web Client. Then list the existing indexes and remove the old one:

curl "http://localhost:9200/_cat/indices/opencloud-resources*?v"
curl -X DELETE "http://localhost:9200/opencloud-resources"

What this does

• The new, empty index (e.g. bleve-v4 / opencloud-resources-v4) is created automatically. The old one stays until you remove it.
• New activity is indexed right away, but files that existed before and are not touched are not found until you re-index.
• Re-indexing runs while the service keeps working.
• After it finishes, delete every index except the one with the highest -v<N> suffix (indexes up to 7.4 have no suffix). Verify search first.

hinweis

--insecure is needed because the internal gRPC transport is not TLS-encrypted by default (OC_GRPC_CLIENT_TLS_MODE defaults to off). Drop it only if you run gRPC with TLS. This is safe here — the command just triggers a rescan; the re-indexing happens inside the OpenCloud process.