Add smart-proxy mTLS auth for container registry#11776
Conversation
Allow smart-proxies to pull/push container images against Katello's registry using their existing Foreman SSL client certificate. A new `container_registry_auth_enabled` flag on SmartProxy opts proxies in explicitly. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
what do you think about this @ianballou - its a PR to start the discussion. |
|
I've personally never come up with a reason to push content from a smart proxy into Katello, only the other way around. At the moment I can't think of a reason why it would hurt, but I'm curious what Are the containers being built on the smart proxy and then pushed to Katello to redistribute them elsewhere? |
Yes, this is exactly the use case. :-) |
Allow smart-proxies to pull/push container images against Katello's registry using their existing Foreman SSL client certificate. A new
container_registry_auth_enabledflag on SmartProxy opts proxies in explicitly.Katello PR: #11776
Smart Proxy PR: theforeman/smart-proxy#948
Smart Proxy Ansible Director: ATIX-AG/smart_proxy_ansible_director#24
Note: I have created this PRs to discuss how to use the katello container registry with smart-proxies.