Loading…
Topic
Red Hat Developer Hub
5 posts about Red Hat Developer Hub. Every summary links to the original.
- 5 posts
- 1 company
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Newest first
Posts
Build golden path CI/CD workflows in Red Hat Developer Hub
This article continues a series on Red Hat Developer Hub, describing how platform engineers create golden path templates to standardize developer workflows. The sample template scaffolds a Go project with a Tekton pipeline, Argo CD manifests, a devfile, and catalog-info.yaml containing annotations that map to enabled plug-ins. Developers use the template from the self-service screen, completing a form to specify application metadata, image registry, OpenShift details, and Git repository. After scaffolding, automated CI/CD is triggered by a Git commit, and developers monitor Tekton PipelineRuns, Argo CD sync status, container images from Quay, and Kubernetes resources from tabs within Developer Hub. The article provides step-by-step instructions for both platform engineers and developers, including template authoring, registration, scaffolding, and subsequent observability.
From hours to minutes: Optimizing Red Hat Developer Hub performance testing with immutable LDAP images
Red Hat Developer Hub performance testing became slow and unreliable as runtime generation of large user and group catalogs stretched environment setup and introduced synchronization failures. Previously, the framework created entries through serialized Keycloak Admin REST API operations, then waited for paginated synchronization into the Developer Hub database; concurrency could not eliminate timeouts, rate limits, or incomplete catalogs. The replacement uses immutable, pre-built LDAP container images selected by an RBAC_POLICY-USER_COUNTu-GROUP_COUNTg convention, with slapadd loading seed data directly into offline LMDB files in a multi-stage build. LDAP starts with 10,000-plus indexed users, while Keycloak serves as an authentication gateway and Developer Hub waits for its initial catalog sync. Reported population time fell from 22-plus hours to 2 minutes 8 seconds for 10,000 users and 150,000 groups, while the immutable approach made tests deterministic, reduced flaky failures, stabilized baselines, and enabled larger reproducible scenarios.
Build a unified CI/CD control plane with Red Hat Developer Hub
Red Hat Developer Hub brings OpenShift, Argo CD, Tekton, and Quay workflows into a unified developer portal, addressing context switching across separate consoles. The guide targets platform engineers and covers installing the Operator, creating GitHub and cluster credentials, configuring application and dynamic-plugin settings, defining RBAC policies, and deploying a Backstage custom resource. It uses a Kubernetes service-account token for access to pods, deployments, and pipeline runs, while Quay integration exposes image tags, vulnerabilities, and manifest details. After granting read access in monitored namespaces, the resulting portal can display pipeline runs, deployment health, image information, and Argo CD status in one view. The source says the setup is a proof-of-concept foundation, with a follow-up planned for software templates and developer self-service.
Red Hat Developer Hub: Preventing compliance violations with AI coding agents
AI coding agents can generate services quickly, but they may miss organization-specific architecture, ownership, and compliance rules stored in an internal developer portal. A demo connects Claude Code to a Backstage-based Red Hat Developer Hub through Backstage CLI actions, allowing the agent to query domains, components, APIs, software templates, and TechDocs before proposing a design. In a simulated Parasol Insurance catalog with more than 500 entities across 14 domains, the agent finds an existing but unrelated reconciliation service and resolves a Claims–Billing messaging conflict by keeping IBM MQ at the payment boundary and publishing internal events to Kafka. It then uses catalog relationships and specifications to identify integrations and produces a Technology Decision Summary that cites the sources behind each choice, making the resulting decisions reviewable and traceable.
Red Hat Developer Hub software template authoring with rhdh-templates
Red Hat Developer Hub software template authors often face Nunjucks syntax, uncertain location.yaml placement, and errors discovered only after rendering in the developer portal. The rhdh-templates skill in the RHDH Users Skill Pack equips an AI assistant with RHDH and Backstage conventions, Nunjucks helpers, schema checks, reference templates, and local validation. After installation, it can scaffold repositories, guide interactive parameterization of existing codebases, add template parameters and Scaffolder steps, generate location.yaml, and check templates offline before merge. With an optional reachable RHDH instance, the skill can list active actions, read their schemas, and dry-run execution against the API; the walkthrough uses the Quarkus getting-started quick start and reports a clean validation run as the readiness signal.
Related topics
All topics →Weekly digest
The best engineering reads, once a week.