Skip to content
This repository has been archived by the owner on Nov 20, 2023. It is now read-only.

not create pod in azure kubernetes service for sqlserver service #1609

Open
abhishek-ats opened this issue Sep 7, 2023 · 1 comment
Open

Comments

@abhishek-ats
Copy link

  • name: sqlserver
    image: mcr.microsoft.com/mssql/server:latest
    env:
    • name: SA_PASSWORD
      value: Ats@1234
    • name: ACCEPT_EULA
      value: Y
      bindings:
    • name: saasdb
      connectionString: Server=${host};Port=${port};User Id=sqlserver;Password=${env:SA_PASSWORD};
    • name: admindb
      connectionString: Server=${host};Port=${port};User Id=sqlserver;Password=${env:SA_PASSWORD};
    • name: identitydb
      connectionString: Server=${host};Port=${port};User Id=sqlserver;Password=${env:SA_PASSWORD};
    • name: reportdb
      connectionString: Server=${host};Port=${port};User Id=sqlserver;Password=${env:SA_PASSWORD};
    • name: lmsdb
      connectionString: Server=${host};Port=${port};User Id=sqlserver;Password=${env:SA_PASSWORD};
@Phiph
Copy link

Phiph commented Oct 3, 2023

It looks like you have no port mappings in your binding config. You are also secifying multiple connection strings referring to multiple ports, I'm not too sure of SQL server supports that out of the box.

Why have you opted to run SQL server in K8s via Tye - I'd love to learn more about your use case and advise you!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants