Skip to content

Adds a few deprecated features and one new feature to authentication … #41535

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.

Sign up for GitHub

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

Merged
stevsmit merged 1 commit into from
Feb 8, 2022
Merged

Adds a few deprecated features and one new feature to authentication … #41535

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions release_notes/ocp-4-10-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -181,6 +181,7 @@ The `ovnkube_master_resource_update_total` metric is removed for the 4.10 releas
==== Enhancement to must-gather to simplify network tracing

The `oc adm must-gather` command is enhanced in a way that simplifies collecting network packet captures.

Previously, `oc adm must-gather` could start a single debug pod only.
With this enhancement, you can start a debug pod on multiple nodes at the same time.

Expand Down Expand Up @@ -276,6 +277,14 @@ In {product-title} 4.7, _Cluster Logging_ became _Red Hat OpenShift Logging_. Fo
[id="ocp-4-10-auth"]
=== Authentication and authorization

[id="ocp-4-10-oc-commands-obtain-credentials-from-podman-config"]
==== oc commands now obtain credentials from Podman configuration locations

Previously, `oc` commands that used the registry configuration, for example `oc login` or `oc image`, obtained credentials from Docker configuration locations. With {product-title} {product-version}, if a registry entry cannot be found in the default Docker configuration location, `oc` commands obtain the credentials from Podman configuration locations. You can set your preference to either `docker` or `podman` by using the `REGISTRY_AUTH_PREFERENCE` environment variable to prioritize the location.

Users also have the option to use the `REGISTRY_AUTH_FILE` environment variable, which serves as an alternative to the existing `--registry-config` CLI flag. The `REGISTRY_AUTH_FILE` environment variable is also compatible with `podman`.


[id="ocp-4-10-sandboxed-containers"]
=== {sandboxed-containers-first}

Expand Down Expand Up @@ -422,6 +431,15 @@ In the table, features are marked with the following statuses:
AMD and Intel 64-bit architectures (x86-64-v2) will still be supported.
====

[id="ocp-4-10-docker-config-location-deprecation"]
==== Default Docker configuration location deprecation
Previously, `oc` commands that used a registry configuration would obtain credentials from the Docker configuration location, which was `~/.docker/config.json` by default. This has been deprecated and will be replaced by a Podman configuration location in a future version of {product-title}.

[id="ocp-4-10-empty-file-support-deprecation"]
==== Empty file and stdout support deprecation in oc registry login

Support for empty files using the `--registry-config` and `--to` flags in `oc registry login` has been deprecated. Support for `-` (standard output) has also been deprecated as an argument when using `oc registry login`. They will be removed in a future version of {product-title}.

[id="ocp-4-10-removed-features"]
=== Removed features

Expand Down