1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/modules/ossm-adding-project-using-smm-resource-cli.adoc
2024-03-28 19:11:43 +00:00

83 lines
2.3 KiB
Plaintext

// Module included in the following assemblies:
//
// * service_mesh/v2x/ossm-create-mesh.adoc
:_mod-docs-content-type: PROCEDURE
[id="ossm-adding-project-using-smm-resource-cli_{context}"]
= Adding a project to the mesh using the ServiceMeshMember resource with the CLI
You can add one or more projects to the mesh using the `ServiceMeshMember` resource with the CLI.
.Prerequisites
* You have installed the {SMProductName} Operator.
* You know the name of the `ServiceMeshControlPlane` resource and the name of the project it belongs to.
* You know the name of the project you want to add to the mesh.
* A service mesh administrator must explicitly grant access to the service mesh. Administrators can grant users permissions to access the mesh by assigning them the `mesh-user` `Role` using a `RoleBinding` or `ClusterRoleBinding`. For more information, see _Creating the {SMProductName} members_.
.Procedure
. Log in to the {product-title} CLI.
. Create the YAML file for the `ServiceMeshMember` manifest. The manifest adds the `my-application` project to the service mesh that was created by the `ServiceMeshControlPlane` resource deployed in the `istio-system` namespace:
+
[source,yaml]
----
apiVersion: maistra.io/v1
kind: ServiceMeshMember
metadata:
name: default
namespace: my-application
spec:
controlPlaneRef:
namespace: istio-system
name: basic
----
. Apply the YAML file to create the `ServiceMeshMember` resource:
+
[source,terminal]
----
$ oc apply -f <file-name>
----
.Verification
* Verify that the namespace is part of the mesh by running the following command. Confirm the that the value `True` appears in the `READY` column.
+
[source,terminal]
----
$ oc get smm default -n my-application
----
+
.Example output
[source,terminal]
----
NAME CONTROL PLANE READY AGE
default istio-system/basic True 2m11s
----
* Alternatively, view the `ServiceMeshMemberRoll` resource to confirm that the `my-application` namespace is displayed in the `status.members` and `status.configuredMembers` fields of the `ServiceMeshMemberRoll` resource.
+
[source,terminal]
----
$ oc describe smmr default -n istio-system
----
+
.Example output
[source,terminal]
----
Name: default
Namespace: istio-system
Labels: <none>
# ...
Status:
# ...
Configured Members:
default
my-application
# ...
Members:
default
my-application
----