Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added OCP 3.11 release notes #11905

Merged
merged 1 commit into from
Sep 17, 2018
Merged

Conversation

ahardin-rh
Copy link
Contributor

FYI @tmorriso-rh

@ahardin-rh ahardin-rh added this to the Future Release milestone Sep 4, 2018
@ahardin-rh ahardin-rh self-assigned this Sep 4, 2018
@openshift-ci-robot openshift-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Sep 4, 2018
@openshift-ci-robot openshift-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Sep 4, 2018
@openshift-ci-robot openshift-ci-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Sep 4, 2018
@vikram-redhat
Copy link
Contributor

@ahardin-rh - can you push to this again (even a small commit) to see if it triggers a fix.

@ahardin-rh
Copy link
Contributor Author

@vikram-redhat Looks like it's fixed. Thanks!

users can automatically authenticate to {product-title} by using the `oc` command
line interface from a domain-joined Windows computer.

See xref:../install_config/configuring_authentication.adoc#GitHub[Configuring
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note to self: update this to be windows-sspi-using-request-header when the docs merge

@bparees
Copy link
Contributor

bparees commented Sep 10, 2018

I would expect to see something about using the new terms based registry (registry.redhat.io) and the auth requirements.

/cc @bmcelvee

@bmcelvee
Copy link
Contributor

Thanks, @bparees. Yes, I will help get that content drafted and added. (fyi - @ahardin-rh 🍃 )

@openshift openshift deleted a comment from openshift-docs-bot Sep 10, 2018
@openshift openshift deleted a comment from openshift-docs-bot Sep 10, 2018
@openshift openshift deleted a comment from openshift-docs-bot Sep 10, 2018
|-
|-
|TP

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the Operator-SDK feature is TP for 3.11, but I could not find it. Document feature card: https://trello.com/c/rU4yP8Cu/1229-formal-documentation-for-operator-sdk.

@gpei
Copy link

gpei commented Sep 11, 2018

hi, better to add an explain about the new default registry(registry.redhat.io) in ocp-3.11, used to replace the previous one(registry.access.redhat.com), and the new registry will require authentication


You can deploy Prometheus on an {product-title} cluster, collect Kubernetes and
infrastructure metrics, and get alerts. You can see and query metrics and alerts
on the Prometheus web dashboard. Alternatively, you can bring your own Grafana
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a pre-configured Grafana out of the box. Bring your own Grafana is currently not supported in this setup.

@sichvoge can you please clarify this with the other cluster-monitoring entry in here?


See
xref:../install/configuring_inventory_file.adoc#install-config-configuring-inventory-file[Configuring
Your Inventory File] for details on configuring the admin console.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Didn't see ansible variables for admin console listed in Configuring Your Inventory File

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yapei These are introduced in #11922

your pods and that the number of active nodes is proportional to
current demand.

See [Configuring the cluster auto-scaler in AWS] for more information.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Configuring the cluster auto-scaler in AWS" no hyperlinks

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The doc hasn't been merged yet. It'll be at admin_guide/cluster-autoscaler.adoc.

@jwforres
Copy link
Member

@ahardin-rh there should be a deprecation note for the registry console and the standalone registry install path

== Configuring the Admin Console

[IMPORTANT]
====
The Admin Console is currently a Technology Preview feature only.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The admin console is not tech preview afaik. It's fully supported.

@jwforres @robszumski can you confirm?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not aware of a reason it would need to be considered tech preview, but I'll leave that to PM to make the call.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@spadgett @jwforres I see in the tech preview tracker spreadsheet from PM, that it's defined as GA, so I will update that. Thanks!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, correct, it's GA

|-
|-

|xref:../install/running_install.adoc#running-the-advanced-installation-system-container[System Container for installer and Kubelet]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just made a change here: s/System Container for installer and Kubelet/Installing from a system container


|xref:../install/running_install.adoc#running-the-advanced-installation-system-container[System Container for installer and Kubelet]
|GA
|Dropped
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/Dropped/GA

To upgrade to this release from a previous version, see the
xref:../upgrading/index.adoc#install-config-upgrading-index[Upgrading Clusters]
documentation.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we adding a note that 3.11 will be the last release in the 3.x stream and that large changes to the underlying architecture and installation process are coming in 4.0?

We're deprecating the blue/green install method in 4.0, and I'd like to announce that along with whatever we're saying for 4.0.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kalexand-rh Noted it in there now. Thanks!

perform new tasks.

See xref:../cli_reference/extend_cli.adoc#cli-reference-extend-cli[Extending the
CLI] for information on how to install and write extensions for the CLI.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CLI plug-ins feature was implemented since >= v3.7. It is by design to add it explicitly in v3.11 release notes?

env` and `oc set volume` instead.

[discrete]
[[ocp-311-oc-exec-config-patch-command-removed]]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ocp-311-oc-exec-...

Not oc-exec. oc exec (execute) differs from oc ex (experimental)

==== Removed the oc ex config patch Command

The `oc ex config patch` command will be removed in a future release, as it is
replaced by the `oc patch` command.
Copy link
Contributor

@xingxingxia xingxingxia Sep 17, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

==== Removed the oc ex config patch Command

1 Now that it is in a future release, the wording should not be "Removed the oc ex config patch Command". Maybe deprecated? But you need confirm 2:
2 I tested in latest v3.11.6, no warning indicates it will be removed in a future release. Where did you get this info?
3

as it is replaced by the oc patch command

oc patch does not have the function of oc ex config patch. oc patch patches openshift resources, oc ex config patch patches standalone yaml/json files

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

==== Removed oc env and oc volume Commands

The deprecated `oc env` and `oc volume` commands are now removed. Use `oc set
env` and `oc set volume` instead.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For oc deploy, oc env, oc volume, need search all doc files if other places reference them and update them in a separate PR. This is to avoid they're still seen in other pages while 3.11 doc is announced.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. This was done in #11449

@ahardin-rh ahardin-rh force-pushed the 311-release-notes branch 3 times, most recently from d94ac6f to 1f6078c Compare September 17, 2018 19:27
@openshift openshift deleted a comment from openshift-docs-bot Sep 17, 2018
@openshift openshift deleted a comment from openshift-docs-bot Sep 17, 2018
@openshift openshift deleted a comment from openshift-docs-bot Sep 17, 2018
@openshift-docs-preview-bot

The preview will be availble shortly at:

@ahardin-rh ahardin-rh changed the title [WIP]Added OCP 3.11 release notes Added OCP 3.11 release notes Sep 17, 2018
@openshift-ci-robot openshift-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 17, 2018
@ahardin-rh
Copy link
Contributor Author

@openshift/team-documentation I am merging this so that we can all continue to build out details together 🏗️

@ahardin-rh ahardin-rh merged commit 7c0fa11 into openshift:master Sep 17, 2018
@ahardin-rh
Copy link
Contributor Author

/cherrypick enterprise-3.11

@jianlinliu
Copy link

In 3.11 Cluster Monitoring Operator install is enabled by default, according to Bug 1625114, we should mention it to make sure there is available node in user's cluster to avoid unexpected failure.

@ahardin-rh
Copy link
Contributor Author

@jianlinliu Thank you. I included those details in #12182.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch/enterprise-3.11 size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.