←back to thread

320 points benocodes | 1 comments | | HN request time: 0s | source
Show context
otterley ◴[] No.41897080[source]
Looks very Azure-centric. Both installation guides (https://drasi.io/how-to-guides/install-sample-applications/b... and https://drasi.io/how-to-guides/install-sample-applications/c...) require Azure to work.

And then there's this:

> Installing Drasi in an EKS cluster can be significantly more complex than a standard installation on other platforms. Instead of downloading a CLI binary using the provided installation scripts, this approach requires modifying the source code of the Drasi CLI and building a local version of the CLI.

Is this an actual requirement or just the current easy path?

replies(7): >>41897227 #>>41897293 #>>41897541 #>>41897811 #>>41897940 #>>41901203 #>>41909560 #
dtquad ◴[] No.41897227[source]
That is usual for new Microsoft open source projects. It takes 1-2 months for the Azure dependencies to go away.
replies(1): >>41900118 #
1. 3abiton ◴[] No.41900118[source]
I'm curious about the other examples? I get it though, as many of these projects are built fulfilling a specific need within MS infrastructure.