jsturtevant

 az vm image  list-skus -l eastus -p MicrosoftWindowsServer -f WindowsServerSemiAnnual

jsturtevant

Windows Containers Logging

With Windows Containers, as with any application, you will need to consider your logging strategy. In the containers world it is generally accepted to log to STDOUT/STDERR (standard out and standard error). As you scale up your services you will need to aggregate and store these logs for analysis and debugging later on. There exist many back end systems to aggregate logs and help with analysis, in Azure you have Log Analytics and Application Insights.

There are two general strategies for configuring your containers to send logs to a backend logging system containers:

• In container logging - Your application is responsible for sending the logs directly to the backend system. This can also be [configured via sidecar].
• Host level logging - You application is configured for sending logs to a log collection agent on the system. The logging agent will

jsturtevant

---
apiVersion: v1
kind: Namespace
metadata:
  name: custom-metrics
---
kind: ServiceAccount
apiVersion: v1
metadata:
  name: custom-metrics-azure-apiserver

jsturtevant

---
apiVersion: v1
kind: Namespace
metadata:
  name: custom-metrics
---
kind: ServiceAccount
apiVersion: v1
metadata:
  name: custom-metrics-azure-apiserver

jsturtevant

# windowsservercore
kubectl run windows-1803 -it --rm -n default --image microsoft/windowsservercore:1803  --image-pull-policy=IfNotPresent --restart=Never --overrides '{ "spec": {"nodeSelector":{"beta.kubernetes.io/os":"windows"}}}' --command -- cmd

# nanoserver
 kubectl run windows-1803-nano -it --rm -n default --image microsoft/nanoserver:1803  --image-pull-policy=IfNotPresent --restart=Never --overrides '{ "spec": {"nodeSelector":{"beta.kubernetes.io/os":"windows"}}}' --command -- cmd

jsturtevant

#https://github.com/Microsoft/vscode-go/issues/1555#issuecomment-393366905
"useApiV1": false,
"dlvLoadConfig": {
    "followPointers": true,
    "maxVariableRecurse": 1,
    "maxStringLen":300,
    "maxArrayValues": 64,
    "maxStructFields": -1
}

jsturtevant

ssh -i $KEY_FILE -o ProxyCommand="ssh -i $KEY_FILE -W %h:%p user@<public-ip>" user@<internal-ip>

jsturtevant

winnode="$(kubectl get nodes -l "beta.kubernetes.io/os=windows" -o json | jq -rc '.items | map({nodeInfo: .status.nodeInfo})[0]')"

echo $winnode
#output
{"nodeInfo":{"architecture":"amd64","bootID":"","containerRuntimeVersion":"containerd://Unknown","kernelVersion":"10.0.17763.194
","kubeProxyVersion":"v1.13.0-alpha.2","kubeletVersion":"v1.13.0-alpha.2","machineID":"3472k8s000","operatingSystem":"windows","osImage":"Windows Server Datacenter","systemUUID":""}}

echo "$winnode" | jq .
#output
parse error: Invalid string: control characters from U+0000 through U+001F must be escaped at line 2, column 1

jsturtevant

$lockedFiles = "kubelet.err.log", "kubelet.log", "kubeproxy.log", "kubeproxy.err.log", "containerd.err.log", "containerd.log"
$netDebugFiles = "network.txt", "endpoint.txt", "policy.txt", "ip.txt", "ports.txt", "routes.txt", "vfpOutput.txt"

$timeStamp = get-date -format 'yyyyMMdd-hhmmss'
$zipName = "$env:computername-$($timeStamp)_logs.zip"

$paths = get-childitem c:\k\*.log -Exclude $lockedFiles
$paths += $lockedFiles | Foreach-Object { Copy-Item "c:\k\$_" . -Passthru }
$scm = Get-WinEvent -FilterHashtable @{logname='System';ProviderName='Service Control Manager'} | Where-Object { $_.Message -Like "*docker*" -or $_.Message -Like "*kub*" } | Select-Object -Property TimeCreated, Id, LevelDisplayName, Message

jsturtevant

apiVersion: v1
kind: Pod
metadata:
  labels:
    test: liveness
  name: dns-liveness-windows
spec:
  containers:
  - name: dns-liveness
    image: mcr.microsoft.com/windows/servercore:1809