vbatts/quay
Archived
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Add ability to restrict V1 push behind a namespace whitelist

Browse source 
Also enables the feature by default with an empty whitelist for QE

Fixes https://jira.coreos.com/browse/QUAY-1342
This commit is contained in:
Joseph Schorr 2019-03-05 16:50:56 -05:00
parent d3dd2f7b7c
commit b86d389c8e
9 changed files with 99 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

30
config_app/js/core-config-setup/config-setup-tool.html
View file

@ -1419,6 +1419,36 @@
</div>
</div> <!-- /Access settings -->
<!-- Registry settings -->
<div class="co-panel">
<div class="co-panel-heading">
<i class="fas fa-cog"></i> Registry Protocol Settings
</div>
<div class="co-panel-body">
<div class="co-alert co-alert-warning" style="margin-bottom: 20px">
Docker V1 protocol support has been <strong>officially deprecated</strong> by Quay and support will be
removed in the next major version. It is <strongly>strongly</strongly> suggested to have this
flag enabled and to restrict access to V1 push.
</div>
<div class="config-bool-field" binding="config.FEATURE_RESTRICTED_V1_PUSH">
Restrict V1 Push Support
</div>
<div class="help-text">
If enabled, Docker V1 push protocol will only be supported by those namespaces whitelisted
below. This feature should be left on unless <strong>general usage</strong> of the older
Docker V1 protocol is necessary.
</div>
<div ng-if="config.FEATURE_RESTRICTED_V1_PUSH" style="margin-top: 20px;">
<strong>Namespace whitelist:</strong>
<span class="config-list-field" item-title="Namespace" binding="config.V1_PUSH_WHITELIST"
item-pattern="[a-z0-9-]"></span>
<div class="help-text">
The list of namespaces in which V1 push is still enabled.
</div>
</div>
</div>
</div>
<!-- Build Support -->
<div class="co-panel">
<div class="co-panel-heading">