1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 21:46:22 +01:00

latest release notes additions, Jan 20 2020

fixed typo

peer review corrections added
This commit is contained in:
Andrew Taylor
2020-01-20 14:15:00 -05:00
parent 61beaf5669
commit ee0735705e

View File

@@ -520,7 +520,7 @@ The following related APIs will be removed in a future release:
* `.osb.openshift.io/v1`
[id="ocp-4-3-virtualbox-for-crc"]
=== VirtualBox support for CodeReady Containers
==== VirtualBox support for CodeReady Containers
The support for using VirtualBox with CodeReady Containers (CRC) is now
deprecated.
@@ -656,6 +656,13 @@ Podman containers on CRI-O restore so that they are no longer deleted from
storage upon startup.
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1758500[*BZ#1758500*])
*Developer Console*
* An invalid property was introduced into the Pipeline Operator during an upgrade.
As a result, Pipelines could no longer start from the UI. The property is now
updated to use a valid specification. As a result, Pipelines start from the UI
again. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1763725[*BZ#1763725*])
*Etcd*
* Etcd would become overloaded with a large number of objects, causing the
@@ -727,7 +734,38 @@ unable to do so. The KCM can now recreate the lease ConfigMap if it is deleted.
*Logging*
* Mismatches between cluster version and ClusterLogging version would cause
ClusterLogging to faile to deploy. Now, the kubeversion is verified that it
supports the deployed ClusterLogging version.
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1765261[*BZ#1765261*])
* The data in journald for facility values wass not sanitized and values were
incorrect, causing fluentd to emit error messages at the wrong level. Now,
fluentd logs at the debug level and these errors are reported correctly.
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1753936[*BZ#1753936*],link:https://bugzilla.redhat.com/show_bug.cgi?id=1766187[*BZ#1766187*])
* The oauth-proxy was misconfigured in a way that users were unable to log in
after logging out. Now, the oauth-proxy has been reconfigured so that users can
log in again after logging out.
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1725517[*BZ#1725517*])
* Eventroute was not able to handle unknown event types, which would result in
Eventrouter crashing. Now, Eventrouter properly handles unknown event types.
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1753568*[BZ#1753568*])
*Management Console*
* The Management Console Dashboard Details were unnecessarily watching the
Infrastructure resources. As a result, errors regarding early web socket
connection terminations were possible. Now, the Details card does not watch
Infrastructure resources and only fetches the resource data once. Errors are not
reported after implementing this fix.
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1765083[*BZ#1765083*])
* The console Operator would record an initial empty string value for the console
URL before the router had a chance to provide the host name. Now, the Operator
waits until the hostname is filled and eliminates the empty string value.
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1768684[*BZ#1768684*])
*Metering Operator*
@@ -758,6 +796,39 @@ objects are cleaned up properly.
are no longer dropped.
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1747532[*BZ#1747532*])
* Previously, in clusters that had high network traffic volumes with packet loss,
a once-successful connection to a service could fail with a *Connection reset by
peer* error. As a result, clients had to reconnect and retransmit. An update has
been made to iptables rules to process TCP retransmits correctly. Established
connections will remain open until they are closed.
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1762298[*BZ#1762298*])
* Previously, NetworkPolicy rule applications to new namespaces could occur slowly
in clusters that had many namespaces, namespace changes, and NetworkPolicies
that select namespaces. New namespaces could take significant amounts of time
before they could be accessed from other namespaces. Due to an update in
Namespace and NetworkPolicy code, NetworkPolicies should be applied promptly to
new namespaces.
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1752636[*BZ#1752636*])
* Previously, SDN pods did not clean up Egress IP addresses when they restarted on
a node, resulting in IP address conflicts. SDN pods now clean up stale Egress IP
addresses as they start, preventing such conflicts from occuring. (link:
https://bugzilla.redhat.com/show_bug.cgi?id=1753216[*BZ#1753216*])
* Previously, DNS names were queried every time they occured in an
EgressNetworkPolicy. Records were queried regardless of whether a particular DNS
record had been refreshed by a previous query, resulting in slow network
performance. DNS records are now queried based on unique names rather than per
each EgressNetworkPolicy. As a result, DNS query performance has been
significantly improved.
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1684079[*BZ#1684079*])
* Route creation between multiple service endpoints was not possible from the
console. Now, the GUI has been updated to add or remote up to three alternative
service endpoints.
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1725006[*BZ#1725006*])
*Node*
* Previously, when containers had a high (or > 1) restart count, the kubelet
@@ -768,6 +839,18 @@ result, the `/metrics` endpoint now allows metrics to flow to Prometheus without
causing a 500 error.
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1779285[*BZ#1779285*])
* Upstream changes were made to the long path names test. Pods with names longer
than 255 character were not logged and no warning was issued. Now, the long
names test is removed and Pods with names longer than 255 characters will
log as expected.
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1711544[*BZ#1711544*])
* The `LocalStorageCapacityIsolation` feature was disabled, and users were unable
to the `Statefulset.emptyDir.sizeLimit` parameter. Now, the
`LocalStorageCapacityIsolation` feature has been enabled and the
`Statefulset.emptDir.sizeLimit` parameter can be set.
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1758434[*BZ#1758434*])
*oc*
* Previously when using server-side print, the wide output option was ignored