Skip to content

NimTechnology

Trình bày các công nghệ CLOUD một cách dễ hiểu.

  • Kubernetes & Container
    • Docker
    • Kubernetes
      • Gateway API
      • Ingress
      • Pod
    • Helm Chart
    • OAuth2 Proxy
    • Isito-EnvoyFilter
    • Apache Kafka
      • Kafka
      • Kafka Connect
      • Lenses
    • Vault
    • Longhorn – Storage
    • VictoriaMetrics
    • MetalLB
    • Kong Gateway
  • CI/CD
    • ArgoCD
    • ArgoWorkflows
    • Argo Events
    • Spinnaker
    • Jenkins
    • Harbor
    • TeamCity
    • Git
      • Bitbucket
  • Coding
    • DevSecOps
    • Terraform
      • GCP – Google Cloud
      • AWS – Amazon Web Service
      • Azure Cloud
    • Golang
    • Laravel
    • Python
    • Jquery & JavaScript
    • Selenium
  • Log, Monitor & Tracing
    • DataDog
    • Prometheus
    • Grafana
    • ELK
      • Kibana
      • Logstash
  • BareMetal
    • NextCloud
  • Toggle search form

[Harbor] Configure the replications on Harbor

Posted on October 23, 2022May 24, 2023 By nim 1 Comment on [Harbor] Configure the replications on Harbor

Task này của chúng ta là backup image từ another Docker registry.
Và bạn cũng đang có sẵn Harbor.
Hoặc bạn muốn push image sang another Docker registry một cách tự động.

Giờ chúng ta cùng nhau bắt đầu Với Harbor thôi.

Contents

Toggle
  • 1) Creating New Registry Endpoint
    • 1.1) AWS ECR
  • 2) Configure Replications.
    • 2.1) Pull-based
      • 2.1.1) AWS ECR
    • 2.2) Push-base
      • 2.2.1) ECR.

1) Creating New Registry Endpoint

Để thực hiện được tính năng này thì bạn cần Create “New Registry Endpoint”

1.1) AWS ECR

2) Configure Replications.

2.1) Pull-based

Bạn sẽ cấu hình để Harbor sẽ pull image từ another docker registy.

2.1.1) AWS ECR

Ở đây chúng ta sẽ configure harbor pull image từ ECR

Trên aws thì imge của bạn nhé nhu sau:
31336350XXX.dkr.ecr.us-west-2.amazonaws.com/nim_engines_result_handler:staging-e6f2831b-linux

Bạn cần tạo 1 project trên Harbor trước nhé.

Giờ bạn tạo Replication Rule nhé

Source resource filter: bạn điên tên image như là: nim_engines_result_handler
Destination:
—-> Namespace: bạn điện tên project mà bạn mới tạo trên harbor example: opxswxat
—-> Flattening: bạn chọn No Flatting

Sau khi bạn save lại thì bạn chạy replicate

show log detail
Đây là log khi harbor pull image.

2.2) Push-base

2.2.1) ECR.

https://mappslearning.com/2021/11/30/enabling-container-image-replication-in-a-harbor-registry/

Phần này sẽ dễ hơn

Mình có 1 project trên harbor.
Phần configure the replication rule.

Các bạn có thể tham khảo thêm bài này:
https://vinothecloudone.medium.ninja/yet-another-harbor-registry-architecture-for-vsphere-with-tanzu-yaha-43395f6547e3

Harbor, Kubernetes & Container

Post navigation

Previous Post: [Ingress Nginx] Internal error occurred: failed calling webhook “validate.nginx.ingress.kubernetes.io”
Next Post: [AWS] Pull docker images from the other ECR

More Related Articles

[KOS] Use KOS to install kubernetes so easily! Kubernetes
[Helm-k8s] Researching to write a unit test for your helm chart – Kubernetes Helm Chart
[Kubernetes] Lesson1: k8s easy – Kubernetes architecture and components Kubernetes & Container
[code/k8s] Lost or not found file inside the container on k8s Kubernetes
[Oauth2-Proxy] Protect any of your websites on Kubernetes by Oauth2-Proxy Kubernetes & Container
[Istio] Custom Authorization with Istio Golang

Comment (1) on “[Harbor] Configure the replications on Harbor”

  1. Working at Target says:
    November 19, 2022 at 11:08 am

    Nice post.

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Tham Gia Group DevOps nhé!
Để Nim có nhiều động lực ra nhiều bài viết.
Để nhận được những thông báo mới nhất.

Recent Posts

  • [Rancher/EKS] Rancher from v2.12.x can not work on eks cluster. April 15, 2026
  • [Telegram/Openclaw] Configure openclaw bot in a Telegram group. March 31, 2026
  • Tutorial: Gateway API + Traefik + oauth2-proxy (Microsoft Entra ID) March 30, 2026
  • Full + incremental backup: When restoring, do deleted files come back? March 27, 2026
  • [K8S] Create long-lived kubeconfig on k8s March 23, 2026

Archives

  • April 2026
  • March 2026
  • February 2026
  • January 2026
  • December 2025
  • November 2025
  • October 2025
  • September 2025
  • August 2025
  • July 2025
  • June 2025
  • May 2025
  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021

Categories

  • AI
    • OpenClaw
  • BareMetal
    • NextCloud
  • CI/CD
    • Argo Events
    • ArgoCD
    • ArgoWorkflows
    • Git
      • Bitbucket
    • Harbor
    • Jenkins
    • Spinnaker
    • TeamCity
  • Coding
    • DevSecOps
    • Golang
    • Jquery & JavaScript
    • Laravel
    • NextJS 14 & ReactJS & Type Script
    • Python
    • Selenium
    • Terraform
      • AWS – Amazon Web Service
      • Azure Cloud
      • GCP – Google Cloud
  • Kubernetes & Container
    • Apache Kafka
      • Kafka
      • Kafka Connect
      • Lenses
    • Docker
    • Helm Chart
    • Isito-EnvoyFilter
    • Kong Gateway
    • Kubernetes
      • Gateway API
      • Ingress
      • Pod
    • Longhorn – Storage
    • MetalLB
    • OAuth2 Proxy
    • Vault
    • VictoriaMetrics
  • Log, Monitor & Tracing
    • DataDog
    • ELK
      • Kibana
      • Logstash
    • Fluent
    • Grafana
    • Prometheus
  • Uncategorized
  • Admin

Copyright © 2026 NimTechnology.