You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 2, 2023. It is now read-only.
-[RBAC required for OCI Service Broker](docs/installation.md#rbac-required-for-oci-service-broker)
19
-
-[RBAC Permissions for registering OCI Service Broker and creating services](docs/installation.md#rbac-permissions-for-registering-service-broker-and-creating-services)
19
+
-[RBAC Permissions for registering OCI Service Broker](docs/installation.md#rbac-permissions-for-registering-oci-service-broker)
20
20
-[Register OCI Service Broker](docs/installation.md#register-oci-service-broker)
21
21
-[Monitoring OCI Service Broker](docs/installation.md#monitoring-oci-service-broker)
22
22
-[JMX](docs/installation.md#jmx)
23
-
-[Guidelines for Securing OCI Service Broker](docs/security.md#guidelines-for-securing-service-broker)
23
+
-[Guidelines for Securing OCI Service Broker](docs/security.md#guidelines-for-securing-oci-service-broker)
24
24
-[Restrict access to Service Catalog resources using RBAC](docs/security.md#restrict-access-to-service-catalog-resources-using-rbac)
-[Restrict access of the OCI User used by OCI Service Broker](docs/security.md#restrict-access-of-the-oci-user-used-by-service-broker)
28
+
-[Restrict access of the OCI User used by OCI Service Broker](docs/security.md#restrict-access-of-the-oci-user-used-by-oci-service-broker)
29
29
-[OCI User Capabilities](docs/security.md#oci-user-capabilities)
30
30
-[Policies to allow access to Services](docs/security.md#policies-to-allow-access-to-services)
31
31
-[Restrict the permissions only to the required Compartments](docs/security.md#restrict-the-permissions-only-to-the-required-compartments)
32
-
-[Limit access to OCI Service Broker endpoint using Networkpolicy](docs/security.md#limit-access-to-service-broker-endpoint-using-networkpolicy)
32
+
-[Limit access to OCI Service Broker endpoint using Networkpolicy](docs/security.md#limit-access-to-oci-service-broker-endpoint-using-networkpolicy)
33
33
-[Strategy 1-Allow access only for Service Catalog running in the same namespace](docs/security.md#strategy-1-allow-access-only-for-service-catalog-running-in-the-same-namespace)
34
34
-[Strategy 2-Allow access only for Service Catalog from any namespace](docs/security.md#strategy-2-allow-access-only-for-service-catalog-from-any-namespace)
35
35
-[Strategy 3-Allow access for any pods running in a certain namespace](docs/security.md#strategy-3-allow-access-for-any-pods-running-in-a-certain-namespace)
@@ -42,39 +42,39 @@
42
42
-[Plans](docs/object-storage.md#plans)
43
43
-[OCI User Permission requirement](docs/object-storage.md#oci-user-permission-requirement)
-[Creating a new ADW ServiceInstance](#creating-a-new-adw-serviceinstance)
17
-
-[Attaching an Existing ADW ServiceInstance](#attaching-an-existing-adw-serviceinstance)
16
+
-[Creating a new ADW Instance](#creating-a-new-adw-instance)
17
+
-[Using an Existing ADW Instance](#using-an-existing-adw-instance)
18
18
-[Get instance status](#get-instance-status)
19
19
-[Binding](#binding)
20
20
-[Creating an ADW ServiceBinding resource](#creating-an-adw-servicebinding-resource)
@@ -63,9 +63,9 @@ To provision, an ADW service user needs to provide the following details:
63
63
|`freeFormTags`| free form tags that are to be used for tagging the ADW instance. | object | no |
64
64
|`definedTags`| The defined tags that are to be used for tagging the ADW instance. | object | no |
65
65
66
-
## Attaching an Existing ADW Service Instance
66
+
## Using an Existing ADW Service Instance
67
67
68
-
For more information about binding to an existing ADW service instance, see [Attaching an Existing Service Instance](services.md#attaching-an-existing-service-instance).
68
+
For more information about binding to an existing ADW service instance, see [Using an Existing Service Instance](services.md#using-an-existing-service-instance).
69
69
70
70
To attach to an existing ADW service, the user needs to provide the following details. In this case, OCI Service broker will neither provision a new instance nor update/change the existing instance.
71
71
@@ -143,7 +143,7 @@ Providing password in plain text may not be an idle case. Alternatively, the use
143
143
144
144
Please refer [Use Secret to pass passwords](#use-secret-to-pass-passwords) section for passing the password from secrets.
145
145
146
-
#### Creating a new ADW ServiceInstance
146
+
#### Creating a new ADW Instance
147
147
148
148
**NOTE:**
149
149
The [`adw-instance-plain.yaml`](../samples/adw/adw-instance-plain.yaml) files contain the compartment OCID in which the user wants to provision the ADW instance. The user needs to update it with their compartment OCID.
@@ -152,7 +152,7 @@ The [`adw-instance-plain.yaml`](../samples/adw/adw-instance-plain.yaml) files co
The [`adw-existing-instance.yaml`](../samples/adw/adw-existing-instance.yaml) files contain the instance OCID and compartment OCID which the user wants to provision as existing ADW instance. The user needs to update it with their instance OCID and compartment OCID.
-[Creating an ATP ServiceInstance](#creating-a-new-atp-serviceinstance)
17
-
-[Attaching an Existing ATP ServiceInstance](#attaching-an-existing-atp-serviceinstance)
16
+
-[Creating an ATP Instance](#creating-a-new-atp-instance)
17
+
-[Using an Existing ATP Instance](#using-an-existing-atp-instance)
18
18
-[Get instance status](#get-instance-status)
19
19
-[Binding](#binding)
20
20
-[Creating an ATP ServiceBinding resource](#creating-an-atp-servicebinding-resource)
@@ -63,9 +63,9 @@ To provision, an ATP service user needs to provide the following details:
63
63
|`freeFormTags`| free form tags that are to be used for tagging the ATP instance. | object | no |
64
64
|`definedTags`| The defined tags that are to be used for tagging the ATP instance. | object | no |
65
65
66
-
## Attaching an Existing ATP Service Instance
66
+
## Using an Existing ATP Service Instance
67
67
68
-
For more information about binding to an existing ATP service instance, see [Attaching an Existing Service Instance](services.md#attaching-an-existing-service-instance).
68
+
For more information about binding to an existing ATP service instance, see [Using an Existing Service Instance](services.md#using-an-existing-service-instance).
69
69
70
70
To attach to an existing ATP service, the user needs to provide the following details. In this case, OCI Service broker will neither provision a new instance nor update/change the existing instance.
71
71
@@ -142,7 +142,7 @@ Providing password in plain text may not be an idle case. Alternatively, the use
142
142
143
143
Please refer [Use Secret to pass passwords](#use-secret-to-pass-passwords) section for passing the password from secrets.
144
144
145
-
#### Creating a New ATP ServiceInstance
145
+
#### Creating a New ATP Instance
146
146
147
147
**NOTE:**
148
148
The [`atp-instance-plain.yaml`](../samples/atp/atp-instance-plain.yaml) files contain the compartment OCID in which the user wants to provision the ATP instance. The user needs to update it with their compartment OCID.
@@ -151,7 +151,7 @@ The [`atp-instance-plain.yaml`](../samples/atp/atp-instance-plain.yaml) files c
The [`atp-existing-instance.yaml`](../samples/atp/atp-existing-instance.yaml) files contain the instance OCID and compartment OCID which the user wants to provision as existing ATP instance. The user needs to update it with their instance OCID and compartment OCID.
-[Provisioning a new Service Instance](#provisioning-a-new-service-instance)
8
-
-[Attaching an Existing Service Instance](#attaching-an-existing-service-instance)
9
-
-[Service Provision Request Parameters for Existing Instance](#service-provision-request-parameters-for-existing-service-instance)
7
+
-[Provisioning a new Object Storage Service Instance](#provisioning-a-new-object-storage-service-instance)
8
+
-[Using an Existing Object Storage Service Instance](#using-an-existing-object-storage-instance)
10
9
-[Service Binding](#service-binding)
11
10
-[Request Parameters](#request-parameters)
12
11
-[Response Credentials](#response-credentials)
13
12
-[Example](#example)
14
13
-[Kubernetes](#kubernetes)
15
-
-[Creating a New Instance](#creating-a-new-instance)
16
-
-[Attaching an Existing Instance](#attaching-an-existing-instance)
14
+
-[Creating a New Object Storage Instance](#creating-a-new-object-storage-instance)
15
+
-[Using an Existing Object Storage Instance](#using-an-existing-object-storage-instance)
17
16
-[Binding](#binding)
18
17
19
18
## Introduction
@@ -41,7 +40,7 @@ Allow group <SERVICE_BROKER_GROUP> to manage buckets in compartment <COMPARTMENT
41
40
42
41
### Service Provision Request Parameters
43
42
44
-
## Provisioning a new Service Instance
43
+
## Provisioning a new Object Storage Service Instance
45
44
46
45
The request parameters for Service provisioning are:
47
46
@@ -55,9 +54,9 @@ The request parameters for Service provisioning are:
55
54
| metadata | The metadata of the bucket | object | No |
56
55
| publicAccessType | The public access type of the bucket. Valid values are NoPublicAccess, ObjectRead and ObjectReadWithoutList. Default is NoPublicAccess | string | No |
57
56
58
-
## Attaching an Existing Service Instance
57
+
## Using an Existing Object Storage Service Instance
59
58
60
-
For more information about binding to an existing Object Storage service instance, see [Attaching an Existing Service Instance](services.md#attaching-an-existing-service-instance).
59
+
For more information about binding to an existing Object Storage service instance, see [Using an Existing Service Instance](services.md#using-an-existing-service-instance).
61
60
62
61
The request parameters for the existing Service provisioning are:
63
62
@@ -90,7 +89,7 @@ Service Binding is optional in case of this service. OCI User credentials can be
0 commit comments