Frank Mai thxCode

Testing images

maiwj/win-metric:windows: for testing Prometheus metric
maiwj/win-openresty:windows: like nginx
maiwj/win-iis:windows: windows iis service
maiwj/win-gmsa:windows: for testing https://kubernetes.io/docs/tasks/configure-pod-container/configure-gmsa/

Generate testing YAML

On Windows:

Installing Tools

Docker install

# default install
iwr -uri https://gist.githubusercontent.com/thxCode/cd8ec26795a56eb120b57675f0c067cf/raw/10d748f604764aa337864941b99d79154cbc5fc2/zz_docker_install.ps1 -UseBasicParsing | iex

# custom version install

Dynamic - PVC

Following https://docs.microsoft.com/en-us/azure/aks/azure-files-dynamic-pv.

Create a StorageClass for creating PV dynamically

For now, we can only choose the following Azure storage redundancy for skuName:

Standard_LRS - standard locally redundant storage (LRS)
Standard_GRS - standard geo-redundant storage (GRS)
Standard_RAGRS - standard read-access geo-redundant storage (RA-GRS)

Windows Troubleshooting Summary

There are two servicing channels of Windows: LTSC (Long-Term Servicing Channel) and SAC (Semi-Annual Channel). 1903 or Windows Server, version 1903 is meaning the SAC server, oppositely, Windows Server 2019 is meaning the LTSC server. The SAC server only has the well known Core mode, which offers great advantages such as smaller hardware requirements, much smaller attack surface, and a reduction in the need for updates. The LTSC server support both GUI mode and Core mode.

The SAC server is not an "update" or "service pack" for LTSC. It's the current twice-yearly server release on the release track that is designed for customers who are moving at a "cloud cadence", such as those on rapid development cycles. This track is ideal for modern applications and innovation scenarios such as containers and micro-services. Each release in this track is supported for 18 months from the initial release. Get more from [Windows Server servicing channels: LTSC and SAC](

Windows Remote

Use PowerShell or PowerShell Core
Remote Management on PowerShell Core
- WMI
- WS-Management
- SSH
Summary

Allow to install armhf package
```
sudo dpkg --add-architecture armhf
```

Update the apt package index and install packages to allow apt to use a repository over HTTPS:

sudo apt-get update && sudo apt-get install -y \
    apt-transport-https \
    ca-certificates \
    curl \

	apiVersion: apps/v1
	kind: Deployment
	metadata:
	labels:
	app: probe-research
	name: probe-research
	spec:
	selector:
	matchLabels:
	app: probe-research

	kind: ServiceMonitor
	apiVersion: monitoring.coreos.com/v1
	metadata:
	name: hpa-app
	namespace: kube-public
	labels:
	app: hpa-app
	spec:
	namespaceSelector:
	matchNames:

	apiVersion: edge.cattle.io/v1alpha1
	kind: DeviceLink
	metadata:
	name: case1
	namespace: default
	spec:
	...
	template:
	metadata:
	labels: