feature wishes 2022

[tg123]

• target netstandard2.0: lightweight client, basic model and basic apis, no websocket or api requires newer .net runtime
• remove microsoft.rest: better httpclient
• api redesign: group apis for easier access (ide autocomplete)
• kubectl experience api
• go/java client parity
• doc server
• net5 code generator to replace generated codes
• more contributors

[brendandburns]

+1 to more contributors!

[m3nax]

I'm studying the sources, then I'll try to help

[goenning]

Would it be useful to have a ITokenProvider that uses Azure Identity to authenticate against AKS?

I see there’s one for GCP, we could contribute with one for Azure, but it’d add a package reference to Azure.Identity though

[tg123]

Would it be useful to have a ITokenProvider that uses Azure Identity to authenticate against AKS?

I see there’s one for GCP, we could contribute with one for Azure, but it’d add a package reference to Azure.Identity though

Thanks PR are welcomed.
I am thinking to move all to KubernetesClient.TokenProvider or KubernetesClient.TokenProvider.XXX

[goenning]

Yeah, I’d prefer the TokenProvider.XXX to avoid having vendor specific dependencies all bundled in one package

[m3nax]

A reduction in external dependencies (nugets) because they represent a security risk in enterprise environments.

[m3nax]

Better integration with .NET 6 hosting model and its Dependency injection (DI)

[m3nax]

More documentation of "how to use", examples are good but without explanation they are hard to understand for newbies like me.
Docs site?

Not understanding how the library works discourages people from using it by lowering its popularity.

I believe investing in documentation could attract new maintainers.

[tg123]

agree raw apis are hard to use and I am think generating c# doc site, but a more user friendly quick start site would be nice to have

[m3nax]

Like github pages or with another type of hosting?

[tg123]

gh page for sure, no budget for private hosting