You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: windows_containers/windows-containers-release-notes-2-x.adoc
+32-8Lines changed: 32 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
[id="windows-containers-release-notes"]
1
+
[id="windows-containers-release-notes-2-x"]
2
2
= Windows Container Support for Red Hat OpenShift release notes
3
3
include::modules/common-attributes.adoc[]
4
4
:context: windows-containers-release-notes
@@ -17,24 +17,46 @@ The release notes for Red Hat OpenShift for Windows Containers tracks the develo
17
17
18
18
You must have a subscription to receive support for the Red Hat WMCO. Deploying Windows container workloads in production clusters is not supported without a subscription. If you do not have a subscription, you can use the community WMCO, a distribution that lacks official support. Request support through the link:http://access.redhat.com/[Red Hat Customer Portal].
19
19
20
-
[id="wmco-1-0-2"]
21
-
== Release notes for Red Hat Windows Machine Config Operator 1.0.2
20
+
[id="wmco-2-0-0"]
21
+
== Release notes for Red Hat Windows Machine Config Operator 2.0.0
22
22
23
-
This release of the WMCO provides initial support for running Windows compute nodes in an {product-title} cluster.
23
+
This release of the WMCO provides bug fixes and enhancements for running Windows compute nodes in an {product-title} cluster. The components of the WMCO 2.0.0 were released in link:https://access.redhat.com/errata/RHBA-2021:0440[RHBA-2021:0440].
24
24
25
25
WMCO supports self-managed clusters built using installer-provisioned infrastructure running on the following cloud providers:
26
26
27
27
* Amazon Web Services (AWS)
28
28
* Microsoft Azure
29
+
* VMware vSphere
29
30
30
-
The following Windows Server operating systems are supported in the initial release of the WMCO:
31
+
The following Windows Server operating systems are supported in this release of the WMCO:
31
32
32
33
* Windows Server Long-Term Servicing Channel (LTSC): Windows Server 2019
33
34
34
-
[id="wmco-1-0-1-known-issues"]
35
+
Version 2.x of the WMCO is only compatible with {product-title} 4.7.
36
+
37
+
[id="wmco-2-0-0-improvements"]
38
+
=== New features and improvements
39
+
40
+
This release adds the following new features and improvements.
41
+
42
+
[id="wmco-2-0-0-vsphere-support"]
43
+
==== Support for clusters running on VMware vSphere
44
+
45
+
You can now run Windows nodes on a cluster installed on VMware vSphere version 6.5, 6.7, or 7.0. You can create a Windows `MachineSet` object on vSphere to host Windows Server compute nodes. For more information, see xref:../windows_containers/creating_windows_machinesets/creating-windows-machineset-vsphere.adoc#creating-windows-machineset-vsphere[Creating a Windows `MachineSet` object on vSphere].
46
+
47
+
[id="wmco-2-0-0-monitoring"]
48
+
==== Enhanced Windows node monitoring
49
+
50
+
Windows nodes are now fully integrated with most of the monitoring capabilities provided by the web console. However, it is not possible to view workload graphs for pods running on Windows nodes in this release.
51
+
52
+
[id="wmco-2-0-0-known-issues"]
35
53
=== Known issues
36
54
37
-
* If you have a cluster with two Windows nodes, and you create a web server deployment with two replicas, the pods each land on a Windows compute node. In this scenario, if you create a `Service` object with type `LoadBalancer`, communication with the load balancer endpoint is flaky. To mitigate this issue, you must use Windows Server 2019 with a version 10.0.17763.1457 or earlier. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1905950[*BZ#1905950*])
55
+
* The filesystem graphs available in the web console do not display for Windows nodes. This is caused by changes in the filesystem queries. This will be fixed in a future release of WMCO. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1930347[*BZ#1930347*])
56
+
57
+
* The Prometheus windows_exporter used by the WMCO currently collects metrics through HTTP, so it is considered unsafe. You must ensure that only trusted users can retrieve metrics from the endpoint. The windows_exporter feature recently added support for HTTPS configuration, but this configuration has not been implemented for WMCO. Support for HTTPS configuration in the WMCO will be added in a future release.
58
+
59
+
* If you have a cluster with two Windows nodes, and you create a web server deployment with two replicas, the pods each land on a Windows compute node. In this scenario, if you create a `Service` object with type `LoadBalancer`, communication with the load balancer endpoint is not reliable. To mitigate this issue, you must use Windows Server 2019 with a version 10.0.17763.1457 or earlier. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1905950[*BZ#1905950*])
38
60
+
39
61
To pick the correct image for the `MachineSet` object, follow the instructions based on your cloud provider:
40
62
+
@@ -46,7 +68,7 @@ To pick the correct image for the `MachineSet` object, follow the instructions b
@@ -83,3 +105,5 @@ $ az vm image list --all --location <location> \// <1>
83
105
"version": "17763.1457.2009030514"
84
106
----
85
107
--
108
+
109
+
* There is currently an issue in Windows Server 2019 versions released after version `10.0.17763.1457` where Windows workloads behind a load balancer are unreachable for clusters installed on AWS. The Windows Server 2019 version `10.0.17763.1457` and earlier are recommended to work around this issue; however, these earlier images are no longer available. This image version unavailability prevents the ability to run Windows workloads behind a load balancer on clusters installed on AWS at this time. See this link:https://github.com/microsoft/Windows-Containers/issues/78[Microsoft Windows Containers issue] for more details.
0 commit comments