当前位置: 首页 > 软件库 > 云计算 > 云原生 >

blackbelt-aks-hackfest

授权协议 MIT License
开发语言 Google Go
所属分类 云计算、 云原生
软件类型 开源软件
地区 不详
投 递 者 华和悦
操作系统 跨平台
开源组织
适用人群 未知
 软件概览

Azure Container Hackfest

Delivering modern cloud native applications with ​open source technologies on Azure​

NOTE: We have moved this content over to a new and updated repository https://github.com/Azure/kubernetes-hackfest

Overview

This workshop will guide you through migrating an application from "on-premise" to containers running in Azure Kubernetes Service.

The labs are based upon a node.js application that allows for voting on the Justice League Superheroes (with more options coming soon). Data is stored in MongoDB.

Note: These labs are designed to run on a Linux CentOS VM running in Azure (jumpbox) along with Azure Cloud Shell. They can potentially be run locally on a Mac or Windows, but the instructions are not written towards that experience. ie - "You're on your own."

Note: Since we are working on a jumpbox, note that Copy and Paste are a bit different when working in the terminal. You can use Shift+Ctrl+C for Copy and Shift+Ctrl+V for Paste when working in the terminal. Outside of the terminal Copy and Paste behaves as expected using Ctrl+C and Ctrl+V.

Lab Guides - Day 1

  1. Setup Lab environment
  2. Run app locally to test components
  3. Create Docker images for apps and push to Azure Container Registry(ACR Build)
  4. Create Docker images for apps and push to Azure Container Registry
  5. Create an Azure Kubernetes Service (AKS) cluster
  6. Deploy application to Azure Kubernetes Service
  7. Kubernetes UI Overview
  8. Operational Monitoring and Log Management
  9. Application and Infrastructure Scaling
  10. Moving your data services to Azure PaaS (CosmosDB)
  11. Update and Deploy New Version of Application
  12. Upgrade an Azure Kubernetes Service (AKS) cluster

Lab Guides - Day 2

These labs can be completed in no particular order.

  1. CI/CD Automation
  2. Kubernetes Ingress Controllers
  3. Kubernetes InitContainers
  4. Azure Service Broker
  5. Persistent Storage
  6. Azure Container Instances and ACI Connector
  7. Kubernetes Stateful Sets (coming soon)
  8. Secrets and ConfigMaps (coming soon)
  9. Helm Charts deep dive (coming soon)
  10. Troubleshooting and debugging (coming soon)
  11. RBAC and Azure AD integration (coming soon)

Contributing

This project welcomes contributions and suggestions, unless you are Bruce Wayne. Most contributions require you to agree to aContributor License Agreement (CLA) declaring that you have the right to, and actually do, grant usthe rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to providea CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructionsprovided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct.For more information see the Code of Conduct FAQ orcontact opencode@microsoft.com with any additional questions or comments.

License

This software is covered under the MIT license. You can read the license here.

This software contains code from Heroku Buildpacks, which are also covered by the MIT license.

This software contains code from [Helm][], which is covered by the Apache v2.0 license.

You can read third-party software licenses [here][Third-Party Licenses].

  • 一、什么是AKS? AKS:全称 Azure Kubernetes。微软提供的高度可用、安全且完全托管的Kubernetes服务。 点此进入官方网站 二、概述 旨在构建可在任何地方运行的云原生应用程序;Azure提供的服务(Azure App Service、Azure Functions、Azure Logic Apps、Azure Event Grid、Azure API Management

 相关资料
  • AKS Engine - Units of Kubernetes on Azure! Project status This project is stable, meaning the pace of new features is intentionally low. AKS Engine is maintained by teams who depend on it including AK

  • Azure Kubernetes Service (AKS) Baseline Cluster This reference implementation demonstrates the recommended starting (baseline) infrastructure architecture for a general purpose AKS cluster. This imple

  • 这是我的secret-class.yml文件(keyvault的名称是正确的)。另外,xxx-xxxx-xxx-xxx-xxx-xxx-xxx-xxx-xxx4b5ec83是AKS托管标识(SonarQubeHelm-agentpool)的对象 这是我的deployment.yml文件 我为AKS托管标识分配了正确的权限,以便访问keyvault(XXX-XXXXX-XXX-XXX-XXXX4B5

  • 我使用Azure库伯内特斯服务来提供我的微服务。当我登录到我的API网关时,它可以工作。但是当我尝试通过Api-Gateway联系另一个微服务时,我收到一个错误(500内部服务器错误)。我还在库伯内特斯设置了一个Eureka命名服务器,我提供的所有微服务都在那里注册。但是为什么我的API网关不能与我的微服务通信?它也可以在本地机器上工作。 我的Yaml文件 我所有的微服务都运行在同一个节点上。我的

  • 堆栈:Azure Kubernetes服务 NGINX Ingress Controller-https://github.com/Kubernetes/ingress-nginx AKS LoadBalancer Docker容器 我的目标是创建一个K8s集群,它将允许我在一个IP下使用多个POD,创建一个微服务架构。在使用了大量的教程和文档之后,我的EndGoal没有任何运气。我已经到了能够使

  • 我的dockerized服务(webrtc服务器)同时使用TCP和UDP传输协议。我在Azure Kubernetes服务公司工作。如您所知,我们无法在Kubernetes中同时使用TCP和UDP proto创建LoadBalancer服务(更多信息请参见此处) 此外,我还尝试创建了两个服务: 一个用于TCP端口 一个用于UDP 用一个公共IP绑定它们,但得到:“确保负载平衡器”消息。 唯一的解决