Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Managed Kubernetes in Azure door Arjen Steinhauer

Managed Kubernetes in Azure door Arjen Steinhauer

devNetNoord #13


March 22, 2018

More Decks by devNetNoord

Other Decks in Technology


  1. Even voorstellen… • Arjen Steinhauer [email protected] • Principle Consultant /

    Architect bij ilionx (Utrecht) • Werkzaam in IT sinds 1995 • Microsoft platform (.NET) • Microsoft Azure • Integration • Continuous Delivery / DevOps
  2. 1. Maintaining existing applications 2. Re-deploying new versions of existing

    applications 3. Troubleshooting issues from feature additions to existing applications 4. Deploying a new application
  3. 1. Maintaining existing applications 2. Fixing* existing applications 3. Adding

    features to existing applications 4. Fixing the features someone else added to existing applications 5. Building a new application (maybe … if there’s time!)
  4. Set of IT Problems forever Patches break installations Deployment binders

    Lead to shadow IT, tension between dev/ops Etc Works on my machine
  5. Common approach • Client Server model • 3-tier architecture •

    Object Oriented (C#, java, C++, …) • RPC, DCOM, SOAP, WCF, REST, … Client Service DB Client Client
  6. “Speed-up” of traditional approach… • Reality is non linear •

    More nodes does not mean more scale 10 5 Speed up number of nodes
  7. Need more scaling options  Scale Cube (3D) • X

    • Horizontal scale • More nodes • Network Load Balancing • Y • Functional scale • Micro services • Z • Data partitioning • Separate tenants • Separate by region Y X Z
  8. Micro Services: the goal • Build easier Distributed Systems •

    Automatic 3D scaling is possible • Less skilled dev’s can build more complex systems • Save development and operation costs • Run same code on-premises and in Cloud
  9. Service Service Micro Services Client Service DB Client Client Service

    Service Service Load Balancer DB Cache Stateless middle-tier Stateless front-end state
  10. Service Service Micro Services Client Service A data Client Client

    Service Service Service B Service Locator data data warehouse Stateful middle-tier Stateless front-end Analytics/ disaster recovery
  11. Containers = Operating system virtualization Container Container Container Traditional virtual

    machines = hardware virtualization VM VM VM Windows Server containers No different from Linux containers Container Container Container Hyper-V containers Isolation plus performance Container Container Container
  12. Balance of control and responsibility depends on the category of

    the service MOVE-IN READY Use immediately with minimal configuration SOME ASSEMBLY REQUIRED Existing services are a starting point, with additional configuration for a custom fit BUILD FROM THE GROUND UP Building blocks, create your own solution or apps from scratch Responsibility On- Prem IaaS PaaS SaaS Applications Data Runtime Middleware O/S Virtualization Servers Storage Networking Microsoft Customer
  13. Notes: (*1) (*2) (*3) App service and “container apps” provides

    for orchestration of a single container apps. In the current state, this is a PaaS offering that abstracts away these concepts. (*4) DC/OS has a good-sized OSS community behind it, however it pales in comparison with K8 ecosystem. (*5) Docker as a container format is very popular and has good community engagement, Docker EE gets some benefits from being associated with it. However, it does not have a strong ecosystem by itself. (*6) DC/OS refers to enterprise DC/OS. ACS provides open source DC/OS
  14. Docker Hub and Docker Store Docker Trusted Registry Azure Container

    Registry Docker Registry https://docs.docker.com/registry https://github.com/docker/distribution