LREST and LRPDB documentation beautification / setup problem

[ilfur]

1. In the description of setting up certificates for an LREST container and LRPDBs, when using the sample YAMLs, there was a problem with one of the created secrets. The LREST container could not find a key mentioned in its deployment.
   I am talking about this section in the docs:
   https://github.com/oracle/oracle-database-operator/tree/main/docs/multitenant/lrest-based#create-secrets-for-certificate-and-keys

There are some lines of shell command code to create secrets with private and public keys inside:
kubectl create secret tls prvkey --key="private.key" --cert=ca.crt -n cdbnamespace
kubectl create secret generic pubkey --from-file=publicKey=public.pem -n cdbnamespace
kubectl create secret generic prvkey --from-file=privateKey="private.key" -n pdbnamespace

The problem was with the first line. The LREST container could not find the key "privateKey" in the secret prvkey in the cdbnamespace. Because the secret and key mentioned in the LREST containers YAML used that notion. After changing the line to look similar as the one for the pdbnamespace, it worked:
kubectl create secret generic prvkey --from-file=privateKey="private.key" -n cdbnamespace

2. this is just for beutification: instead of creating so many secrets with just one password inside each, just create on single secret with all those keys and passwords that are related to each other anyway.

3. this is also just for beautification: instead of manually encrypting secrets' values with pkcs8, just leave them as they are. there are good ways to reference values in secrets from external or internal vault solutions, like hashicorp vault or Oracle Cloud Vault. So the implementor does not need to care about that himself and reduce complexity.

Best regards!
Marcel