Oracle Cloud Infrastructure Documentation

Moving an Ingress Gateway Between Compartments

Move an ingress gateway from one compartment to another in Service Mesh.

After you move an ingress gateway to a new compartment, inherent policies apply immediately, and affect access to the ingress gateway through the Console. For more information, see Managing Compartments.

Important

Before you proceed, you must set up the appropriate OCI policies for the ingress gateway resource. For details, see Required IAM Policy for Ingress Gateways.
    1. Open the navigation menu and click Developer Services. Under Containers & Artifacts, click Service Mesh.
    2. Click Service Meshes.
    3. On the Service Mesh page, from the list of compartments on the left side, select a compartment.
    4. From the list of meshes, click the mesh name, which contains the ingress gateway that you want to move.
    5. On the details page of the mesh, under Resources, click Ingress Gateways.
    6. In the Ingress Gateways table, click the ingress gateway that you want to move.
    7. On the details page of the ingress gateway, click Move resource.
    8. In the Move resource dialog box, select the destination compartment.
    9. Click Move resource.

  • To see what operations are available for ingress-gateway change-compartment use:

    oci service-mesh ingress-gateway change-compartment -h

    Run ingress-gateway change-compartment to move an ingress gateway from one compartment to another:

    oci service-mesh ingress-gateway change-compartment --ingress-gateway-id <ingressGatewayId> --compartment-id <compartmentId>

    where:

    • <compartmentId>: The OCID of the compartment to which to move the ingress gateway.
    • <ingressGatewayId>: The OCID of the ingress gateway to move. To find out the Ingress Gateway's OCID, see Listing Ingress Gateways.

    For example:

    oci service-mesh ingress-gateway change-compartment --ingress-gateway-id ocid.meshingressgateway.oc1.iad.aaaa.... --compartment-id ocid.compartment.oc1.iad.aaaa....

    The response to the command includes:

    • The life cycle state (for example, ACTIVE, FAILED).
    • The ID of the work request to move the ingress gateway (details of work requests are available for seven days after completion, cancellation, or failure).

    If you want the command to wait to return control until the ingress gateway is active (or the request has failed), include either or both the following parameters:

    • --wait-for-state SUCCEEDED
    • --wait-for-state FAILED

    For example:

    oci service-mesh ingress-gateway change-compartment --ingress-gateway-id ocid.meshingressgateway.oc1.iad.aaaa.... --compartment-id ocid.compartment.oc1.iad.aaaa.... --wait-for-state SUCCEEDED
    Important

    You cannot use the ingress gateway until the work request has successfully moved it and the ingress gateway is active.

    Checking Ingress Gateway Status

    To see the status of the ingress gateway, enter:

    oci service-mesh ingress-gateway get --ingress-gateway-id <ingressGatewayId>

    To view the status of the work request updating the ingress gateway, refer to Service Mesh Work Requests.

    For more information about using the CLI, see:

  • Use the ChangeAccessPolicyCompartment operation to move an ingress gateway.