Skip to content

Conversation

@mich-elle-luna
Copy link
Collaborator

@mich-elle-luna mich-elle-luna commented Jul 31, 2025

DOC-3151 DOC-5312 DOC-3851
More info to help new users connect to a database and configure their Kubernetes secrets.

Details:
• New Database Connectivity Guide - Created a comprehensive guide (content/operate/kubernetes/networking/database-connectivity.md) that consolidates scattered connectivity information into a single authoritative resource covering service types, in-cluster/external access patterns, credentials management, connection examples, and troubleshooting, while eliminating content duplication by streamlining related pages (networking index, database controller, REDB index) to reference this central guide

- New Kubernetes Secrets configuration guide

  • Cover license configuration using both licenseSecretName and direct embedding methods
  • Include cluster FQDN determination for licensing purposes
  • Document TLS certificate configuration for mTLS and different services
  • Provide step-by-step kubectl commands and YAML examples
  • Add best practices for secret management
  • Include cross-references to related documentation

This addresses the gap in practical guidance for managing Redis Enterprise configuration through Kubernetes Secrets, complementing the existing API reference documentation.

- Add comprehensive guide for storing Redis Enterprise configuration in Kubernetes Secrets
- Cover license configuration using both licenseSecretName and direct embedding methods
- Include cluster FQDN determination for licensing purposes
- Document TLS certificate configuration for mTLS and different services
- Provide step-by-step kubectl commands and YAML examples
- Add best practices for secret management
- Include cross-references to related documentation

This addresses the gap in practical guidance for managing Redis Enterprise configuration through Kubernetes Secrets, complementing the existing API reference documentation.
Copy link
Contributor

@kaitlynmichael kaitlynmichael left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On small grammar error before I get this reviewed by the dev team

@kaitlynmichael kaitlynmichael self-assigned this Aug 11, 2025
@kaitlynmichael kaitlynmichael changed the title Add Kubernetes configuration secrets documentation K8s: add more secrets and connectivity info Aug 11, 2025
@markotrapani
Copy link
Contributor

Thanks for your work on this!

Note: on https://redis.io/docs/staging/DOC-3151/operate/kubernetes/networking/ ...

These sections appear redundant:
Screenshot 2025-08-15 at 2 19 50 PM
Screenshot 2025-08-15 at 2 19 53 PM

@kaitlynmichael kaitlynmichael requested review from a team and kaitlynmichael and removed request for kaitlynmichael August 19, 2025 18:40
Copy link
Collaborator

@dwdougherty dwdougherty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mostly just some missing punctuation (per SG). Up to you. I'll go ahead and approve to save you some time.


When `defaultUser` is disabled, the database secret is not created, and you must configure custom authentication.

## Connection examples
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems like it might be a good use case for the multitab control. Up to you.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea! I'll create a ticket to identify uses in my docs for this. https://redislabs.atlassian.net/browse/DOC-5614

@kaitlynmichael kaitlynmichael merged commit cea01be into main Aug 21, 2025
5 checks passed
@kaitlynmichael kaitlynmichael deleted the DOC-3151 branch August 21, 2025 16:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants