openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-06 06:46:26 +01:00
Code Issues Releases Activity

Merge pull request #27289 from openshift-cherrypick-robot/cherry-pick-27236-to-enterprise-4.7

Browse Source 
[enterprise-4.7] OSSMDOC-157
This commit is contained in:
J Stickler
2020-11-11 16:09:43 -05:00
committed by GitHub
parent 307d73bda4 6cb3347876
commit 4e69550c49
2 changed files with 41 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
modules/ossm-rn-fixed-issues.adoc
View File

@@ -19,6 +19,8 @@ The following issues been resolved in the current release:
[id="ossm-rn-fixed-issues-ossm_{context}"]
== {ProductShortName} fixed issues
* link:https://issues.redhat.com/browse/MAISTRA-1983[MAISTRA-1983] Upgrading to 2.0.0 with an existing invalid `ServiceMeshControlPlane` cannot easily be repaired. The invalid items in the `ServiceMeshControlPlane` resource caused an unrecoverable error. The fix makes the errors recoverable. You can delete the invalid resource and replace it with a new one or edit the resource to fix the errors. For more information about editing your resource, see [Configuring the Red Hat OpenShift Service Mesh installation].
* link:https://issues.redhat.com/browse/MAISTRA-1502[Maistra-1502] As a result of CVEs fixes in version 1.0.10, the Istio dashboards are not available from the *Home Dashboard* menu in Grafana. The Istio dashboards still exist. To access them, click the *Dashboard* menu in the navigation panel and select the *Manage* tab.
* link:https://bugzilla.redhat.com/show_bug.cgi?id=1821432[Bug 1821432] Toggle controls in {product-title} Control Resource details page do not update the CR correctly. UI Toggle controls in the Service Mesh Control Plane (SMCP) Overview page in the {product-title} web console sometimes update the wrong field in the resource. To update a SMCP, edit the YAML content directly or update the resource from the command line instead of clicking the toggle controls.

42
service_mesh/v2x/upgrading-ossm.adoc
View File

@@ -4,7 +4,7 @@ include::modules/ossm-document-attributes.adoc[]
:context: upgrading-ossm
toc::[]
To access the most current features of {ProductName}, upgrade to the most current version, 2.0. Upgrading from version 1.1 to 2.0 requires manual steps that migrate your workloads and apps to a new instance of {ProductName} running the new version.
To access the most current features of {ProductName}, upgrade to the current version, 2.0. Upgrading from version 1.1 to 2.0 requires manual steps that migrate your workloads and apps to a new instance of {ProductName} running the new version.
.Prerequisites
@@ -14,15 +14,51 @@ To access the most current features of {ProductName}, upgrade to the most curren
[id="ossm-upgrading-upgrade_{context}"]
== Upgrading {ProductName}
To upgrade {ProductName}, you must create an instance of {ProductName} 2.0 in a new namespace. Then, once it's configured, move your microservice applications and workloads from your old mesh to the new service mesh.
To upgrade {ProductName}, you must create an instance of {ProductName} `ServiceMeshControlPlane` v2 resource in a new namespace. Then, once it's configured, move your microservice applications and workloads from your old mesh to the new service mesh.
.Procedure
. Check your v1 `ServiceMeshControlPlane` resource configuration to make sure it is valid.
+
.. Run the following command to view your `ServiceMeshControlPlane` resource as a v2 resource.
+
[source,terminal]
----
$ oc get smcp -o yaml
----
+
.. Check the `spec.techPreview.errored.message` field in the output for information about any invalid fields.
+
.. If there are invalid fields in your v1 resource, the resource is not reconciled and cannot be edited as a v2 resource. All updates to v2 fields will be overridden by the original v1 settings. To fix the invalid fields, you can replace, patch, or edit the v1 version of the resource. You can also delete the resource without fixing it. After the resource has been fixed, it can be reconciled, and you can to modify or view the v2 version of the resource.
+
.. To fix the resource by editing a file, use `oc get` to retrieve the resource, edit the text file locally, and replace the resource with the file you edited.
+
[source,terminal]
----
$ oc get smcp.v1.maistra.io <smcp_name> > smcp-resource.yaml
#Edit the smcp-resource.yaml file.
$ oc replace -f smcp-resource.yaml
----
+
.. To fix the resource using patching, use `oc patch`.
+
[source,terminal]
----
$ oc patch smcp.v1.maistra.io <smcp_name> --type json --patch '[{"op": "replace","path":"/spec/path/to/bad/setting","value":"corrected-value"}]'
----
+
.. To fix the resource by editing with command line tools, use `oc edit`.
+
[source,terminal]
----
$ oc edit smcp.v1.maistra.io <smcp_name>
----
+
. Back up your control plane configuration. Switch to the project that contains your `ServiceMeshControlPlane` resource.
+
[source,terminal]
----
oc project istio-system
$ oc project istio-system
----
+
. Enter the following command to retrieve the current configuration. Your <smcp_name> is specified in the metadata of your `ServiceMeshControlPlane` resource, for example `basic-install` or `full-install`.