bdburns
Building for the 99% Developers
Azure Arc enabled Kubernetes public preview
Service Mesh Interface (SMI): A specification for service mesh interoperability
Microsoft Open Sources Confidential Consortium Framework (CCF)
Why Google Cloud’s new boss will fail like the old boss
The history of Kubernetes and the community behind it
Graphical editing with vs. code now in azure cloud shell
Manage Azure IoT Edge Devices from Kubernetes
Kubernetes on Azure: Industry’s best end-to-end Kubernetes experience
Virtual Kubelet: Open source kubernetes connector for serverless containers
Azure brings new Serverless and DevOps capabilities to the Kubernetes community
Metaparticle: A stdlib for distributed systems from the co-creator of Kubernetes
This looks very similar to what we launched with Azure Container Instances last summer.
The Azure Container Instances kubernetes connector is open source and available here:
Visual Studio Connected Environment for Kubernetes
It's really awesome to see Microsoft's experience in developer productivity coming to cloud native applications!
PowerShell joins Bash in the Azure web and mobile console
Your future cloud is hybrid and so is Azure
Metaparticle/Storage: Simple automatic persistence for Node applications
Each container has hypervisor level isolation. We are not relying on kernel level isolation for security isolation between different user's containers.
https://github.com/Azure/aci-connector-k8s/blob/master/synch...
https://github.com/Azure/aci-connector-k8s/blob/master/aci.t...
Docs/SDK updates should roll out in the next 1-2 weeks.
TechCrunch: Microsoft's new container instances make containers fast and easy
Microsoft Joins the Cloud Native Compute Foundation (CNCF)
Azure Container Instances
a) For the longest time, I've wanted a "TTL" extension for Kubernetes objects, maybe this is a good excuse to build it. But concretely, since you are paying for the VMs in the cluster (IaaS) the Pods you deploy are "free" (until you run out of cluster capacity, of course)
b) The right way to do this is Kubernetes namespaces. You can specify a different Namespace in each user's draft config file that will place each developer's containers in a different namespace.
Now that I write that, though, that seems like too much work. We should probably automagically build a unique namespace for you...