# TKG Windows packaging

2 major components to windows packaging.

## What we currently do

We have a custom buildinfo w/ a custom TKR bom that points to windows componetns. i.e.
- https://gitlab.eng.vmware.com/TKG/bolt/bolt-release-yamls/-/merge_requests/152#diff-content-5f6ba14af8940ead08cd027c740e213db3b27a43 is used as an input to
- https://gitlab.eng.vmware.com/perit/subway/-/blob/master/src/cmd/burrito/buildinfo.go
- This then builds n image which we hardoode in https://kscom.svc.eng.vmware.com/jenkins/self-service/windows-sandbox-3/

This works to build functioning windows nodes

## What we'll do in dakar

The current solution works but isnt integrated w/ current dakar packaging stream. so to make sure customers have access to our windows solution:

- PR 1.21.1
-

- Integration into Dakar mainline:
- https://gitlab.eng.vmware.com/TKG/bolt/bolt-release-yamls/
- v3.publish.yaml
- https://gitlab.eng.vmware.com/TKG/bolt/bolt-release-yamls/-/merge_requests/207
- ^ intial cut but needs a rebase
- kubernetes 1.21
- publ components for windows kube component
- PR above will include a corgi test that points to the windows branch:
- branch = `test-infra/create-windows-cluster`
- test_10_windows.py

- After merging into Dakar: Image builder job
- Windows ova builder has been setup but awaiting k8s v3.publish.yaml
- tkg-burrito-delivery-service job
- build burrito w/ the tkg-daily build payload and be release blocking to enusure windows is always available
- windows-sandbox-3 job
- build image (takes 30 minutes, will cache images daily)W
- using see gitlab /perit/subway src/cmd/burrito/buildinfo.go for logic
- also need to make w-s-3 release-blockin.