New Blog Post: Exposing Your OTEL Collector with the Kubernetes Gateway API & mTLS

[vipinvkmenon]

Description:
This blog post will be a step-by-step demonstration/tutorial on how to expose an OpenTelemetry Collector deployed within a Kubernetes cluster to external clients using the Kubernetes Gateway API . We will also examine how to secure this through mTLS.We will be using Istio as our Gateway Class. However, the vendor-neutral configuration can be used with any other Gateways/ Service mesh supporting the new Kubernetes Gateway API.

Outline
A basic structure for the blog would be as follows:

• Introduction:
  • Need to expose OTEL Collector externally
  • Brief introduction to Gateway API and difference from Ingress
  • Brief introduction to mTLS
• Step by step setup
  • Configure and deploy OTEL Collector
  • Generate the Client and Server Certificates
  • Expose the OTEL Collector with Gateway API
    • Installing the Gateway API CRDs
    • Creating the Gateway
    • Creating a grpcRoute(and HTTPRoute)
  • Configure External OTEL Client
  • Verify Steup
• Summary & Conclusions

---

Will cnage structure and content based on feedback.

SIG & Sponsor : I believe this would be part of the End-User SIG under Cross Cutting SIGs (@danielgblanco). (However, I can change based feedback)

[svrnm]

Thanks for proposing this blog post, @vipinvkmenon!

@danielgblanco are you sponsoring this blog post?

@open-telemetry/collector-approvers @open-telemetry/operator-approvers PTAL as well, since this is collector/k8s related

[danielgblanco]

I think this would be a great blog post! I would be happy to sponsor this. However, due to personal time-off and KubeCon prep I may be not review things until April. Does that align with your expectations?

[vipinvkmenon]

Hi @danielgblanco ,

Yes, that is fine. I shall strat working on this and give an update with this in April