-
Notifications
You must be signed in to change notification settings - Fork 80
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
Vad1mo
wants to merge
2
commits into
goharbor:main
Choose a base branch
from
container-registry:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+67
−0
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 | ||
|
||
- 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 |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
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.