You have a containerized app that requires an Autonomous Transaction Processing (ATP) Database. Which option is not valid for o from a container in Kubernetes?
The Kubernetes documentation lays out the followinguse 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 to deal 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 it to 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 with the implementation details or management of the message queue. The application can simply use it as a service.
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 theATP Service Instance
- Deploy theService Instance
- Create a YAML config for theATP Service Binding
- Deploy the Service Binding to obtain which results in the creation of anew 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 todecode 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
Currently there are no comments in this discussion, be the first to comment!