Skip to content
GitLab
Next
Projects
Groups
Snippets
Help
Loading...
Help
What's new
4
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
GitLab
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Locked Files
Issues
34,862
Issues
34,862
List
Boards
Labels
Service Desk
Milestones
Iterations
Merge Requests
1,208
Merge Requests
1,208
Requirements
Requirements
List
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Test Cases
Security & Compliance
Security & Compliance
Dependency List
License Compliance
Operations
Operations
Metrics
Incidents
Environments
Packages & Registries
Packages & Registries
Container Registry
Analytics
Analytics
CI / CD
Code Review
Insights
Issue
Repository
Value Stream
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
GitLab.org
GitLab
Merge Requests
!37459
Closed
Opened
Jul 21, 2020
by
Dan Davison
@ddavison
Maintainer
5 of 5 tasks completed
5/5 tasks
Options
Report abuse
Report abuse
Allow K3s provider to generate name and port
Overview
5
Commits
1
Pipelines
6
Changes
3
What does this MR do?
K3s provider will generate unique name and port to ensure that conflicts don't arise.
De-quarantine kubernetes_integration_spec.rb
Closes
#225315
Does this MR meet the acceptance criteria?
Conformity
[-]
Changelog entry
Documentation
(
if required
)
Code review guidelines
Merge request performance guidelines
Style guides
Database guides
[-]
Separation of EE specific content
Edited
Sep 25, 2020
by
Dan Davison
👍
0
👎
0