ORDS is a piece of software that acts as an intermediary between Oracle Database and the layers where business logic is implemented and/or consumed.
NOTE: If your database hasn’t been set up for ORDS just google for it or take a look at this post.
With ORDS you expose database objects as REST. ORDS can be started standalone or in an application server. Deploying ORDS in Kubernetes as stateless pods with several replicas provide an elastic layer of rest exposition, out of the database, with high availability and fault tolerant.
First of all, we need a container ready to run ORDS in standalone mode. For this particular case, we are utilising one already done, see yaml file mentioned in next steps.
Let’s start creating a secret for storing the password for the user that makes de connection to the database:
kubectl create secret generic ordspassword --type=string --from-literal=password=[somepassword]
env: - name: DB_HOSTNAME value: "example:172.16.0.7" - name: DB_PORT value: "example:1521" - name: DB_SERVICENAME value: "example:jsonpdb.xxxxxx.yyyyyy.oraclevcn.com" - name: APEX_PUBLIC_USER_NAME value: "ORDS_PUBLIC_USER" - name: ORDS_PASS valueFrom:
kubectl apply -f my.yaml
kubectl get svc
javiermugueta$ kubectl get svc NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE eciveci LoadBalancer 10.96.92.19 126.96.36.199 3000:31522/TCP 4d kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 15d ordscontainer LoadBalancer 10.96.229.248 188.8.131.52 8080:31523/TCP 2d
I have a setup of ords on tomcat, on OKE behind nginx ingress. The login page displays well, but I am running into 403 error hit submit to login. :
full message :
The request cannot be processed because this resource does not support Cross Origin Sharing requests, or the request Origin is not authorized to access this resource. If ords is being reverse proxied ensure the front end server is propagating the host name, for mod_proxy ensure ProxyPreserveHost is set to On
I tried to add proxyPort, proxyName, scheme and secure params to http connector but no effect.
I added also in my nginx ingress :
proxy_set_header Host $host;
proxy_set_header X-Forwarded-Host $host:$server_port;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Origin “”;
nginx.ingress.kubernetes.io/cors-allow-methods: “PUT, GET, POST, OPTIONS”
Still nothing change.
exposing ords on tomcat directly as loadbalancer resolves this but I don’t think it is a suitable solution.
Any idea ?
Why don’t you launch ords as stand-alone?