Justin Parisi

So one of the biggest requests that we've had is with Trident, with ONTAP, it always requested a cluster-scoped account.

The reason for this is because of how Trident does storage properties.

I can go in, and in my storage class, I can specify that I want to provision a volume on SATA drives.

And in order to do that, Trident would look at the configured storage virtual machines, the aggregates that those storage virtual machines had access to, and then look at things like disk properties.

Well, in order to look at disk properties, you have to have a cluster scoped account, not an SVM scoped account.

So we made some modifications where you can now go in and define these types of things so that Trident can now operate with a storage virtual machine level account.

So from an administrator perspective, storage admins are much, much happier about this level of permissions than previously.

Absolutely.

It makes it a lot more administrator-friendly.

Us storage administrators, turns out we're kind of a paranoid group, and we don't like giving out permissions that have more or accounts with more permissions than they absolutely need.

What else you got for me?

So, you know, I saved the best for last.

E-Series support.

Trident now supports E-Series.

So that is official.

That is in the upstream or, well, upstream.

It has been published publicly.

We added internally for a little bit that we could, if somebody wanted it, they could request it.

So the big holdup there, and the reason why we had not previously published it, even though it's been done for quite a while, is, well, really it was Kubernetes.

So remember, Trident is a dynamic storage provisioner for Kubernetes.