docs: adding GKE specific workaround to the cilium provider documentation

[aksenk]

📑 Description

If you are using a GKE cluster, you cannot connect Keep to the Google-managed hubble-relay directly because:

• hubble-relay operates only in secure mode,
• hubble-relay requires client certificate authentication.

However, Keep does not currently support these features.

To work around this, you can add an NGINX Pod that listens on a plaintext HTTP port and proxies requests to hubble-relay secure port using hubble-relay certificates.

✅ Checks

• My pull request adheres to the code style of this project
• My code requires changes to the documentation
• I have updated the documentation as required
• All the tests have passed

ℹ Additional Information

I created root cause feature request

close #4264

[vercel]

Someone is attempting to deploy a commit to the KeepHQ Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.

[shahargl]

Thanks on that! Gonna definitely make this possible within Keep!

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
keep	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 27, 2025 5:46pm

[shahargl]

@Matvey-Kuk any reason not to merge?

[Matvey-Kuk]

@shahargl I approved and enabled auto-merge, wondering why it's not merging

[skynetigor]

LGTM

[github-actions]

🎊 Fantastic work @aksenk! Your very first PR to keep has been merged! 🎉🥳

You've just taken your first step into open-source, and we couldn't be happier to have you onboard. 🙌
If you're feeling adventurous, why not dive into another issue and keep contributing? The community would love to see more from you! 🚀

For any support, feel free to reach out on the community: https://slack.keephq.dev. Happy coding! 👩‍💻👨‍💻