MOF, Dash y MCP en un Pod.
Linux amd64 · kubectl · PostgreSQL externo · 1 Pod · 3 contenedores
Red privada · se requiere permiso CREATEDB · PostgreSQL solo con TLS no compatible.
Origen de la imagen
Descargar mof.yaml
Docker Hub · MOF v2.0.15 · Dash v2.0.17 · MCP v2.0.3
Descargar mof.yaml ↓Ver archivo
# MOF v2.0.15 + Dash v2.0.17 + MCP v2.0.3
# Edit database address, user and password before applying. Keep this file private.
# Keep the Service names mof, mof-mcp and dash, all in one namespace: the components find each
# other by them (mof:8080, mof-mcp:8001). Renamed Services can't connect.
# Private-network PostgreSQL without TLS. TLS-only databases are not supported by this release.
apiVersion: v1
kind: Namespace
metadata:
name: mof
---
apiVersion: v1
kind: Secret
metadata:
name: mof-database
namespace: mof
type: Opaque
stringData:
password: "REPLACE_WITH_YOUR_DATABASE_PASSWORD"
---
apiVersion: v1
kind: ConfigMap
metadata:
name: mof-config
namespace: mof
data:
RK_POSTGRES_0_ADDR: "db.example.com:5432"
RK_POSTGRES_0_USER: "mof"
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: mof
namespace: mof
spec:
replicas: 1
# First-release template: stop the old Pod before starting the new version.
strategy:
type: Recreate
selector:
matchLabels:
app: mof
template:
metadata:
labels:
app: mof
# Prometheus discovery by annotation; see the monitoring guide for a PodMonitor
annotations:
prometheus.io/scrape: "true"
prometheus.io/port: "8080"
prometheus.io/path: /internal/v1/mof/metrics
spec:
enableServiceLinks: false
nodeSelector:
kubernetes.io/arch: amd64
terminationGracePeriodSeconds: 120
containers:
- name: mof
image: mofcloud/mof:v2.0.15
envFrom:
- configMapRef:
name: mof-config
env:
- name: RK_POSTGRES_0_PASS
valueFrom:
secretKeyRef:
name: mof-database
key: password
ports:
- name: api
containerPort: 8080
startupProbe:
httpGet:
path: /v1/mof/site-info
port: api
periodSeconds: 10
failureThreshold: 60
readinessProbe:
httpGet:
path: /v1/mof/site-info
port: api
periodSeconds: 10
timeoutSeconds: 5
resources:
requests:
cpu: "500m"
memory: "1Gi"
volumeMounts:
- name: offer-cache
mountPath: /usr/src/mof/offer-cache
volumes:
- name: offer-cache
emptyDir: {}
---
apiVersion: v1
kind: Service
metadata:
name: mof
namespace: mof
spec:
selector:
app: mof
ports:
- name: api
port: 8080
targetPort: api
type: ClusterIP
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: mof-mcp
namespace: mof
spec:
replicas: 1
selector:
matchLabels:
app: mof-mcp
template:
metadata:
labels:
app: mof-mcp
spec:
enableServiceLinks: false
nodeSelector:
kubernetes.io/arch: amd64
containers:
- name: mof-mcp
image: mofcloud/mof-mcp:v2.0.3
ports:
- name: mcp
containerPort: 8001
readinessProbe:
exec:
command: ["node", "/app/build/healthcheck.js"]
periodSeconds: 10
timeoutSeconds: 5
resources:
requests:
cpu: "100m"
memory: "128Mi"
---
apiVersion: v1
kind: Service
metadata:
name: mof-mcp
namespace: mof
spec:
selector:
app: mof-mcp
ports:
- name: mcp
port: 8001
targetPort: mcp
type: ClusterIP
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: dash
namespace: mof
spec:
replicas: 1
selector:
matchLabels:
app: dash
template:
metadata:
labels:
app: dash
spec:
enableServiceLinks: false
nodeSelector:
kubernetes.io/arch: amd64
containers:
- name: dash
image: mofcloud/dash:v2.0.17
ports:
- name: web
containerPort: 80
readinessProbe:
httpGet:
path: /
port: web
periodSeconds: 10
resources:
requests:
cpu: "100m"
memory: "64Mi"
---
apiVersion: v1
kind: Service
metadata:
name: dash
namespace: mof
spec:
selector:
app: dash
ports:
- name: web
port: 80
targetPort: web
type: ClusterIP
Alibaba Cloud ACR · MOF v2.0.15 · Dash v2.0.17 · MCP v2.0.3
Descargar mof.yaml ↓Ver archivo
# MOF v2.0.15 + Dash v2.0.17 + MCP v2.0.3
# Edit database address, user and password before applying. Keep this file private.
# Keep the Service names mof, mof-mcp and dash, all in one namespace: the components find each
# other by them (mof:8080, mof-mcp:8001). Renamed Services can't connect.
# Private-network PostgreSQL without TLS. TLS-only databases are not supported by this release.
apiVersion: v1
kind: Namespace
metadata:
name: mof
---
apiVersion: v1
kind: Secret
metadata:
name: mof-database
namespace: mof
type: Opaque
stringData:
password: "REPLACE_WITH_YOUR_DATABASE_PASSWORD"
---
apiVersion: v1
kind: ConfigMap
metadata:
name: mof-config
namespace: mof
data:
RK_POSTGRES_0_ADDR: "db.example.com:5432"
RK_POSTGRES_0_USER: "mof"
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: mof
namespace: mof
spec:
replicas: 1
# First-release template: stop the old Pod before starting the new version.
strategy:
type: Recreate
selector:
matchLabels:
app: mof
template:
metadata:
labels:
app: mof
# Prometheus discovery by annotation; see the monitoring guide for a PodMonitor
annotations:
prometheus.io/scrape: "true"
prometheus.io/port: "8080"
prometheus.io/path: /internal/v1/mof/metrics
spec:
enableServiceLinks: false
nodeSelector:
kubernetes.io/arch: amd64
terminationGracePeriodSeconds: 120
containers:
- name: mof
image: registry.cn-hangzhou.aliyuncs.com/mofcloud/mof:v2.0.15
envFrom:
- configMapRef:
name: mof-config
env:
- name: RK_POSTGRES_0_PASS
valueFrom:
secretKeyRef:
name: mof-database
key: password
ports:
- name: api
containerPort: 8080
startupProbe:
httpGet:
path: /v1/mof/site-info
port: api
periodSeconds: 10
failureThreshold: 60
readinessProbe:
httpGet:
path: /v1/mof/site-info
port: api
periodSeconds: 10
timeoutSeconds: 5
resources:
requests:
cpu: "500m"
memory: "1Gi"
volumeMounts:
- name: offer-cache
mountPath: /usr/src/mof/offer-cache
volumes:
- name: offer-cache
emptyDir: {}
---
apiVersion: v1
kind: Service
metadata:
name: mof
namespace: mof
spec:
selector:
app: mof
ports:
- name: api
port: 8080
targetPort: api
type: ClusterIP
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: mof-mcp
namespace: mof
spec:
replicas: 1
selector:
matchLabels:
app: mof-mcp
template:
metadata:
labels:
app: mof-mcp
spec:
enableServiceLinks: false
nodeSelector:
kubernetes.io/arch: amd64
containers:
- name: mof-mcp
image: registry.cn-hangzhou.aliyuncs.com/mofcloud/mof-mcp:v2.0.3
ports:
- name: mcp
containerPort: 8001
readinessProbe:
exec:
command: ["node", "/app/build/healthcheck.js"]
periodSeconds: 10
timeoutSeconds: 5
resources:
requests:
cpu: "100m"
memory: "128Mi"
---
apiVersion: v1
kind: Service
metadata:
name: mof-mcp
namespace: mof
spec:
selector:
app: mof-mcp
ports:
- name: mcp
port: 8001
targetPort: mcp
type: ClusterIP
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: dash
namespace: mof
spec:
replicas: 1
selector:
matchLabels:
app: dash
template:
metadata:
labels:
app: dash
spec:
enableServiceLinks: false
nodeSelector:
kubernetes.io/arch: amd64
containers:
- name: dash
image: registry.cn-hangzhou.aliyuncs.com/mofcloud/dash:v2.0.17
ports:
- name: web
containerPort: 80
readinessProbe:
httpGet:
path: /
port: web
periodSeconds: 10
resources:
requests:
cpu: "100m"
memory: "64Mi"
---
apiVersion: v1
kind: Service
metadata:
name: dash
namespace: mof
spec:
selector:
app: dash
ports:
- name: web
port: 80
targetPort: web
type: ClusterIP
GHCR · MOF v2.0.15 · Dash v2.0.17 · MCP v2.0.3
Descargar mof.yaml ↓Ver archivo
# MOF v2.0.15 + Dash v2.0.17 + MCP v2.0.3
# Edit database address, user and password before applying. Keep this file private.
# Keep the Service names mof, mof-mcp and dash, all in one namespace: the components find each
# other by them (mof:8080, mof-mcp:8001). Renamed Services can't connect.
# Private-network PostgreSQL without TLS. TLS-only databases are not supported by this release.
apiVersion: v1
kind: Namespace
metadata:
name: mof
---
apiVersion: v1
kind: Secret
metadata:
name: mof-database
namespace: mof
type: Opaque
stringData:
password: "REPLACE_WITH_YOUR_DATABASE_PASSWORD"
---
apiVersion: v1
kind: ConfigMap
metadata:
name: mof-config
namespace: mof
data:
RK_POSTGRES_0_ADDR: "db.example.com:5432"
RK_POSTGRES_0_USER: "mof"
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: mof
namespace: mof
spec:
replicas: 1
# First-release template: stop the old Pod before starting the new version.
strategy:
type: Recreate
selector:
matchLabels:
app: mof
template:
metadata:
labels:
app: mof
# Prometheus discovery by annotation; see the monitoring guide for a PodMonitor
annotations:
prometheus.io/scrape: "true"
prometheus.io/port: "8080"
prometheus.io/path: /internal/v1/mof/metrics
spec:
enableServiceLinks: false
nodeSelector:
kubernetes.io/arch: amd64
terminationGracePeriodSeconds: 120
containers:
- name: mof
image: ghcr.io/mofcloud/mof:v2.0.15
envFrom:
- configMapRef:
name: mof-config
env:
- name: RK_POSTGRES_0_PASS
valueFrom:
secretKeyRef:
name: mof-database
key: password
ports:
- name: api
containerPort: 8080
startupProbe:
httpGet:
path: /v1/mof/site-info
port: api
periodSeconds: 10
failureThreshold: 60
readinessProbe:
httpGet:
path: /v1/mof/site-info
port: api
periodSeconds: 10
timeoutSeconds: 5
resources:
requests:
cpu: "500m"
memory: "1Gi"
volumeMounts:
- name: offer-cache
mountPath: /usr/src/mof/offer-cache
volumes:
- name: offer-cache
emptyDir: {}
---
apiVersion: v1
kind: Service
metadata:
name: mof
namespace: mof
spec:
selector:
app: mof
ports:
- name: api
port: 8080
targetPort: api
type: ClusterIP
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: mof-mcp
namespace: mof
spec:
replicas: 1
selector:
matchLabels:
app: mof-mcp
template:
metadata:
labels:
app: mof-mcp
spec:
enableServiceLinks: false
nodeSelector:
kubernetes.io/arch: amd64
containers:
- name: mof-mcp
image: ghcr.io/mofcloud/mof-mcp:v2.0.3
ports:
- name: mcp
containerPort: 8001
readinessProbe:
exec:
command: ["node", "/app/build/healthcheck.js"]
periodSeconds: 10
timeoutSeconds: 5
resources:
requests:
cpu: "100m"
memory: "128Mi"
---
apiVersion: v1
kind: Service
metadata:
name: mof-mcp
namespace: mof
spec:
selector:
app: mof-mcp
ports:
- name: mcp
port: 8001
targetPort: mcp
type: ClusterIP
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: dash
namespace: mof
spec:
replicas: 1
selector:
matchLabels:
app: dash
template:
metadata:
labels:
app: dash
spec:
enableServiceLinks: false
nodeSelector:
kubernetes.io/arch: amd64
containers:
- name: dash
image: ghcr.io/mofcloud/dash:v2.0.17
ports:
- name: web
containerPort: 80
readinessProbe:
httpGet:
path: /
port: web
periodSeconds: 10
resources:
requests:
cpu: "100m"
memory: "64Mi"
---
apiVersion: v1
kind: Service
metadata:
name: dash
namespace: mof
spec:
selector:
app: dash
ports:
- name: web
port: 80
targetPort: web
type: ClusterIP
Conserva los nombres de Service mof, mof-mcp y dash, todos en un mismo namespace. Los componentes se encuentran entre sí por estos nombres (mof:8080, mof-mcp:8001), así que no hay que configurar nada más; los Services renombrados no pueden conectarse.
Conexión a la base de datos
Completa tu PostgreSQL existente en mof.yaml:
RK_POSTGRES_0_ADDR- Dirección:puerto
RK_POSTGRES_0_USER- Usuario
stringData.password- Contraseña de la base de datos existente
Mantén las contraseñas entre comillas y este archivo privado.
Desplegar
kubectl apply -f mof.yaml
kubectl -n mof rollout status deployment/mof --timeout=10m
kubectl -n mof rollout status deployment/mof-mcp deployment/dashCuando los tres estén desplegados, obtén la contraseña de Admin:
kubectl -n mof logs deployment/mof | grep "Admin password"Abrir MOF
kubectl -n mof port-forward service/dash 8000:80Mantén esta terminal en ejecución.
http://127.0.0.1:8000/adminInstala tu licencia y crea usuarios.
http://127.0.0.1:8000Inicia sesión con tu cuenta de MOF.
Configuración avanzada
Compatibilidad de TLS con PostgreSQL
MOF aplica la configuración TLS a Mof y AsyncJobMof, pero no a las bases de datos de proveedores. Esta plantilla requiere una red privada de confianza y no puede usar PostgreSQL solo con TLS.
Dominio, HTTPS y OAuth opcional
Usa un Ingress controller existente y apunta tu dominio hacia él. Define la clase, el hostname y un Secret de TLS existente en el namespace mof.
Descargar ingress.yaml ↓# Requires an installed Ingress controller and an existing TLS Secret.
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: mof
namespace: mof
spec:
ingressClassName: nginx
tls:
- hosts: [mof.example.com]
secretName: mof-web-tls
rules:
- host: mof.example.com
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: dash
port:
number: 80
kubectl apply -f ingress.yaml
kubectl -n mof get ingressHabilita MCP en Admin → Configuración → MCP. Endpoint: /v1/mof/remote-mcp. Los tokens no necesitan OAuth; OAuth en el navegador requiere HTTPS, MOF_PUBLIC_URL y MOF_MCP_OAUTH_SECRET.
Health checks y resolución de problemas
kubectl -n mof get pods
kubectl -n mof logs deployment/mof --tail=100
kubectl -n mof logs deployment/mof-mcp --tail=60
kubectl -n mof logs deployment/dash --tail=60
kubectl -n mof exec deployment/mof -- wget -q -O - http://mof-mcp:8001/healthResultado esperado: mof, mof-mcp y dash en Running y Ready; MCP ready: true. Si el arranque falla, revisa la descarga de imágenes, la arquitectura del nodo y el acceso a la base de datos.
Parámetros de la plantilla
RK_POSTGRES_0_ADDRhostname:puerto del PostgreSQL externo, accesible desde el Pod.RK_POSTGRES_0_USERRol de base de datos existente con permiso para crear las bases de datos de MOF y de los proveedores.mof-database / passwordContraseña de la base de datos guardada en un Secret; se inyecta solo en MOF.Services mof / mof-mcp / dashUn Deployment y un Service cada uno. Se encuentran entre sí por nombre de Service; no hay nada que configurar.replicas / strategy1 / Recreate. Las actualizaciones interrumpen el servicio brevemente; la alta disponibilidad con varias réplicas queda fuera de esta plantilla.resources.requestsReservas de scheduling, no límites de memoria. Dimensiona MOF según tu volumen de facturas y monitoriza el uso real.offer-cache / emptyDirCaché de precios públicos reconstruible. Se pierde cuando se reemplaza el Pod; los datos de facturación permanecen en PostgreSQL.ingressClassName / host / tlsAjústalo a tu controlador instalado, dominio público y Secret de TLS. Opcional para comprobaciones locales con port-forward.Actualizaciones, datos y escalado
Haz una copia de seguridad de PostgreSQL, actualiza las versiones de las imágenes y aplica mof.yaml. Reinicia después de cambiar un ConfigMap o un Secret. Las actualizaciones con Recreate interrumpen el servicio.
kubectl -n mof rollout restart deployment/mof
kubectl -n mof rollout status deployment/mof --timeout=10mSolo una réplica; los Jobs de Kubernetes bajo demanda no están implementados. Los datos de la aplicación permanecen en el PostgreSQL externo; la caché de precios se puede reconstruir.