The Registry Proxy module helps ensure security compliance for organizations with strict security policies, for which exposing an internal Docker registry to the public internet is not acceptable.
With the Registry Proxy module, you can set up a managed connection between kubelet and the Connectivity Proxy service inside your Kyma cluster. Combined with a properly configured SAP Cloud Connector targeting your on-premises Docker registry, you can run workloads in your Kyma cluster using container images hosted on your own infrastructure without exposing your internal registry directly to the internet.
Ensure that the kyma-system namespace exists:
kubectl create namespace kyma-system | trueDownload the registry-proxy-operator.yaml and default-registry-proxy-cr.yaml manifests from the latest release.
Apply registry-proxy-operator.yaml to install Registry Proxy Operator:
kubectl apply -f registry-proxy-operator.yamlTo get Registry Proxy installed, apply the sample Registry Proxy CR:
kubectl apply -f default-registry-proxy-cr.yaml- Go version v1.22.0+
- Docker version 17.03+.
- kubectl version v1.11.3+.
- Access to a Kubernetes v1.11.3+ cluster.
// TODO(user): Add detailed information on how you would like others to contribute to this project
NOTE: Run make help for more information on all potential make targets
More information can be found via the Kubebuilder Documentation