Skip to content
GitLab
Next
Menu
Why GitLab
Pricing
Contact Sales
Explore
Why GitLab
Pricing
Contact Sales
Explore
Sign in
Get free trial
Primary navigation
Search or go to…
Project
gitlab-runner
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Privacy statement
Keyboard shortcuts
?
What's new
4
Snippets
Groups
Projects
Show more breadcrumbs
GitLab.org
gitlab-runner
Commits
d03ea54b
There was a problem fetching the pipeline summary.
Commit
d03ea54b
authored
7 years ago
by
Tomasz Maczukin
Browse files
Options
Downloads
Plain Diff
Merge branch 'patch-7' into 'master'
support private registries with Kubernetes Closes
#1957
See merge request
!551
parents
8e5d3d6b
a2af73b4
No related branches found
No related tags found
Loading
Pipeline
#
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/configuration/advanced-configuration.md
+0
-1
0 additions, 1 deletion
docs/configuration/advanced-configuration.md
with
0 additions
and
1 deletion
docs/configuration/advanced-configuration.md
+
0
−
1
View file @
d03ea54b
...
...
@@ -209,7 +209,6 @@ This will use `/path/to/bind/from/host` of the CI host inside the container at
support for using private registries, which required manual configuration
of credentials on runner's host. We recommend to upgrade your Runner to
at least version
**1.8**
if you want to use private registries.
-
Private registries are currently not supported by the Kubernetes executor.
-
Using private registries with the
`if-not-present`
pull policy may introduce
[
security implications
][
secpull
]
. To fully understand how pull policies work,
read the
[
pull policies documentation
](
../executors/docker.md#how-pull-policies-work
)
.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment