Third question is about kubernetes orion installat...
# prefect-community
b
Third question is about kubernetes orion installation. Everytime I started my docker/kubernetes environment, services become active but I have to reconfigure storage, create work queues and all delpyment/flows are gone in UI. Isn’t the data or the POD disk persisted ?
This is the K8s deployment manifest. I think the persistence is ignored as well as the namespace.
Copy code
apiVersion: apps/v1
kind: Deployment
metadata:
  name: orion
spec:
  selector:
    matchLabels:
      app: orion
  replicas: 1  # We're using SQLite, so we should only run 1 pod
  template:
    metadata:
      labels:
        app: orion
    spec:
      containers:
      - name: api
        image: prefecthq/prefect:2.0b3-python3.8
        command: ["prefect", "orion", "start", "--host", "0.0.0.0", "--log-level", "WARNING"]
        imagePullPolicy: "IfNotPresent"
        ports:
        - containerPort: 4200
      - name: agent
        image: prefecthq/prefect:2.0b3-python3.8
        command: ["prefect", "agent", "start", "kubernetes"]
        imagePullPolicy: "IfNotPresent"
        env:
          - name: PREFECT_API_URL
            value: <http://orion:4200/api>
k
Where would it be persisted to once the container stops?
a
The persistence layer is the backend database, so you would need to configure your Orion setup to use this database - this spec uses embedded SQLite DB we don't have any template for external Postgres yet, feel free to give it a try if you want to contribute. For now, the easiest way to get persistence would be to use Cloud 2.0
b
If the persistence volume is added to kubernetes manifest, definetely the storage where the SQLLite DB resides can benefit from this. Let me work on this and circle back about the solution.
👀 1
👍 1