Skip to content

Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
    • Insights
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 23,588
    • Issues 23,588
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 834
    • Merge Requests 834
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Security & Compliance
    • Security & Compliance
    • Dependency List
  • Packages
    • Packages
    • Container Registry
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLabGitLab
  • Merge Requests
  • !3539

Closed
Opened Nov 23, 2017 by Matija Čupić@matteeyah4 of 8 tasks completed4/8 tasks
  • Report abuse
Report abuse

WIP: Resolve "Support multiple Kubernetes cluster per project"

What does this MR do?

Are there points in the code the reviewer needs to double check?

Did I put the ClustersHelper in the correct place? Since it's EE only.

Why was this MR needed?

N/A

Screenshots (if relevant)

N/A

Does this MR meet the acceptance criteria?

  • Changelog entry added, if necessary
  • Documentation created/updated
  • N/A API support added
  • Tests added for this feature/bug
  • Review
    • N/A Has been reviewed by UX
    • N/A Has been reviewed by Frontend
    • Has been reviewed by Backend
    • N/A Has been reviewed by Database
  • Conform by the merge request performance guides
  • Conform by the style guides
  • Squashed related commits together
  • N/A Internationalization required/considered
  • If paid feature, have we considered GitLab.com plan and how it works for groups and is there a design for promoting it to users who aren't on the correct plan

What are the relevant issue numbers?

Closes #3734 (closed)

Edited Nov 24, 2017 by Matija Čupić

Check out, review, and merge locally

Step 1. Fetch and check out the branch for this merge request

git fetch origin
git checkout -b "3734-support-multiple-kubernetes-cluster-per-project" "origin/3734-support-multiple-kubernetes-cluster-per-project"

Step 2. Review the changes locally

Step 3. Merge the branch and fix any conflicts that come up

git fetch origin
git checkout "origin/master"
git merge --no-ff "3734-support-multiple-kubernetes-cluster-per-project"

Step 4. Push the result of the merge to GitLab

git push origin "master"

Note that pushing to GitLab requires write access to this repository.

Tip: You can also checkout merge requests locally by following these guidelines.

  • Discussion 6
  • Commits 12
  • Pipelines 3
  • Changes 12
Assignee
Assign to
10.3
Milestone
10.3
Assign milestone
Time tracking
12
Labels
CI/CD [DEPRECATED] Deliverable Enterprise Edition GitLab Premium UX ready [DEPRECATED] customer+ deploy direction feature frontend kubernetes workflow::In dev
Assign labels
  • View project labels
Reference: gitlab-org/gitlab!3539