DOCS-776: Document private CA Gateway setup for Kubernetes Injector

[harrison-akeyless]

Summary:

• Documented private/internal CA Gateway guidance for AKEYLESS_API_GW_URL.
• Added recommended gatewayCert.tlsCertsSecretName secret-based configuration.
• Added certificate secret creation command.
• Kept legacy inline AKEYLESS_GW_CERTIFICATE note.
• Nested private-CA guidance under the Gateway URL bullet.

[coderabbitai]

Warning

Rate limit exceeded

@harrison-akeyless has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 23 minutes and 30 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: d5aa8597-3a99-4ef8-bf2a-1bc3dd6a0999

📥 Commits

Reviewing files that changed from the base of the PR and between 14aff8c and d844c61.

📒 Files selected for processing (1)

• docs/Integrations & Plugins/plugins-overview/kubernetes-plugins/akeyless-kubernetes-secrets-injector.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch v1.0_docs-776-k8s-injector-private-ca

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[EldadH89]

@netserheruty can you confirm it's working that way? we used the env vars, certificate is not a secret at all but this approach is more elegant and centralized (assuming this is the same secret as the GW is using )
@harrison-akeyless FYI