Skip to content

[enterprise-4.13] MIG-1320 Issue in file migrating_from_ocp_3_to_4/premigration-checklists-3-4.adoc #62049

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
merged 1 commit into from
Jul 5, 2023
Merged

[enterprise-4.13] MIG-1320 Issue in file migrating_from_ocp_3_to_4/premigration-checklists-3-4.adoc #62049

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
2 changes: 1 addition & 1 deletion migrating_from_ocp_3_to_4/premigration-checklists-3-4.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,6 +66,7 @@ $ oc get csr -A | grep pending -i
----

* [ ] The link:https://docs.openshift.com/container-platform/3.11/install_config/configuring_authentication.html#overview[identity provider] is working.
* [ ] You have set the value of the `openshift.io/host.generated` annotation parameter to `true` for each {product-title} route, which updates the host name of the route for the target cluster. Otherwise, the migrated routes retain the source cluster host name.

[id="target-cluster_{context}"]
== Target cluster
Expand All @@ -88,7 +89,6 @@ If an application uses an internal image in the `openshift` namespace that is no
* [ ] The target cluster and the replication repository have sufficient storage space.
* [ ] The xref:../authentication/understanding-identity-provider.adoc#supported-identity-providers[identity provider] is working.
* [ ] DNS records for your application exist on the target cluster.
* [ ] Set the value of the `annotation.openshift.io/host.generated` parameter to `true` for each {product-title} route to update its host name for the target cluster. Otherwise, the migrated routes retain the source cluster host name.
* [ ] Certificates that your application uses exist on the target cluster.
* [ ] You have configured appropriate firewall rules on the target cluster.
* [ ] You have correctly configured load balancing on the target cluster.
Expand Down