Collaborative and visual infrastructure as design for Kubedb Catalog
Components (33)
The Meshery model for Kubedb Catalog supports the following components.
hazelcast-version
oracle-version
click-house-version
druid-version
elasticsearch-version
etcd-version
ferret-db-version
kafka-connector-version
kafka-version
maria-db-version
memcached-version
mongo-db-version
mssql-server-version
my-sql-version
percona-xtra-db-version
pg-bouncer-version
pgpool-version
postgres-version
proxy-sql-version
rabbit-mq-version
redis-version
schema-registry-version
singlestore-version
solr-version
zoo-keeper-version
cassandra-version
ignite-version
db2version
hana-db-version
milvus-version
neo4j-version
qdrant-version
weaviate-version
What are Meshery Models and Components?
Meshery Models and Components represent the fundamental building blocks of your infrastructure. Use them to define the structure and configuration of your infrastructure and deployments by incorporating their use into a Design. Think of Designs as blueprints or templates that encapsulate everything from network configurations to service definitions.
Learn more about Models, Components, Relationships, and Designs
What is the Meshery Registry
The Meshery Registry is a vital component within Meshery, serving as a centralized repository for managing a diverse range of cloud and cloud native resources. It stores and organizes crucial information such as models, categories, components, and relationships, enabling efficient interaction and utilization of these resources within the Meshery ecosystem. You can conveniently access and manage registry data through Meshery UI, and through Meshery CLI (mesheryctl registry).Learn more about the Registry
Designs containing Kubedb Catalog
Related Tutorials for Kubedb Catalog
Related Models in App Definition and Development
- Actions Runner Controller (ARC)
- Aerokube
- Aerospike Kubernetes Operator
- AIGIS UK
- Apache Cassandra
- Apache ShardingSphere
- ArangoDB Kubernetes Operator
- Argo CD Applications
- Argo CD Operator
- Argo Workflows
- Armory Spinnaker Operator
- Artifact Hub
- AWS DocumentDB
- AWS DynamoDB
- AWS ElastiCache
- AWS EventBridge
- AWS Kinesis
- AWS Lambda
- AWS MQ
- AWS Relational Database Service
- AWS Simple Notification Service
- AWS Simple Queuing Service
- Azure API Management
- Azure App Configuration
- Azure App Service
- Backstage
- Brigade
- Buildpacks
- Camel K
- cdk8s For Kubernetes
- Chaos
- Cloudbees Previews
- Cloudevents
- CloudNativePG
- Couchbase Monitor Stack
- Couchbase Operator
- Devfile
- Flagger
- Flux
- Gerrit Operator
- Github Actions Runner Operator
- Github Actions Runners
- GitLab
- Gitlab Controller
- Gitlab Runner Operator
- Helm Controller
- Jenkins Operator
- Kanister Operator
- Kubedb
- Kubedb CRDs
- Kubedb Grafana Dashboards
- Kubedb Metrics
- Kubedb Ops Manager
- Kubedb Opscenter
- Kubedb UI Server
- KubeRocketCI Pipeline Operator
- Kubevela
- Kubevirt
- MinIO Operator
- MySQL Operator
- NATS Operator
- Nocalhost
- OpenFeature
- OpenGitOps
- Openkruise
- Operator Framework
- Porter
- Posthog
- Pulsar Operator
- Pulsar Resources Operator
- RabbitMQ Cluster Operator
- RabbitMQ Operator
- Schemahero
- Serverless Workflow
- Stackgres Operator
- Strimzi Kafka Operator
- Strimzi Registry Operator
- Telepresence
- Tikv Operator
- Tremor
- Vald
- Vela Workflow
- Vitess