Operator 4.0.2

• The Helm chart now supports configuring tolerations for the operator's deployment.
• Domain resource schema now supports .spec.maxClusterUnavailable, which is the default value for the maximum number of cluster members that can be temporarily unavailable, such as during a roll.
• Resolved an issue that would prevent Model in Image domains from working correctly when Secured Production Mode is enabled.
• Pods created for WebLogic Server instances that are members of a WebLogic cluster will now include the label weblogic.clusterObservedGeneration specifying the metadata.generation of the Cluster resource. This is similar to the already existing weblogic.domainObservedGeneration label that specifies the observed generation of the Domain resource.
• Schema conversion from "v8" to "v9" Domains now uses shorter name prefixes when converting "v8" style auxiliary images.
• The Helm chart specifies a more compatible securityContext for the operator's deployment when the kubernetesPlatform value is "OpenShift".
• The Node Manager instance running within the Pod created for each WebLogic Server instance now supports additional configuration for how often to restart WebLogic before the Pod's liveness probe fails and the Pod is recreated.
• Samples and utility scripts now support the environment variables KUBERNETES_CLI, which defaults to kubectl, and WLSIMG_BUILDER, which defaults to docker, to make it easier to use these samples and scripts on platforms that use binaries with different names.
• Resolved an issue where a "v8" Domain that used auxiliary images and also configured logHome could be converted to a "v9" Domain that was invalid.
• Resolved an issue where Domains that had a .spec.domainUid that was different from the value of .metadata.name would not start.