-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
RHDH Cookbooks for Platform Engineers
-
False
-
-
False
-
-
To Do
-
RHIDP-7905 - Cookbooks for Platform Engineers and Plugin Developers
-
QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
-
-
EPIC Goal
- Platform engineers can efficiently deploy, configure, and manage RHDH instances across various environments (OCP, AWS, Azure, GCP) including air-gapped setups
- Platform engineers have access to proven reference architectures, high availability configurations, and operational best practices
- Plugin developers can quickly bootstrap new dynamic plugin projects with clear development environment setup instructions
- Both user personas have comprehensive guidance for testing, debugging, and troubleshooting their respective implementations
- Users can navigate from a single entry point to detailed, practical documentation organized in a tree-like structure
- Internal processes and approaches are documented with references to open-source implementations and upstream documentation
Background/Feature Origin
- Create comprehensive, practical cookbooks that provide step-by-step guides for platform engineers and plugin developers working with Red Hat Developer Hub (RHDH)
- Extend existing documentation with real-world scenarios, implementation approaches, and operational best practices
- Establish a centralized knowledge base that bridges the gap between high-level documentation and hands-on implementation
Out of Scope (Optional)
- Replacement of existing upstream or product documentation
- Comprehensive code tutorials (preference for linking to existing repositories)
- Basic RHDH concepts already covered in official documentation
- Generic Backstage documentation not specific to RHDH implementation
User Scenarios
- Cookbooks must address real-world enterprise deployment scenarios
- Air-gapped environment considerations must be included for security-conscious organizations
- Multi-cloud deployment scenarios should be covered for hybrid environments
- Role-based access patterns should reflect common enterprise organizational structures
- Integration examples should cover commonly used enterprise tools and systems
Dependencies (internal and external)
Acceptance Criteria
- Comprehensive deployment guides for RHDH across multiple platforms (OCP, AWS, Azure, GCP)
- Reference architectures and high availability configuration examples
- Step-by-step installation, upgrade, and configuration procedures
- Authentication and authorization (RBAC) implementation guides with practical examples
- Monitoring, logging, audit logging, and telemetry configuration instructions
- Security best practices and vulnerability management guidance
- Dynamic plugin management lifecycle documentation
- Plugin building, testing, and shipping processes from platform perspective