Diagnose unknown repositories
Elastic Cloud on Kubernetes extends Kubernetes orchestration capabilities to allow you to deploy and manage components of the Elastic Stack. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes. Self-managed deployments are Elastic Stack deployments managed without the assistance of an orchestrator. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
ECK
Generally available
Self-managed
Generally available
When a snapshot repository is marked as "unknown", it means that an Elasticsearch node is unable to instantiate the repository due to an unknown repository type. This is usually caused by a missing plugin on the node. Make sure each node in the cluster has the required plugins by following the following steps:
- Retrieve the affected nodes from the affected resources section of the health report.
- Use the nodes info API to retrieve the plugins installed on each node.
- Cross reference this with a node that works correctly to find out which plugins are missing and install the missing plugins.
Learn more about snapshot and restore plugins:
- Snapshot/restore repository plugins
- Installing plugins in self-managed clusters
- Installing plugins on Elastic Cloud on Kubernetes
Elastic Cloud Hosted and Elastic Cloud Enterprise only support specific repository types, which can't be extended using plugins. Learn more.