HN user

kastden

98 karma
Posts5
Comments16
View on HN

To make the transition seamless for you and your organization, there are no changes to any Azure AD capabilities, APIs, login URLs, PowerShell cmdlets, Microsoft authentication library (MSAL), developer experiences, or tooling.

So we will still be calling it Azure AD in most situations where someone interacts with it

I'd suggest trying out https://k3s.io/ then. Runs on pretty much anything and supports multiple nodes that can be added later. They have ripped out a lot of things you might not need (cloud drivers, etc). Despite that, it was easy to install things like storage drivers or Cilium for networking when I wanted that.

I used k3sup to setup my cluster, but that was just for convenience.

Thanks for the explanation! I think SQLite is fine for this too.

My use case would be running this on AWS ECS, but since this wouldn't get written to very often (probably) and the file hopefully wouldn't be very big either, I could just have the container or a sidecar pull it from S3 on startup and sync it at regular intervals and on shutdown.

This looks very nice! It’s not mentioned in the README, so I’m wondering how persistence is handled? EDIT: To be clear, I see backups is mentioned, but I’m wondering if it’s a database file like sqlite3 or something else.