Not immune, no. But the majority of work was figuring out the authentication logic and reading/writing the tokens in a way that is compatible with Azure CLI. The parsing of the REST API response is comparatively easy.
Azure is still changing a lot, but they also have an OK policy with their API changes, IMO. Old API versions are kept alive for some time, so there's always some time to migrate.
>Error from server (Forbidden): configmaps is forbidden: User "system:serviceaccount:pascalgn:pascalgn-user" cannot list resource "configmaps" in API group "" in the namespace "pascalgn"
Is that intended? Because I can get secrets, but not configmaps
Also, currently (?) there is no way to create services, so for now we can create Pods, but they cannot serve any data (or I did something wrong)
Yes! Config maps are coming very soon, just doing a bit of testing to ensure they're safely isolated. This is the next feature we'll add for sure!
As for services, that gets tricky due to our shared cluster design, and for now services can only be created thru the interface. Were working on tools that show users what their service yaml ought to be, but we're mostly focusing on demoing and educating users about the Deployment object. Via the interface you can expose an HTTP service (and we'll handle HTTPS termination), and TCP <-> internet is coming soon!
Good point! Unfortunately, for most statements it's very difficult to find a source (hence this writeup in the first place). Where possible, I linked directly to the primary source (e.g. published paper)
