AtlasSchema and tolerations on kubernetes

[perpective2410]

Hi guys,

I have a simple AtlasSchema on Kubernetes and a deployment for my app.
My deployment is running ok (sql-migration-sample-service) as I have added the right tolerations. However, "sql-migration-sample-service-atlas-dev-db" which is created by your controller is in pending state as it does not have the necessary tolerations.

Can we add the tolerations to the AtlasSchema, so the "-atlas-dev-db' pod gets created with the right tolerations?

[giautm]

Hello @florentvaldelievre, can you share what tolerations you have apply on the AtlasSchema resource?

[perpective2410]

Actually @giautm , I dont specify the tolerations in the AtlasSchema resource as I could not find it in the CRD definition.
Could you please share an example?

Note that the I was expecting that the 'sql-migration-sample-service-atlas-dev-db' pod would be created with the same tolerations as 'sql-migration-sample-service'

  tolerations:
    - key: "kubernetes.azure.com/scalesetpriority"
      operator: "Equal"
      value: "spot"
      effect: "NoSchedule"
    - key: "dev"
      operator: "Equal"
      value: "true"
      effect: "NoSchedule"

[perpective2410]

@giautm As you mentioned in another post, we can deploy our own SQL server (dev) instance instead of letting AtlasSchema generate the 'atlas-dev-db' pod as it does not seem that we can specify the tolerations.
Do you have a timeline for this?

[giautm]

Do you have a timeline for this?

Not yet, but maybe next few weeks. We're rolling more features in the atlas-operator like support custom atlas.hcl. So, custom DevDB spec must be after that.