API Management service for grpc service inside cluster

@Maria Dąbrowiecka

Thank you for reaching out !!

It looks like you're encountering a "415 Unsupported Media Type" error when trying to access your gRPC service through the Azure API Management. This type of error usually indicates that the server is refusing to process the request because the request payload is in a format that the server does not support.

Here are a few steps you can take to troubleshoot the issue:

Check Protobuf File: Ensure that you have uploaded the correct and valid Protobuf (.proto) file for your gRPC service to the API Management. This file should define your service's methods and messages correctly.

gRPC Server URL: Make sure that the gRPC server URL (the one exposed by your nginx) is correct and that the server is accessible over HTTPS. Verify that there are no typos in the URL.

Supported Gateway: Please remember that gRPC APIs are only supported with the self-hosted gateway at this time. If you're using a managed gateway, that could be the issue.

Content-Type Header: The 415 error can also arise if the request is not using the proper Content-Type header. For gRPC, the content type is typically application/grpc. Ensure that your client is setting this header when making requests.

Logs and Monitoring: Check the logs available in Azure API Management for more detailed error descriptions. You might also want to enable additional logging and monitoring for your gRPC service to capture any issues on that side.

Kubernetes Considerations: Since you're using a gRPC service inside a Kubernetes cluster, ensure that your service objects are set up correctly and are exposing the necessary ports.

Here’s a link to a documentation that might help you with setting up gRPC in API Management: Import a gRPC API.