Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chainguard Registry architecture diagram #1689

Open
MordodeMaru opened this issue Jul 15, 2024 · 5 comments
Open

Chainguard Registry architecture diagram #1689

MordodeMaru opened this issue Jul 15, 2024 · 5 comments
Assignees
Labels

Comments

@MordodeMaru
Copy link

Chainguard Registry Visual Reference Architecture Needed

Overview

We need to create a comprehensive visual reference architecture that illustrates how Chainguard's Registry operates both as a standalone solution and in conjunction with other popular artifact repositories. This visual guide will help our users and potential customers understand the flexibility and interoperability of our registry within various ecosystems.

Scope

The visual reference architecture should cover the following scenarios:

  1. Chainguard Registry as a standalone solution
  2. Chainguard Registry integrated with:
    • JFrog Artifactory
    • Sonatype Nexus
    • Docker Hub
    • Harbor
    • Google Artifact Registry
    • AWS ECR Public Gallery

Key Requirements

  • Clear and visually appealing diagrams
  • Explanation of data flow and integration points
  • OIDC
  • Pull-through caches
  • Consideration of security aspects and compliance requirements
  • Tags and refresh frequency

Expected Outcome

A set of diagrams and accompanying explanations that can be used in our documentation, presentations, and sales materials to effectively communicate the versatility of Chainguard Registry.

Next Steps

  • @MordodeMaru to draft the first diagrams
  • Review with @imjasonh and any other SME
  • Create visual designs based on the approved architecture
  • Incorporate feedback and finalize the reference architecture

Please comment on this issue with any questions, suggestions, or if you need any clarification on the requirements.

@some-natalie
Copy link

some-natalie commented Jul 15, 2024

This is what I made (forgiving the lack of fontawesome icons in github, of course)

flowchart LR
    subgraph corporate network
    A(fa:fa-laptop-code\ndeveloper)
    B(fas:fa-boxes-stacked\ncontainer\nregistry)
    A -->| push new images | B
    B -->| pull base images | A
    end
    subgraph internet
    C(:octopus:\nchainguard registry)
    D(fab:fa-docker\ndockerhub)
    B -->| pull tokens\nor\nOIDC | C
    B -->| pull tokens | D
    end
Loading

Image

@amouat
Copy link
Collaborator

amouat commented Jul 17, 2024

@johnfosborneiii made this one

Image

@amouat
Copy link
Collaborator

amouat commented Jul 19, 2024

Another one!

Image

@amouat
Copy link
Collaborator

amouat commented Jul 19, 2024

@sheesh sheesh added the backlog label Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants