controllers:

• watch for cluster.yaml updates & reflect addons annotations from cluster.yaml to argocd cluster yaml secrets
• watch argocd repo certs and check for expire, re-adding automatically
• tanzu watch for service associated with cluster to appear & annotate with fqdn automatically (in order to add dns entry for each cluster kubeapi)
• watch for certificate authority expiration and update ‘ca-bundle’ stored in vault

Why

In a world of containers, developers need to have multiple linux repos mirrored on prem for use when building or modifying images.

What

Similar to how cert-manager works with providers to extend functionality, repo-manager can be extended to mirror additional linux distros.

How

repo-manager provides an operator-type controller which watches for the CRD type ‘mirror.aarr.xyz’ & manages for each repo mirror:

• the deployment of a pod for mirroring
• a pvc for each pod
• the increasing of the pvc size as needed
• ingress configuration to reach each repo using a subpath http(s)://mirror.<fqdn>/<path>
• a status using kubectl via displaying relevant CRDs
• mapping of a ca-bundle
• repo-specific settings

Also

• an overall web interface
• settings which apply to all repo mirrors