When configuring an OCI API Gateway deployment, you need to specify the backend type for each route in your API deployment specification3. The backend type determines how the API gateway handles requests to that route and forwards them to the appropriate backend service3. The following backend types are valid options for an OCI API Gateway deployment3:

• HTTP_BACKEND: The API gateway forwards requests to an HTTP or HTTPS URL as the backend service.
• ORACLE_FUNCTIONS_BACKEND: The API gateway invokes an Oracle Functions function as the backend service.
• STOCK_RESPONSE_BACKEND: The API gateway returns a stock response without invoking any backend service. ORACLE STREAMS_BACKEND is not a valid backend type for an OCI API Gateway deployment. Oracle Streams is a fully managed, scalable, and durable messaging service that you can use to ingest and consume large amounts of data in real-time4. However, Oracle Streams is not supported as a backend service for an OCI API Gateway deployment.

To pull a Docker image from OCI Registry to the client machine, you need to use the docker pull command with the following syntax1: docker pull .ocir.io//: where:

• is the key for the OCI Registry region you’re using. For example, iad. See Availability by Region1.
• ocir.io is the OCI Registry name.
• is the auto-generated Object Storage namespace string of the tenancy that owns the repository from which you want to pull the image (as shown on the Tenancy Information page)1.
• is the name of the repository that contains the image you want to pull.
• is the tag of the image you want to pull.

Explanation

The correct syntax for implementing a rolling update deployment strategy in Kubernetes using the kubectl command is: kubectl rolling-update --image=image:v2 This command initiates a rolling update of the specified deployment by updating the container image to image:v2. The rolling update strategy ensures that the new version of the application is gradually deployed while maintaining availability and minimizing downtime.