Explanation
The Kubernetes documentation lays out the following use case for the Service Catalog API:
An application developer wants to use message queuing as part of their application running in a Kubernetes cluster. However, they do not want todeal with the overhead of setting such a service up and administering it themselves. Fortunately, there is a cloud provider that offers message queuing as a managed service through its service broker.
A cluster operator can setup Service Catalog and use itto communicate with the cloud provider's service broker to provision an instance of the message queuing service and make it available to the application within the Kubernetes cluster. The application developer therefore does not need to be concerned withthe implementation details or management of the message queue. The application can simply use it as a service.
The samples in theOCI Service Broker source code include a deployment YAML file that describes how to use an init container to take the values in the Autonomous Transaction Processing service binding and put them in environment variables or in a volume mount. After that, your application can use those values to connect to the database.
Once you've installed and registered the service broker, you're ready to use the ATP service plan to provision an ATP instance. I'll go into details below, but the overview of the process looks like so:
-Create a Kubernetes secret with a new admin and wallet password (in JSON format)
- Create a YAML configuration for the ATP Service Instance
- Deploy the Service Instance
- Create a YAML config for the ATP Service Binding
- Deploy the Service Binding to obtain which results in the creation of a new Kubernetes secret containing the wallet contents
- Create a Kubernetes secret for Microservice deployment use containing the admin password and the wallet password (in plain text format)
- Create a YAML config for the Microservice deployment which uses an initContainer to decode the wallet secrets (due to a bug which double encodes them) and mounts the wallet contents as a volume References:
https://blogs.oracle.com/developers/creating-an-atp-instance-with-the-oci-service-broker
https://blogs.oracle.com/cloud-infrastructure/integrating-oci-service-broker-with-autonomous-transaction-proces

Explanation
If you are running your Kubernetes cluster on Oracle Container Engine for Kubernetes (commonly known as OKE), you can have OCI automatically provision load balancers for you by creating a Service of type LoadBalancer instead of (or in addition to) installing an ingress controller like Traefik or Voyage YAML file

When you apply this YAML file to your cluster, you will see the new service is created. After a short time (typically less than a minute) the OCI Load Balancer will be provisioned.

https://oracle.github.io/weblogic-kubernetes-operator/faq/oci-lb/

Explanation
Overviewof Functions:
The serverless and elastic architecture of Oracle Functions means there's no infrastructure administration or software administration for you to perform. You don't provision or maintain compute instances, and operating system softwarepatches and upgrades are applied automatically. Oracle Functions simply ensures your app is highly-available, scalable, secure, and monitored. With Oracle Functions, you can write code in Java, Python, Node, Go, and Ruby (and for advanced use cases, bringyour own Dockerfile, and Graal VM). You can then deploy your code, call it directly or trigger it in response to events, and get billed only for the resources consumed during the execution.
References:
https://docs.cloud.oracle.com/en-us/iaas/Content/Functions/Concepts/functionsoverview.htm

Explanation
Pushing Images Using the Docker CLI:
You use the Docker CLI to push images to Oracle Cloud Infrastructure Registry.
To push an image, you first use the docker tag command to create a copy of the local source image as a new image (the new image is actually just a reference tothe existing source image). As a name for the new image, you specify the fully qualified path to the target location in Oracle Cloud Registry where you want to push the image, optionally including the name of a repository.
For example, assume you have a local image named acme-web-app:latest. Let's say you want to push this image to Oracle Cloud Infrastructure Registry with a name of acme-web-app:version2.0.test into a repository called project01 in the Ashburn region of the acme-dev tenancy. When you use the docker tag command, you'd name the new image with the fully qualified path to its destination, in the format <region-key>.ocir.io/<tenancy-namespace>/<repo-name>/<image-name>:<tag>. So in this case, you'd name the new image iad.ocir.io/ansh81vru1zp/project01/acme-web-app:version2.0.test. Subsequently, when you use the docker push command, the image's name ensures it is pushed to the correct destination.
To push images to Oracle Cloud Infrastructure Registry using the Docker CLI:
If you already have an auth token, go to the next step. Otherwise:
In the top-right corner of the Console, open the Profile menu () and then click User Settings to view the

details.
On the Auth Tokens page, click Generate Token.
Enter a friendly description for the auth token.Avoid entering confidential information.
Click Generate Token. The new auth token is displayed.
Copy the auth token immediately to a secure location from where you can retrieve it later, because you won't see the auth token again in the Console.
Close theGenerate Token dialog.
References:
https://docs.cloud.oracle.com/en-us/iaas/Content/Registry/Tasks/registrypushingimagesusingthedockercli.htm

Explanation
Managing Topics and Subscriptions:
1. Create Notifications Topic and Subscription
If a suitable Notifications topic doesn't already exist, then you must log in to the Console as a tenancy administrator and create it. Whether you use an existing topic or create a new one, add an email address as a subscription so that you canmonitor that email account for notifications
2. Using the Console to Create a Rule
Use the Console to create a rule with a pattern that matches bucket creation events emitted by Object Storage.
Specify the Notifications topic you created as an action to deliver matching events. To test your rule, create a bucket. Object Storage emits an event which triggers the action. Check the email specified in the subscription to receive your notification

References:
https://docs.cloud.oracle.com/en-us/iaas/Content/Events/Concepts/eventsgetstarted.htm
https://docs.cloud.oracle.com/en-us/iaas/Content/Notification/Tasks/managingtopicsandsubscriptions.htm
https://docs.cloud.oracle.com/en-us/iaas/Content/Notification/Concepts/notificationoverview.htm
https://docs.cloud.oracle.com/en-us/iaas/Content/Events/Concepts/filterevents.htm
https://docs.cloud.oracle.com/en-us/iaas/Content/ResourceManager/Tasks/managingstacksandjobs.htm