이 페이지에서는 Google Kubernetes Engine(GKE) 표준 모드에서 Windows Server 컨테이너에 대해 간략하게 설명합니다. 클러스터를 만드는 방법은 Windows Server 노드 풀을 사용하여 클러스터 만들기를 참조하세요. Windows Server 노드 이미지 및 컨테이너는 GKE Autopilot 모드에서 사용할 수 없습니다.
개요
GKE 기반 Windows Server 컨테이너를 사용하면 Windows Server 애플리케이션의 민첩성, 배포 속도, 관리 간소화 등 Kubernetes의 이점을 활용할 수 있습니다. 동일한 클러스터에서 Windows Server와 Linux 컨테이너를 나란히 실행할 수 있으므로 중앙 관리 영역에서 두 컨테이너 플랫폼을 모두 관리할 수 있습니다.
Microsoft Hyper-V 컨테이너는 현재 지원되지 않습니다.
노드 이미지
Windows Server 반기 채널(SAC) 또는 Windows Server 장기 서비스 채널(LTSC)를 사용하여 Windows Server 컨테이너 노드 이미지를 빌드할 수 있습니다.
단일 클러스터에는 다양한 Windows Server 버전을 사용하는 여러 Windows Server 노드 풀이 있을 수 있지만 각 개별 노드 풀은 하나의 Windows Server 버전만 사용할 수 있습니다. 이러한 버전 간의 차이점에 대한 자세한 내용은 Windows Server 노드 이미지 선택을 참조하세요.
스토리지
Windows Server 컨테이너는 GKE가 제공하는 다양한 스토리지 옵션을 활용할 수 있습니다. Windows에서 GKE 스토리지 옵션을 사용하는 예시는 로컬 SSD를 참조하세요.
Windows에는 ext4 파일 스토리지 유형이 지원되지 않으므로 Windows Server 컨테이너로 작업할 때는 StorageClass 객체를 만들고 PersistentVolumeClaim 객체의 storageClassName 필드에 객체 이름을 지정해야 합니다. Compute Engine 영구 디스크를 사용 중인 경우에는 NTFS를 파일 스토리지 유형으로 사용해야 합니다.
Linux 컨테이너와 마찬가지로 Windows 컨테이너는 프로세스 및 리소스 격리 경계를 제공합니다. Windows Server 컨테이너는 엔터프라이즈 멀티테넌시에 사용할 수 있습니다.
하지만 Microsoft에서 Windows 컨테이너 이스케이프 취약점에 대한 서비스를 제공하지 않으므로 악의적인 멀티테넌시 시나리오나 다른 위험 수준이 요구되는 시나리오에서는 Windows 노드를 사용하지 않는 것이 좋습니다. 대신 각 애플리케이션 또는 개발팀에 별도의 클러스터와 Google Cloud프로젝트를 제공하여 격리를 수행해야 합니다.
기능 제한사항
일부 Kubernetes 기능은 아직 Windows Server 컨테이너에서 지원되지 않습니다. 또한 일부 기능은 Linux에만 해당되며 Windows에서는 작동하지 않습니다. 지원되는 Kubernetes 기능과 지원되지 않는 Kubernetes 기능의 전체 목록은 Kubernetes 문서를 참조하세요.
지원되지 않는 Kubernetes 기능 외에도 지원되지 않는 일부 GKE 기능이 있습니다.
GKE 클러스터의 경우 Windows Server 노드 풀에서 다음 기능이 지원되지 않습니다.
애플리케이션을 현대화할 때는 기존 도구 및 워크플로를 지원하는 엔드 투 엔드 DevOps 관리 환경에도 이를 사용할 수 있기를 원할 수 있습니다. 이를 위해 Google은 빌드, 테스트, 배포, 구성, 모니터링 애플리케이션이 Windows 컨테이너와 올바르게 작동하는지 확인하기 위해 여러 파트너와 협력하고 있습니다. 여기에서는 GKE에서 Windows 컨테이너 지원을 위해 테스트한 몇 가지 사용 사례 및 파트너 솔루션을 보여줍니다.
사용 사례
설명
파트너
CI/CD
파트너의 CI/CD 솔루션은 Windows 컨테이너에서 실행되는 애플리케이션을 빌드, 테스트, 배포할 수 있습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[],[],null,["# Windows Server containers on GKE\n\n[Standard](/kubernetes-engine/docs/concepts/choose-cluster-mode)\n\n*** ** * ** ***\n\n| **Warning:** Windows Server Semi-Annual Channel (SAC) images aren't supported after August 9, 2022 because Microsoft is removing support for the SAC. For potential impact and migration instructions, refer to [Windows Server Semi-Annual Channel end of servicing](/kubernetes-engine/docs/deprecations/windows-server-sac).\n\nThis page provides an overview of Windows Server containers in\nGoogle Kubernetes Engine (GKE) Standard mode. To learn how to create a cluster, see\n[Creating a cluster using Windows Server node pools](/kubernetes-engine/docs/how-to/creating-a-cluster-windows). Windows Server node images and containers aren't available in GKE Autopilot mode.\n\nOverview\n--------\n\nUsing Windows Server containers on GKE enables you to take\nadvantage of the benefits of Kubernetes: agility, speed of deployment and\nsimplified management of your Windows Server applications. You can run\nyour Windows Server and Linux containers side by side in the same cluster,\nwhich allows for a central management plane for both container platforms.\nMicrosoft Hyper-V containers are not currently supported.\n\nNode images\n-----------\n\nYou can build your Windows Server container\n[node images](/kubernetes-engine/docs/concepts/node-images) using Windows Server\nSemi-Annual Channel (SAC) or Windows Server Long-Term Servicing Channel (LTSC).\nA single cluster can have multiple Windows Server node pools using different Windows\nServer versions, but each individual node pool can only use one Windows Server\nversion. To learn more about the differences between these versions, see\n[Choosing your Windows Server node images](/kubernetes-engine/docs/how-to/creating-a-cluster-windows#choose_your_windows_server_node_image).\n\nStorage\n-------\n\nYour Windows Server containers can take advantage of many of the storage\noptions that GKE provides. For an example of using\nGKE storage options with Windows, see\n[Local SSDs](/kubernetes-engine/docs/how-to/persistent-volumes/local-ssd).\n\nWhen working with Windows Server containers, you must create a `StorageClass`\nobject, and specify the name of that object in the `storageClassName` field of\nthe `PersistentVolumeClaim` object because the `ext4` file storage type is not\nsupported with Windows. If you are using a Compute Engine persistent disk, you\nmust use NTFS as the file storage type.\n\nThe Compute Engine persistent disk CSI Driver is also available for Windows Server containers.\nFor more details, see [Using the Compute Engine persistent disk CSI Driver](/kubernetes-engine/docs/how-to/persistent-volumes/gce-pd-csi-driver).\n\nSecurity\n--------\n\nLike Linux containers, Windows containers provide a process and resource\nisolation boundary. Windows Server containers can be used for\n[enterprise multi-tenancy](/kubernetes-engine/docs/concepts/multitenancy-overview#enterprise_multi-tenancy).\nHowever, because Microsoft does not [intend to service](https://www.microsoft.com/en-us/msrc/windows-security-servicing-criteria)\nWindows container escape vulnerabilities, the use of Windows nodes is not\nrecommended in hostile [multi-tenancy](/kubernetes-engine/docs/concepts/multitenancy-overview)\nscenarios or those where differing risk levels are needed. Instead, give each\napplication or development team a separate cluster and Google Cloud\nproject to achieve isolation.\n\nFeature limitations\n-------------------\n\nThere are some Kubernetes features that are not yet supported for\nWindows Server containers. In addition, some features are Linux-specific and do not\nwork for Windows. For the complete list of supported and unsupported Kubernetes features,\nsee the [Kubernetes documentation](https://kubernetes.io/docs/setup/production-environment/windows/intro-windows-in-kubernetes/#supported-functionality-and-limitations).\n\nIn addition to the unsupported Kubernetes features, there are some GKE\nfeatures that are not supported.\n\nFor GKE clusters, the following features are not supported with\nWindows Server node pools:\n\n- [Cloud TPUs](/tpu/docs/tpus) (`--enable-tpu`)\n- [Image streaming](/kubernetes-engine/docs/how-to/image-streaming)\n- [Intranode visibility](/kubernetes-engine/docs/how-to/intranode-visibility) (`--enable-intra-node-visibility`)\n- [IP masquerade agent](/kubernetes-engine/docs/how-to/ip-masquerade-agent)\n- [Kubernetes alpha cluster](/kubernetes-engine/docs/concepts/alpha-clusters) (`--enable-kubernetes-alpha`)\n- [Node Local DNS cache](/kubernetes-engine/docs/how-to/nodelocal-dns-cache)\n- [Private use of Class E IP addresses](/kubernetes-engine/docs/how-to/alias-ips#enable_reserved_ip_ranges)\n- [Private use of public IP addresses](/kubernetes-engine/docs/how-to/alias-ips#enable_pupis)\n- [Network policy logging](/kubernetes-engine/docs/how-to/network-policy-logging)\n- [Kubernetes `service.spec.sessionAffinity`](https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies)\n- [GPUs](/compute/docs/gpus) (`--accelerator`)\n- [Setting the maximum Pods per node greater than the default limit of 110](/kubernetes-engine/docs/how-to/flexible-pod-cidr)\n- [Filestore CSI driver](/kubernetes-engine/docs/how-to/persistent-volumes/filestore-csi-driver)\n- Docker-based [CloudSQL Auth proxy](/sql/docs/mysql/sql-proxy)\n- [IPv4/IPv6 dual-stack networking](/kubernetes-engine/docs/concepts/alias-ips#dual_stack_network) IPv6 is not supported on Windows nodes.\n\n[Local External Traffic Policy](/kubernetes-engine/docs/how-to/service-parameters#externalTrafficPolicy)\non Windows node pool is only supported with GKE\nversion v1.23.4-gke.400 or later.\n\nOther Google Cloud products that you want to use with GKE clusters\nmight not support Windows Server node pools. For specific limitations, refer to\nthe documentation of that product.\n\nResources\n---------\n\nThe following sections provide links to relevant resources for Windows Server\ncontainers on GKE.\n\n### Discover\n\nReview these resources to discover information about Windows on GKE:\n\n- Read the [Run Windows Server containers on GKE](/blog/products/containers-kubernetes/run-windows-server-containers-on-gke) blog.\n- Read the [Windows Server containers on GKE now GA](/blog/products/containers-kubernetes/windows-server-containers-on-gke-now-ga) blog.\n- Read the [Windows Server support comes to Google Distributed Cloud](/blog/topics/anthos/windows-server-support-comes-to-anthos-on-prem) blog.\n- Read the [Migrating Legacy OSes to Google Cloud](/resources/forrester-cost-savings-of-migrating-os-to-cloud-tei-study) case study.\n\n### Get started\n\nConsider these resources for getting started:\n\n- Watch the [How to modernize and run Windows apps in GKE Enterprise GKE](https://www.youtube.com/watch?v=w6tzIjZhTIk) video.\n- Watch the [Migrate, Manage \\& Modernize: Windows Workloads Powered by GKE and GKE Enterprise](https://cloudonair.withgoogle.com/events/gke-anthos) webinar.\n- Try out the [New Microsoft and Windows on Google Cloud Demo Center](/blog/topics/windows/new-microsoft-and-windows-on-google-cloud-demo-center) demos.\n- Learn how to [Create a cluster using Windows Server node pools](/kubernetes-engine/docs/how-to/creating-a-cluster-windows).\n\n### Create \\& deploy\n\nFor guidance on creating and deploying your applications, see these pages:\n\n- [Deploying a Windows Server application](/kubernetes-engine/docs/how-to/deploying-windows-app)\n- [Deploying a stateful application](/kubernetes-engine/docs/how-to/stateful-apps)\n- [Building Windows Server multi-arch images](/kubernetes-engine/docs/tutorials/building-windows-multi-arch-images)\n- [Using the Compute Engine persistent disk CSI Driver](/kubernetes-engine/docs/how-to/persistent-volumes/gce-pd-csi-driver#using_the_for_windows_clusters)\n\n### Integrate with Active Directory\n\nFor guidance on Active Directory integration, see these pages:\n\n- [Best practices for running Active Directory on Google Cloud](/compute/docs/instances/windows/best-practices)\n- [Configure Windows Server nodes to automatically join an Active Directory domain](/kubernetes-engine/docs/how-to/auto-join-windows-nodepools)\n- [Deploy ASP.NET apps with Windows Authentication in GKE Windows containers](/kubernetes-engine/docs/how-to/deploying-aspnet-with-windows-authentication-in-gke-windows-containers)\n\n### Troubleshoot\n\nFor help with troubleshooting, see [Collecting diagnostic information](/compute/docs/instances/collecting-diagnostic-information).\n\n### Explore\n\nTo explore and learn about using GKE Enterprise for Windows, see these resources:\n\n- Learn about [Migrate to Containers](/migrate/containers/docs) for migrating Windows workloads.\n- Learn about using Windows node pools in [Google Distributed Cloud](/anthos/clusters/docs/on-prem/1.8/how-to/user-guide-for-windows-server-os-node-pools).\n\n### Partner solutions\n\nWhen you modernize your applications, you also want to incorporate them into an\nend-to-end DevOps management experience that works with your existing tooling\nand workflows. To that end, Google has worked with several partners to make sure\nthat your build, test, deploy, config and monitoring applications work well with\nWindows containers. Here are some use cases and partner solutions that we've\ntested to support Windows containers in GKE:"]]
