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

User Harbor ourselves #237

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
67 changes: 67 additions & 0 deletions proposals/use-our-own-registry.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,67 @@
# Harbor Community Proposal - Eating your own dog food Container Registry

Status: In Progress
Created by: Vadim Bauer
Created time: January 24, 2024 1:17 PM
Last Edited: January 24, 2024 1:52 PM

# **Proposal:Use Our Own Registry**

# **Abstract**

Use of our Harbor registry to distribute our own container images. We should be the first to adopt our own technology. If we are not willing to utilize our own application for day-to-date use, don't expect others to do so.

# **Background**

Today, Harbor is the most popular and widely recognized full-fledged container registry on the market. Yet, we are not using our own product ourselfs. Hence the [dogfooding](https://www.projectmanagement.com/articles/217092/eat-your-own-dog-food#_=_) title

# **Proposal**

Deploy and operate Harbor on AWS to distribute containerized images of Harbor.

With support and sponsoring from [8gears](https://container-registry.com/), a 24/7 operation can be accomplished.

# **Non-Goals**

# Rationale

Here are some advantages of using our own Registry.

*Eating your own dog food* doesn't just mean we should use our own product. It also means you should attempt to install it and configure it ourselves.

- Better understanding of the end users' experience.
- Product's quality would significantly improve.
- Better documentation
- Users can see how Harbor can be used in real case scenario

## Costs

The used AWS account is sponsored by AWS. There is currently no cost limited or restriction.

- 80% of the costs will be traffic. Assuming 10 TiB monthly traffic per month would generate ~870-1000 USD (10240 GiB * 0.085USD/GiB)
- Fixed costs will be around 200-300 USD a month.
- As a Fallback, Cloudflare R2 can be used instead of AWS S3, where there are no egress fees. However there are no agreements between CNCF and Cloudflare in place..

# **Compatibility**

-
-

# **Implementation**

![Untitled](assets/aws-infa-harbor.png)

Better understanding of the end users' experience

## Phase I
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we introduce Phase 0?

I believe we should aim for a graceful migration and use the test assets as a pilot to validate the stability and availability of the system for a period of time.


- IaC Repo containing the infrastructure
- Migrate all images from Docker Hub to Harbor.
- Replace image references in Documentation
- Replace Image references in Compose
- Replace image references in Helm
- Keep Docker Hub account as a fallback

## Phase II

- Disable DockerHub Account