How to use versioned migrations with ent and atlas kubernetes operator?

[idc77]

I have this backend using ent.
Now I've been getting into kubernetes.
I have installed the Atlas Operator via helm as instructed in the readme.

kubectl apply -f https://raw.githubusercontent.com/ariga/atlas-operator/master/config/integration/databases/mysql.yaml
deployment.apps/mysql created
service/mysql created
secret/mysql-credentials created

I'm going to build an image of the backend with ent with ko and push to my private registry.
Next the deployment and service

apiVersion: apps/v1
kind: Deployment
metadata:
  name: cooksbooks-backend
  labels:
    app: cooksbooks-backend
  namespace: cooksbooks
spec:
  replicas: 1
  selector:
    matchLabels:
      app: cooksbooks-backend
  template:
    metadata:
      name: cooksbooks-backend
      namespace: cooksbooks
      labels:
        app: cooksbooks-backend
    spec:
      containers:
        - name: backend
          image: registry.icod.de/cooksbooks/backend/cooksbooks-1234567890bad8de8eeab40cd
          imagePullPolicy: Always
          command: [ cooksbooks ]
          args: [ "restful", "--bp=false", "--debug=false", "--addr=tcp::8080", "--dsn=mysql.default.svc.cluster.local:3306/cooksbooks" ]
          ports:
            - containerPort: 8080
              protocol: TCP
              name: backend-port
      imagePullSecrets:
        - name: registrycredentials
      restartPolicy: Always
---
apiVersion: v1
kind: Service
metadata:
  name: cooksbooks-backend-service
  namespace: cooksbooks
spec:
  selector:
    app: cooksbooks-backend
  ports:
    - port: 8080
      protocol: TCP
      name: backend-svc-port
      targetPort: backend-port

Now how do I use the Atlas Operator to run the migrations first, please?

[rotemtam]

First, you need to make the migrations available to the operator. The easiest way is to push them to the Atlas schema registry using the "atlas migrate push". Alternatively, inline them in the spec of an AtlasMigration resource or provide them as a config map.

For config map/registry you then create an AtlasMigration referencing the migration dir and the version that you want to deploy within that directory

Details:

https://atlasgo.io/integrations/kubernetes/operator#versioned-schema-migrations

https://atlasgo.io/blog/2023/12/06/gitops-for-databases-part-1

[idc77]

how can I access "atlas migrate push" when it's all in containers? should I do it manually, enter the container?
I'm sorry but this is all very vague.
Can you be more hands on?

In the Terraform thread you were like this is awesome and the guy created a migration job.
Wouldn't that mean that the proper way is to create a job that runs before the container is ran?

I'm going by this: https://entgo.io/docs/versioned-migrations
I have the migrations in ent/migrate/migrations

What am I doing next?

[idc77]

Ah you want to sell me your cloud offering. I'm not interested. No money honey.
I asked you a detailed question and you're trying to upsell me your cloud offering, which isn't even in v1? WTH?

[rotemtam]

Hey @idc77

You might have missed some of the information I sent you, so I will try to point it out .

First, pushing to schema registry does require a cloud account , which is free. So, not selling you anything, if you enjoy using it, we will appreciate your business. As you know , Atlas is backed by a commercial company. If you prefer to use projects that aren't, there are plenty of alternatives in the migrations space. We feel this is the only way to build something sustainable and high quality.

Second, if you read my reply and link to the docs I sent, you will see that you can provide the migration dir to the operator as a config map or inline it.

Finally, I don't mean to offend, but please keep this snarky tone and attitude to yourself. We are providing here a lot of value for free to this community and if you don't like it you can look elsewhere.

Best regards,

Rotem

[a8m]

Ah you want to sell me your cloud offering. I'm not interested. No money honey. I asked you a detailed question and you're trying to upsell me your cloud offering, which isn't even in v1? WTH?

Hey Darko,

Ent and Atlas are projects I personally have spent thousands of hours building them, and support users like you. Unfortunately, this isn't the first time you've made disrespectful and non-constructive comments in our communities. You enjoy what we do for free and have received support dozens of times over the last three years. You clearly don't appreciate it.

If you have a question, comment, or suggestion, please initiate a discussion as people do in real life - there are real people working on these projects, and mean comments in the style of HN/Reddit are not acceptable here. Otherwise, you will no longer be part of our communities. Is that clear?

---

For your question, Rotem was clear about alternatives:

Alternatively, inline them in the spec of an AtlasMigration resource or provide them as a config map.

For config map/registry you then create an AtlasMigration referencing the migration dir and the version that you want to deploy within that directory

Details:

https://atlasgo.io/integrations/kubernetes/operator#versioned-schema-migrations

https://atlasgo.io/blog/2023/12/06/gitops-for-databases-part-1