OCP 3.4 Release Notes #3486
OCP 3.4 Release Notes #3486
Conversation
adellape
force-pushed
the
34relnotes
branch
2 times, most recently
from
b603a34 to
6052d35
Compare
|
@openshift/team-documentation There are still some loose ends I need to follow up on, but this first draft is basically done and could get some peer review from anyone able: http://file.rdu.redhat.com/~adellape/011217/34relnotes/release_notes/ocp_3_4_release_notes.html |
|
Thanks @adellape . @bfallonf @gaurav-nelson @ahardin-rh @bmcelvee - PTAL. |
|
@aheslin - PTAL. |
|
|
||
| Users can now use wildcard routes where all traffic destined to, for example, | ||
| `*.foo.com` is routed to the same back-end service, configured to handle all the | ||
| subdomains. You can specify that a route allows wildcard support through an |
There was a problem hiding this comment.
@adellape I don't understand the sentence above. Is there a word missing? Should the bits after "for example" be their own sentence? Where does the "configured to..." section fit? So maybe:
"Users can now use wildcard routes to determine the location of all traffic. For example, *.foo.com is now routed to the same back-end service, which is configured to handle all subdomains."
?
There was a problem hiding this comment.
+1. Rewritten to:
"Users can now use wildcard routes to determine the destination of all traffic
for a domain and its subdomains. For example, *.foo.com is routed to the same
back-end service, which is configured to handle all the subdomains."
|
|
||
| Users working within quota constraints had a hard time knowing when they had run | ||
| out of quota, unless they went to check the *Quota* page. To address this, | ||
| checks hav ebeen added for the most common scenarios where people have problems |
|
|
||
| * This bug fix updates the web console to add an image change trigger with `automatic: false`. This prevents deployments from happening automatically when the image stream tag is updated, but allows users to run `oc rollout` commands, or use the *Deploy* action in the web console, without any additional configuration. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1383804[*BZ#1383804*]) | ||
|
|
||
| * It was impossible to specify when to start a deployment with the latest image. Triggers would cause each build to deploy. So triggers had to be disabled, then enabled once a deploy is desired. With this bug fix, a new endpoint and `oc rollout latest` that uses the endpoint and supersedes `oc deploy --latest` were added in OpenShift Container Platform 3.4 to enable manual deployments without the need to enable triggers. (BZ#1303938) |
There was a problem hiding this comment.
| * The *a-o-i* package was considering extra hosts when determining if the target HA environment is a mix of installed and uninstalled hosts. As a result, the comparison failed and incorrectly reported that a fully installed environment was actually a mix of installed and uninstalled. With this fix, non-masters and non-nodes were removed from the comparison and installed HA environments are correctly detected. | ||
| (link:https://bugzilla.redhat.com/show_bug.cgi?id=1390064[*BZ#1390064*]) | ||
|
|
||
| * Previously, the dnsmasq configuration included `strict-order`, meaning that dnsmasq would iterate through the host's nameservers in order. This meant that if the first nameserver had failed, a lengthy timeout would be observed while dnsmasq waited before moving on to the next nameserver. By removing the `strict-order` option, dnsmasq prefers nameservers that it knows to be up over those that are unresponsive, ensuring faster name resolution. If you wish add this or any other option, use the advanced installer option `openshift_node_dnsmasq_additional_config_file`, which allows you to provide the path to a dnsmasq configuration file that will be deployed on all nodes. |
There was a problem hiding this comment.
s/if you wish add this/If you wish to add this
And a double space inbetween "openshift_node_dnsmasq_additional_config_file, which"
| * Previously, you could select *Push Secret* and *Pull Secret* on the DC editor page and on the *Create From Image* page. These options are not helpful on these pages because they are using integrated registry. Therefore, the *Push Secret* and *Pull Secret* select boxes are now removed from the DC editor and *Create From Image* pages and users can no longer select these options. | ||
| (link:https://bugzilla.redhat.com/show_bug.cgi?id=1388884[*BZ#1388884*]) | ||
|
|
||
| * Routes popover warning messages were being truncated at the end of the string. Before the relevant portion of the warning message could be displayed, the certificate content results in the warning message were being truncated. After the bug fix, the truncation of the warning message was changed from truncating at the end of the string to truncating in the middle of the string. As a result, the relevant portion of the warning message is now visible. (BZ#1389658) |
There was a problem hiding this comment.
Seems like here down doesn't have BZ links?
There was a problem hiding this comment.
Yeah, this chunk got added last and I didn't make em fancy links yet. Doing so now.
|
|
||
| * The password field was set as type *text*, and therefore the password was visible. In this bug fix, the password field type was set to *password*. As a result, the password is not visible. (BZ#1393290) | ||
|
|
||
| * Previously, the `BuildConfig` editor displayed a blank section. The `BuildConfig`editor now shows a message when there are no editable source types for a `BuildConfig`. (BZ#1393803) |
There was a problem hiding this comment.
There's a markup mismatch here somewhere. I think the missing space after the second BuildConfig is breaking it?
| *Upgrade* | ||
|
|
||
| * Previously the upgrade playbook would in inadvertently upgrade etcd when it should not have. If this upgrade triggered an upgrade to etcd3 then the upgrade would fail as etcd would become unavailable. With this bug fix, etcd no longer updates when it is not necessary ensuring upgrades proceed successfully. (BZ#1393187) |
|
@adellape I made comments. LG otherwise. |
|
@bfallonf Thanks! Edits made/pushed. |
|
other devex items (maybe not worthy of mention? but they are new features): |
|
Spoke with @adellape on irc and he was happy with this to get merged. |
WIP preview:
http://file.rdu.redhat.com/~adellape/011217/34relnotes/release_notes/ocp_3_4_release_notes.html