LogoLogo
CloudDiscordGitHub
  • 👉Getting Started
    • Introduction
    • Quick start
    • Learn by example
    • Case studies
    • How to contribute?
  • ⭐Memphis Broker
    • Architecture
    • Key concepts
      • Message broker
      • Station
      • Producer API
      • Consumer API
      • Consumer Group
      • Storage and Redundancy
      • Security/Authentication
      • Scaling
      • Ordering
      • Dead-letter Station (DLS)
      • Delayed messages
      • Data exchange
      • Idempotency (Duplicate processing)
      • Failover Scenarios
      • Troubleshooting process
      • Connectors
    • Best practices
      • Producer optimization
      • Compression
    • Memphis configuration
    • Comparisons
      • NATS Jetstream vs Memphis
      • RabbitMQ vs Memphis
      • AWS SQS vs Memphis
      • Apache Kafka vs Memphis
      • Apache Pulsar vs Memphis
      • ZeroMQ vs Memphis
      • Apache NiFi vs Memphis
    • Privacy Policy
  • ⭐Memphis Schemaverse
    • Overview
    • Getting started
      • Management
      • Produce/Consume
        • Protobuf
        • JSON Schema
        • GraphQL
        • Avro
    • Comparison
    • KB
  • 📦Open-Source Installation
    • Kubernetes
      • 1 - Installation
      • 2 - Access
      • 3 - Upgrade
      • Terraform
        • Deploy on AWS
        • Deploy on GCP
        • Deploy on DigitalOcean
      • Guides
        • Deploy/Upgrade Memphis utilizing predefined secrets
        • Monitoring/Alerts Recommendations
        • Production Best Practices
        • NGINX Ingress Controller and Cloud-Agnostic Memphis Deployments
        • Migrate Memphis storage between storageClass's
        • Expanding Memphis Disk Storage
        • Scale-out Memphis cluster
        • TLS - Deploy Memphis with TLS Connection to Metadata Frontend
        • TLS - Memphis TLS websocket configuration
        • TLS - Securing Memphis Client with TLS
        • Installing Memphis with an External Metadata Database
    • Docker
      • 1 - Installation
      • 2 - Access
      • 3 - Upgrade
    • Open-source Support
  • Client Libraries
    • REST (Webhook)
    • Node.js / TypeScript / NestJS
    • Go
    • Python
    • Kotlin (Community)
    • .NET
    • Java
    • Rust (Community)
    • NATS
    • Scala
  • 🔌Integrations Center
    • Index
    • Processing
      • Zapier
    • Change data Capture (CDC)
      • Debezium
    • Monitoring
      • Datadog
      • Grafana
    • Notifications
      • Slack
    • Storage tiering
      • S3-Compatible Object Storage
    • Source code
      • GitHub
    • Other platforms
      • Argo
  • 🗒️Release notes
    • KB
    • Releases
      • v1.4.3 - latest/stable
      • v1.4.2
      • v1.4.1
      • v1.4.0
      • v1.3.1
      • v1.3.0
      • v1.2.0
      • v1.1.1
      • v1.1.0
      • v1.0.3
      • v1.0.2
      • v1.0.1
      • V1.0.0 - GA
      • v0.4.5 - beta
      • v0.4.4 - beta
      • v0.4.3 - beta
      • v0.4.2 - beta
      • v0.4.1 - beta
      • v0.4.0 - beta
      • v0.3.6 - beta
      • v0.3.5 - beta
      • v0.3.0 - beta
      • v0.2.2 - beta
      • v0.2.1 - beta
      • v0.2.0 - beta
      • v0.1.0 - beta
Powered by GitBook
LogoLogo

Legal

  • Terms of Service
  • Privacy Policy

All rights reserved to Memphis.dev 2023

On this page
  • Introduction
  • Prerequisites
  • Step 1: Create DigitalOcean Kubernetes Cluster
  • Step 2: Connect to the Kubernetes cluster
  • Step 3: Install Memphis
  • Step 4: Expose Memphis for data using a load balancer
  • Step 5: Expose Memphis UI using a load balancer
  • Step 6: Connect your 1st app

Was this helpful?

  1. 📦Open-Source Installation
  2. Kubernetes
  3. Terraform

Deploy on DigitalOcean

Last updated 1 year ago

Was this helpful?

Introduction

DigitalOcean simplifies cloud computing so builders can spend more time creating software that changes the world.

DigitalOcean offers easy-to-use and configure cloud services like servers, kubernetes, object storage, serverless functions, a marketplace of applications, and much more.

Memphis.dev chose DigitalOcean Kubernetes Marketplace to offer both DO and Memphis users a 1-click installation of memphis cluster in a production kubernetes environment.

Prerequisites

  • DigitalOcean account

Step 1: Create DigitalOcean Kubernetes Cluster

Nodes are the servers that provide the Kubernetes compute and storage resources

Step 2: Connect to the Kubernetes cluster

Follow the below instructions to communicate with the newly created cluster

Step 3: Install Memphis

We need to create two different load balancers, one for data (the broker itself) and one for the UI.

Step 4: Expose Memphis for data using a load balancer

Run the following YAML

apiVersion: v1
kind: Service
metadata:
  annotations:
    meta.helm.sh/release-name: memphis
    meta.helm.sh/release-namespace: memphis
  creationTimestamp: "2022-07-19T16:25:00Z"
  finalizers:
  - service.kubernetes.io/load-balancer-cleanup
  labels:
    app.kubernetes.io/instance: memphis
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: memphis
    app.kubernetes.io/version: 1.16.0
    helm.sh/chart: memphis-0.1.0
  name: memphis-cluster
  namespace: memphis
spec:
  allocateLoadBalancerNodePorts: true
  externalTrafficPolicy: Cluster
  internalTrafficPolicy: Cluster
  ipFamilies:
  - IPv4
  ipFamilyPolicy: SingleStack
  ports:
  - name: memphis-cp-management
    nodePort: 30794
    port: 5555
    protocol: TCP
    targetPort: 5555
  - name: memphis-cp-tcp
    nodePort: 31534
    port: 6666
    protocol: TCP
    targetPort: 6666
  - name: client
    nodePort: 30363
    port: 7766
    protocol: TCP
    targetPort: 7766
  selector:
    app.kubernetes.io/instance: memphis
    app.kubernetes.io/name: memphis
  sessionAffinity: None
  type: LoadBalancer

The above will create a digitalocean load balancer with a public ip.

Step 5: Expose Memphis UI using a load balancer

Run the following YAML

 kubectl expose deployment memphis-ui --port=80 --target-port=80 \
        --name=memphis-ui --type=LoadBalancer

Step 6: Connect your 1st app

To get the public IPs of the load balancers we created before, run

kubectl get svc
Page cover image