The latest version of LinkerdD that is available in nixpkgs is 2.14.9. With the change to enterprise will you work and publish nix flakes for LinkerdD enterprise version of the CLI?
Hi @sstarcher! The Nix community did the heavy lifting there, so this is probably more of a question for them than for us.
If they want to keep it pure OSS, one option would be to point that work to the OSS edge releases instead. It looks like they have that machinery already. There was a similar discussion about OpenSUSE packages here: Does it make sense to package the edge releases for openSUSE (instead of following stable)? · linkerd/linkerd2 · Discussion #12669 · GitHub
If they want to use the BEL releases, the binaries are published in Releases · BuoyantIO/linkerd-buoyant · GitHub in a very similar way. These are non-OSS artifacts, but they’re freely available for anyone to use, and will work without a license key—though they do expect the cluster to have a license key.
Hope that helps!
To rephrase what you are saying. You have no intention of supporting a nix install of your BEL releases and we will have to do that work ourselves.
I think it might be more fair to say that we, Buoyant, haven’t ever supported Nix installs of anything. 
If you look in generic.nix you’ll find bryanasdev000 and Gonzih listed as maintainers, so they may be the folks to contact.
update-stable.sh looks like it’s likely to do the right thing if it’s changed to
- pull release tags from https://api.github.com/repos/linkerd/linkerd-buoyant/releases;
- look for the latest tag starting with
enterprise-; and - use https://github.com/linkerd/linkerd-buoyant/archive/refs/tags/enterprise-${VERSION}.tar.gz to download the release tarball.
But, again, the maintainers of the Nix packages are going to be a better place than we are to look in more detail into this.
How large could you consider the risk of using edge linkerd cli with the linkerd enterprise deployments?
Using the edge CLI with enterprise deployments is not likely to work – the edge CLI will try to refer to edge resources everywhere rather than the enterprise resources you actually want.
@sstarcher How familiar are you with the Nix side of things? Do you know whether they have an appetite for non-OSS components? The patch required here to add/change their current setup from stable → enterprise looks like it would be quite minimal. Or if they wouldn’t take that patch, is there an alternative? I am happy to explore the options here, I think we just don’t know a lot about Nix.
Nix typically builds everything from source, but you could create your own nix flake to instead just download the binary. I don’t have a ton of experience with Nix so I can’t speak for how the community normally functions.