VSTS/ TFS automated Release Pipelines for Web Applications with Docker
1 like150 views
The document discusses Docker and Kubernetes concepts including containers, images, orchestration, pods, services, deployments, ingress controllers, and connecting a Kubernetes cluster to Azure services like VSTS and container registries. Key steps shown are deploying an AKS Kubernetes cluster, setting up ingress controllers and config maps, creating namespaces and secrets, and applying YAML configurations to deploy applications, agents, and ingress rules.
![FROM microsoft/aspnetcore:2.0
WORKDIR /app
COPY --from=publish /app .
ENTRYPOINT ["dotnet", "a.dll"]
FROM microsoft/aspnetcore:2.0 AS base
WORKDIR /app
EXPOSE 80
FROM microsoft/aspnetcore-build:2.0 AS build
WORKDIR /src
COPY *.sln ./
COPY SampleWebApplication/SampleWebApplication.csproj
SampleWebApplication/
RUN dotnet restore
COPY . .
WORKDIR /src/SampleWebApplication
RUN dotnet build -c Release -o /app
FROM build AS publish
RUN dotnet publish -c Release -o /app
FROM base AS final
WORKDIR /app
COPY --from=publish /app .
ENTRYPOINT ["dotnet", "SampleWebApplication.dll"]](https://image.slidesharecdn.com/4tecturereleasepipelinevstskubernetes-180403064120/85/VSTS-TFS-automated-Release-Pipelines-for-Web-Applications-with-Docker-17-320.jpg)
![Param(
[string]$vstspat = "xxxxxxx",
[string]$subscriptionname = "xxxxxxx",
[string]$rsakeyfile = "xxxxxxx",
[string]$vstsaccount = "xxxxxxx"
)
### setup the cli settings
kubectl config unset contexts.demo-4t-k8s
az account set --subscription $subscriptionname
az account show
#az login #if needed
### setup kubernetes cluster
az group create -n "KubernetesDemo" -l "westeurope"
az acs create -n KubernetesDemo -d demo-4t-k8s -g KubernetesDemo --generate-ssh-keys --orchestrator-type kubernetes
az acs kubernetes get-credentials -g=KubernetesDemo -n=KubernetesDemo --ssh-key-file=$rsakeyfile
az acr create --name 4tKubernetesDemoRegistry --resource-group KubernetesDemo --sku Basic
az acr update -n 4tKubernetesDemoRegistry --admin-enabled true
$acrusername = az acr credential show -n 4tKubernetesDemoRegistry --query username
$acrpassword = az acr credential show -n 4tKubernetesDemoRegistry --query passwords[0].value
kubectl create secret docker-registry 4tkubernetesdemoregistry --docker-username=$acrusername --docker-password=$acrpassword--docker-server='4tkubernetesdemoregistry.azurecr.io' --
docker-email='info@4tecture.ch'
### deploy k8s configurations
kubectl apply -f .devfun_namespaces.yaml
kubectl apply -f nginx-ingress-defaultbackend.yaml
kubectl apply -f nginx-ingress-controller.yaml
kubectl apply -f nginx-ingress-service.yaml
kubectl -n kube-system get po
kubectl apply -f vsts_namespaces.yaml
kubectl create secret generic vsts --from-literal=VSTS_TOKEN=$vstspat --from-literal=VSTS_ACCOUNT=$vstsaccount --namespace=vsts
kubectl apply -f vsts_agent.yaml
kubectl apply -f lego_namespaces.yaml
kubectl apply -f lego_configmap.yaml
kubectl apply -f lego_deployment.yaml
kubectl apply -f devfun_ingress-dev.yaml
kubectl apply -f devfun_ingress-test.yaml
kubectl apply -f devfun_ingress-prod.yaml](https://image.slidesharecdn.com/4tecturereleasepipelinevstskubernetes-180403064120/85/VSTS-TFS-automated-Release-Pipelines-for-Web-Applications-with-Docker-64-320.jpg)
VSTS/ TFS automated Release Pipelines for Web Applications with Docker
- 3. ▪ ▪ ▪ ▪
- 6. Write Code Customer use the code Write Code Customer use the code
- 8. ▪ ▪ ▪ ▪ ▪ ▪
- 11. ▪ Versioned artifact ▪ Isolated deployable unit ▪ Container image is bit by bit identical when deployed ▪ Abstraction of data center resources ▪ ▪ Orchestration is “Cattle Business” ▪ ▪
- 13. Server Host OS Hypervisor Server Host OS Docker Engine Guest OS Guest OS Guest OS Bins/Libs Bins/Libs App A App A’ App B Bins/Libs Bins/Libs AppA AppA’ AppB AppB’ AppB AppB’ AppB AppB’ Containers are isolated, but share OS and, where appropriate, bins/librariesBins/Libs Image Source: https://sec.ch9.ms/sessions/build/2016/B822.pptx
- 14. ▪ ▪
- 16. Developer PC / Laptop Docker Engine Container Container Container
- 17. FROM microsoft/aspnetcore:2.0 WORKDIR /app COPY --from=publish /app . ENTRYPOINT ["dotnet", "a.dll"] FROM microsoft/aspnetcore:2.0 AS base WORKDIR /app EXPOSE 80 FROM microsoft/aspnetcore-build:2.0 AS build WORKDIR /src COPY *.sln ./ COPY SampleWebApplication/SampleWebApplication.csproj SampleWebApplication/ RUN dotnet restore COPY . . WORKDIR /src/SampleWebApplication RUN dotnet build -c Release -o /app FROM build AS publish RUN dotnet publish -c Release -o /app FROM base AS final WORKDIR /app COPY --from=publish /app . ENTRYPOINT ["dotnet", "SampleWebApplication.dll"]
- 19. App1 App2
- 20. VSTS Build VSTS Release Management Docker Registry Build App Test Build Container Repo Container Info Publish to Target Host Container Info Push Host Pull Config Artifact
- 21. ▪ ▪ ▪ ▪ ▪ ▪ ▪
- 22. ▪ ▪ ▪ ▪
- 23. ▪ ▪ Pod Container Pod Container Container 10.0.10.14 10.0.10.16 localhost Multi container Pods should only be used for highly coupled containers! Pod Container 10.0.10.15
- 24. ▪ ▪ Replication Controller / Deployment (Replication Set) Pod Container Pod Container Pod Container
- 25. ▪ ▪ ▪
- 26. ▪ ▪ ▪ ▪ ▪ ▪ Service Pod Container Pod Container Pod Container A 1.2 A 1.2 A 1.2 A 1.2
- 28. ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪
- 31. ▪ ▪ ▪ ▪ ▪ ▪
- 33. VSTS Azure Resource Group DCOS Master DCOS Master Master Agent VSTS Agent App1 App1 App1 App1 App1 App2 Git Build Release Internet AzureLoadBalancer Ingress LeGo
- 36. ▪ ▪ ▪ ▪ ▪ ▪
- 38. ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪
- 39. VSTS Build Agent Build Pool Build Pool Build Pool Build Definition Build Definition Build Queue Docker Engine Build Agent
- 55. ▪ ▪ ▪ ▪ ▪
- 61. We are looking for great talents to join our team! Apply to job@4tecture.ch www.4tecture.ch/jobs
- 64. Param( [string]$vstspat = "xxxxxxx", [string]$subscriptionname = "xxxxxxx", [string]$rsakeyfile = "xxxxxxx", [string]$vstsaccount = "xxxxxxx" ) ### setup the cli settings kubectl config unset contexts.demo-4t-k8s az account set --subscription $subscriptionname az account show #az login #if needed ### setup kubernetes cluster az group create -n "KubernetesDemo" -l "westeurope" az acs create -n KubernetesDemo -d demo-4t-k8s -g KubernetesDemo --generate-ssh-keys --orchestrator-type kubernetes az acs kubernetes get-credentials -g=KubernetesDemo -n=KubernetesDemo --ssh-key-file=$rsakeyfile az acr create --name 4tKubernetesDemoRegistry --resource-group KubernetesDemo --sku Basic az acr update -n 4tKubernetesDemoRegistry --admin-enabled true $acrusername = az acr credential show -n 4tKubernetesDemoRegistry --query username $acrpassword = az acr credential show -n 4tKubernetesDemoRegistry --query passwords[0].value kubectl create secret docker-registry 4tkubernetesdemoregistry --docker-username=$acrusername --docker-password=$acrpassword--docker-server='4tkubernetesdemoregistry.azurecr.io' -- docker-email='info@4tecture.ch' ### deploy k8s configurations kubectl apply -f .devfun_namespaces.yaml kubectl apply -f nginx-ingress-defaultbackend.yaml kubectl apply -f nginx-ingress-controller.yaml kubectl apply -f nginx-ingress-service.yaml kubectl -n kube-system get po kubectl apply -f vsts_namespaces.yaml kubectl create secret generic vsts --from-literal=VSTS_TOKEN=$vstspat --from-literal=VSTS_ACCOUNT=$vstsaccount --namespace=vsts kubectl apply -f vsts_agent.yaml kubectl apply -f lego_namespaces.yaml kubectl apply -f lego_configmap.yaml kubectl apply -f lego_deployment.yaml kubectl apply -f devfun_ingress-dev.yaml kubectl apply -f devfun_ingress-test.yaml kubectl apply -f devfun_ingress-prod.yaml