anchor.diff:  link:https://access.redhat.com/support/offerings/techpreview[Technology Preview
   Features Support Scope]
   
  -Starting in {product-title} 4.1, some _feature gates_, a set of key=value pairs
  -that describe Technology Preview features, will ship enabled. You can change the
  -default feature gates, but doing so prevents you from upgrading your cluster.
  -Any change to a feature gate stops an upgrade. Clusters with a changed feature
  -gate must be re-installed to apply even an asynchronous release update.
  -
   In the table below, features marked *TP* indicate _Technology Preview_ and
  -features marked *GA* indicate _General Availability_.
  -
  -If a feature is marked *yes;on*, that feature is controlled by a feature gate
  -that is enabled, or turned on, when shipped. If a feature is marked *yes;off*,
  -that feature is controlled by a feature gate that is disabled, or turned off,
  -when shipped.
  +￼	features marked *GA* indicate _General Availability_.
   
   .Technology Preview Tracker
   [cols="4",options="header"]
   |====
  -|Feature |Feature gate |OCP 3.11 |OCP 4.1
  +|Feature |OCP 3.11 |OCP 4.1
   
   |Prometheus Cluster Monitoring
  -|
   |GA
   |GA
   
   |Local Storage Persistent Volumes
  -|
   |TP
   |TP
   
   |CRI-O for runtime pods
  -|
   |GA* footnoteref:[disclaimer, Features marked with `*` indicate delivery in a z-stream patch.]
   |GA
   
   |Tenant Driven Snapshotting
  -|
   |TP
   |TP
   
   |`oc` CLI Plug-ins
  -|
   |TP
   |TP
   
   |Service Catalog
  -|
   |GA
   |GA
   
   |Template Service Broker
  -|
   |GA
   |GA
   
   |OpenShift Ansible Service Broker
  -|
   |GA
   |GA
   
   |Network Policy
  -|
   |GA
   |GA
   
   |Multus
  -|
   |-
   |GA
   
   |Service Catalog Initial Experience
  -|
   |GA
   |GA
   
   |New Add Project Flow
  -|
   |GA
   |GA
   
   |Search Catalog
  -|
   |GA
   |GA
   
   |Cron Jobs
  -|
   |GA
   |GA
   
   |Kubernetes Deployments
  -|
   |GA
   |GA
   
   |StatefulSets
  -|
   |GA
   |GA
   
   |Explicit Quota
  -|
   |GA
   |GA
   
   |Mount Options
  -|
   |GA
   |GA
   
   |System Containers for Docker, CRI-O
  -|
   |-
   |-
   
   |Hawkular Agent
  -|
   |-
   |-
   
   |Pod PreSets
  -|
   |-
   |-
   
   |experimental-qos-reserved
  -|
   |TP
   |TP
   
   |Pod sysctls
  -|
   |GA
   |GA. See xref:ocp-4-1-known-issues[Known issues] for current limitations.
   
   |Central Audit
  -|
   |GA
   |GA
   
   |Static IPs for External Project Traffic
  -|
   |GA
   |GA
   
   |Template Completion Detection
  -|
   |GA
   |GA
   
   |`replicaSet`
  -|
   |GA
   |GA
   
   |Fluentd Mux
  -|
   |TP
   |TP
   
   |Clustered MongoDB Template
  -|
   |-
   |-
   
   |Clustered MySQL Template
  -|
   |-
   |-
   
   |Image Streams with Kubernetes Resources
  -|
   |GA
   |GA
   
   |Device Manager
  -|
   |GA
   |GA
   
   |Persistent Volume Resize
  -|
   |GA
   |GA
   
   |Huge Pages
  -|
   |GA
   |GA
   
   |CPU Pinning
  -|
   |GA
   |GA
   
   |Admission Webhooks
  -|
   |TP
   |GA
   
   |External provisoner for AWS EFS
  -|
   |TP
   |TP
   
   |Pod Unidler
  -|
   |TP
   |TP
   
   |Node Problem Detector
  -|
   |TP
   |TP
   
   |Ephemeral Storage Limit/Requests
  -|
   |TP
   |TP
   
   |Descheduler
  -|
   |TP
   |TP
   
   |CephFS
  -|
   |TP
   |TP
   
   |Podman
  -|
   |TP
   |TP
   
   |Kuryr CNI Plug-in
  -|
   |TP
   |TP
   
   |Istio
  -|
   |TP
   |TP
   
   |Sharing Control of the PID Namespace
  -|
   |TP
   |TP
   
   |Manila Provisioner
  -|
   |TP
   |TP
   
   |Cluster Administrator console
  -|
   |GA
   |GA
   
   |Cluster Autoscaling (AWS Only)
  -|
   |GA
   |GA
   
   |Container Storage Interface (CSI)
  -|
   |TP
   |TP
   
   |Operator Lifecycle Manager
  -|
   |TP
   |GA
   
   |Red Hat OpenShift Service Mesh
  -|
   |TP
   |TP
   
   |"Fully Automatic" Egress IPs
  -|
   |GA
   |GA
   
   |Pod Priority and Preemption
  -|
   |GA
   |GA
   
   |Multi-stage builds in Dockerfiles
  -|
   |TP
   |GA
   
   |OVN
   |
  -|
   |TP
   
   |HPA custom metrics adapter based on Prometheus
   |
  -|
   |TP
   
   |Machine health checks
  -|
   |
   |TP
   |====
  
positive.code: xref:../updating/updating-cluster.adoc#updating-cluster[updating your cluster]
  properly.
  ====
  
negative.code: `deleting` status.
  (link:https://bugzilla.redhat.com/show_bug.cgi?id=1713061[*BZ#1713061*])
  
  * Querying `Jolokia` on `JBoss EAP` images fails as the result of empty
  certificates presented to the client. The `Jolokia` SSL client authentication
  will fail and may require a username and password challenge if enabled.
  (link:https://bugzilla.redhat.com/show_bug.cgi?id=1708640[*BZ#1708640*])
  
  * The `TokenRequest` API is not available in {product-title} 4.1. Requesting a
  `ServiceAccountTokenVolumeProjection` volume is not available in {product-title}
  4.1. The kubelet will present an error if a
  `ServiceAccountTokenVolumeProjection` is used.
  (link:https://bugzilla.redhat.com/show_bug.cgi?id=1695196[*BZ#1695196*])
  
  * The `es nodeCount` in ElasticSearch CRD instances can not be scaled up if
  deployed with three nodes. Scaling works correctly if deployed with one, two,
  four, five or six ElasticSearch CRD instances.
  (link:https://bugzilla.redhat.com/show_bug.cgi?id=1712955[*BZ#1712955*])
  
  * ElasticSearch instances created from OperatorHub deploy with a one CPU limit,
  even though no limits are specified.
  (link:https://bugzilla.redhat.com/show_bug.cgi?id=1710657[*BZ#1710657*])
  
  * After an AWS installation, the `openshiftClustID` tag is not present.
  (link:https://bugzilla.redhat.com/show_bug.cgi?id=1685089[*BZ#1685089*])
  
  * scc(CRD) resources can not be upgraded by using the `oc patch` and `oc edit`
  commands. As a result, strategic merges also fail.
  (link:https://bugzilla.redhat.com/show_bug.cgi?id=1707679[*BZ#1707679*])
  
  * The {product-title} 4.1 registry service utilizes port 5000 instead of port 443.
  (link:https://bugzilla.redhat.com/show_bug.cgi?id=1701422[*BZ#1701422*])
  
  * Machineset scaling in AWS environments may fail if the resources requested are
  unavailable in the chosen Availability Zone.
  (link:https://bugzilla.redhat.com/show_bug.cgi?id=1713157[*BZ#1713157*])
  
  * Using `OAuth` endpoints after configuring ingress wildcard certificates from
  custom PKIs result in login errors.
  (link:https://bugzilla.redhat.com/show_bug.cgi?id=1712525[*BZ#1712525*])
  
  * Source-to-Image (S2I) builds in {product-title} 4.1 may take longer to complete.
  This is because {product-title} 4.1 does not utilize a shared image cache for
  building images like in previous versions of {product-title}.
  (link:https://bugzilla.redhat.com/show_bug.cgi?id=1685352[*BZ#1685352*])
  
  * The `cloud-credential-operator` may crash on clusters with large numbers of
  projects or namespaces due to memory limitations.
  (link:https://bugzilla.redhat.com/show_bug.cgi?id=1711402[*BZ#1711402*])
  
  * The Marketplace can not detect `opsrc` after a cluster upgrade is performed. As
  a result, the `csc` packages are empty and can not download `packagemanifests`.
  Marketplace can repair this problem approximately one hour later when it syncs
  again.
  (link:https://bugzilla.redhat.com/show_bug.cgi?id=1695550[*BZ#1695550*])
  
  * In {product-title} 4.1, `oc` and `openshift-install` version may have a dirty
  `GitTreeState:` when checking the `oc version`.
  (link:https://bugzilla.redhat.com/show_bug.cgi?id=1715001[*BZ#1715001*])
  
  * In AWS environments, if a master node is stopped, the `kubeapiserver` cannot be
  deployed due a pod stuck in a `Pending` status.
  (link:https://bugzilla.redhat.com/show_bug.cgi?id=1713292[*BZ#1713292*])
  
  * AWS IPI and UPI instances fail to verify
  (https://access.redhat.com/security/cve/cve-2019-11091[*CVE-2019-1109*]) using
  Broadwell CPU model 79 (type m4) because the `microcode_ctl` will not update.
  (link:https://bugzilla.redhat.com/show_bug.cgi?id=1710981[*BZ#1710981*])
  
  * New ElasticSearch deployments can not be created if another ElasticSearch
  deployment is stuck in a deleting state.
  (link:https://bugzilla.redhat.com/show_bug.cgi?id=1711044[*BZ#1711044*])
  
  * There is no _Open Java Console_ link available in the {product-title} 4.1 web
  console.
  (link:https://bugzilla.redhat.com/show_bug.cgi?id=1713656[*BZ#1713656*])
  
  * The `openshift-cluster-node-tuning-operator` may generate a large number of
  secrets after several days of uptime.
  (link:https://bugzilla.redhat.com/show_bug.cgi?id=1714484[*BZ#1714484*])
  
  * Autoscaling for Memory Utilization is not working as expected. Creating HPA for
  memory-based autoscaling is failing while looking for resources.
  (link:https://bugzilla.redhat.com/show_bug.cgi?id=1707785[*BZ#1707785*])
  
  * After successfully performing updates, `oc clusterversion` may report that the
  update could not be applied.
  (link:https://bugzilla.redhat.com/show_bug.cgi?id=1711964[*BZ#1711964*])
  
  * The installer may have a `0` return code when hitting a FATAL event.
  (link:https://bugzilla.redhat.com/show_bug.cgi?id=1712409[*BZ#1712409*])
  
  [id="ocp-4-1-asynchronous-errata-updates"]
  == Asynchronous errata updates
  
  