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
Copy file name to clipboardExpand all lines: docs/ordsservices/README.md
+37-6Lines changed: 37 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,22 +25,53 @@ It supports the majority of ORDS configuration settings as per the [API Document
25
25
The ORDS and APEX schemas can be [automatically installed/upgraded](./autoupgrade.md) into the Oracle Database by the ORDS controller.
26
26
27
27
ORDS Version support:
28
-
* v22.1+
28
+
* 24.1.1
29
+
(Newer versions of ORDS will be supported in the next update of OraOperator)
29
30
30
31
Oracle Database Version:
31
32
* 19c
32
33
* 23ai (incl. 23ai Free)
33
34
35
+
### Prerequisites
34
36
35
-
### Common Configurations
37
+
1. Oracle Database Operator
38
+
39
+
Install the Oracle Database Operator (OraOperator) using the instructions in the [README](https://github.com/oracle/oracle-database-operator/blob/main/README.md) file.
40
+
41
+
1. Namespace
42
+
43
+
For a dedicated namespace deployment of the ORDSSRVS controller, refer to the "Namespace Scoped Deployment" section in the OraOperator [README](https://github.com/oracle/oracle-database-operator/blob/main/README.md#2-namespace-scoped-deployment).
44
+
45
+
The following examples deploy the controller to the 'ordsnamespace' namespace.
46
+
47
+
Create the namespace:
48
+
```bash
49
+
kubectl create namespace ordsnamespace
50
+
```
51
+
52
+
Apply namespace role binding [ordsnamespace-role-binding.yaml](./examples/ordsnamespace-role-binding.yaml):
53
+
```bash
54
+
kubectl apply -f ordsnamespace-role-binding.yaml
55
+
```
56
+
57
+
Edit OraOperator to add the namespace under WATCH_NAMESPACE:
58
+
```yaml
59
+
- name: WATCH_NAMESPACE
60
+
value: "default,<your namespaces>,ordsnamespace"
61
+
```
62
+
63
+
### Common configuration examples
36
64
37
65
A few common configuration examples can be used to quickly familiarise yourself with the ORDS Custom Resource Definition.
38
66
The "Conclusion" section of each example highlights specific settings to enable functionality that maybe of interest.
39
67
40
-
*[Containerised Single Instance Database using the Oracontroller](./examples/sidb_container.md)
41
-
*[Multipool, Multidatabase using a TNS Names file](./examples/multi_pool.md)
42
-
*[Autonomous Database using the Oracontroller](./examples/adb_oraoper.md) - (Customer Managed ORDS) <sup>*See [Limitations](#limitations)</sup>
43
-
*[Autonomous Database without the Oracontroller](./examples/adb.md) - (Customer Managed ORDS)
* [Containerised Single Instance Database (SIDB)](./examples/sidb_container.md)
72
+
* [Multidatabase using a TNS Names file](./examples/multi_pool.md)
73
+
* [Autonomous Database using the OraOperator](./examples/adb_oraoper.md) <sup>*See [Limitations](#limitations)</sup>
74
+
* [Autonomous Database without the OraOperator](./examples/adb.md)
44
75
* [Oracle API for MongoDB Support](./examples/mongo_api.md)
45
76
46
77
Running through all examples in the same Kubernetes cluster illustrates the ability to run multiple ORDS instances with a variety of different configurations.
Copy file name to clipboardExpand all lines: docs/ordsservices/examples/adb.md
+18-22Lines changed: 18 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,11 +5,7 @@ This example walks through using the **ORDSSRVS controller** with an Oracle Auto
5
5
This assumes that an ADB has already been provisioned and is configured as "Secure Access from Anywhere".
6
6
Note that if behind a Proxy, this example will not work as the Wallet will need to be modified to support the proxy configuration.
7
7
8
-
9
-
### Cert-Manager and Oracle Database Operator installation
10
-
11
-
Install the [Cert Manager](https://github.com/cert-manager/cert-manager/releases/download/v1.14.4/cert-manager.yaml) and the [Oracle Database Operator](https://github.com/oracle/oracle-database-operator) using the instractions in the Operator [README](https://github.com/oracle/oracle-database-operator/blob/main/README.md) file.
12
-
8
+
Before testing this example, please verify the prerequisites : [ORDSSRVS prerequisites](../README.md#prerequisites)
Copy file name to clipboardExpand all lines: docs/ordsservices/examples/adb_oraoper.md
+36-50Lines changed: 36 additions & 50 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,23 +4,15 @@ This example walks through using the **ORDS Controller** with a Containerised Or
4
4
5
5
When connecting to a mTLS enabled ADB while using the OraOperator to retreive the Wallet as is done in the example, it is currently not supported to have multiple, different databases supported by the single Ordssrvs resource. This is due to a requirement to set the `TNS_ADMIN` parameter at the Pod level ([#97](https://github.com/oracle/oracle-database-operator/issues/97)).
6
6
7
-
### Cert-Manager and Oracle Database Operator installation
8
-
9
-
Install the [Cert Manager](https://github.com/cert-manager/cert-manager/releases/download/v1.14.4/cert-manager.yaml) and the [Oracle Database Operator](https://github.com/oracle/oracle-database-operator) using the instractions in the Operator [README](https://github.com/oracle/oracle-database-operator/blob/main/README.md) file.
7
+
Before testing this example, please verify the prerequisites : [ORDSSRVS prerequisites](../README.md#prerequisites)
10
8
11
9
### Setup Oracle Cloud Authorisation
12
10
13
-
In order for the OraOperator to access the ADB, some pre-requisites are required, as detailed [here](https://github.com/oracle/oracle-database-operator/blob/main/docs/adb/ADB_PREREQUISITES.md). Either establish Instance Principles or create the required ConfigMap/Secret. This example uses the later:
11
+
In order for the OraOperator to access the ADB, some additional pre-requisites are required, as detailed [here](https://github.com/oracle/oracle-database-operator/blob/main/docs/adb/ADB_PREREQUISITES.md).
12
+
Either establish Instance Principles or create the required ConfigMap/Secret. This example uses the later, using the helper script [set_ocicredentials.sh](https://github.com/oracle/oracle-database-operator/blob/main/set_ocicredentials.sh) :
14
13
15
14
```bash
16
-
kubectl create configmap oci-cred \
17
-
--from-literal=tenancy=<TENANCY_OCID> \
18
-
--from-literal=user=<USER_OCID> \
19
-
--from-literal=fingerprint=<FINGERPRINT> \
20
-
--from-literal=region=<REGION>
21
-
22
-
kubectl create secret generic oci-privatekey \
23
-
--from-file=privatekey=<full path to private key>
15
+
./set_ocicredentials.sh run -n ordsnamespace
24
16
```
25
17
26
18
### ADB ADMIN Password Secret
@@ -31,6 +23,7 @@ Create a Secret for the ADB Admin password:
SERVICE_NAME=$(kubectl get adb adb-oraoper -o=jsonpath='{.spec.details.dbName}'_TP)
103
-
```
90
+
```bash
91
+
SERVICE_NAME=$(kubectl get -n ordsnamespace adb adb-oraoper -o=jsonpath='{.spec.details.dbName}'_TP)
92
+
```
104
93
105
94
1. Create a manifest for ORDS.
106
95
107
96
As an ADB already maintains ORDS and APEX, `autoUpgradeORDS` and `autoUpgradeAPEX` will be ignored if set. A new DB User for ORDS will be created to avoid conflict with the pre-provisioned one. This user will be
108
97
named, `ORDS_PUBLIC_USER_OPER`if`db.username` is either not specified or set to `ORDS_PUBLIC_USER`.
0 commit comments