Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • See what's new at GitLab
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab FOSS
GitLab FOSS
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 5
    • Merge Requests 5
  • Requirements
    • Requirements
    • List
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #58941

Closed
Open
Opened Mar 14, 2019 by Daniel Gruesso@danielgruesso🌀Maintainer

Use GitLab serverless with existing Knative installation

Problem to solve

Currently, the serverless features is enabled when a knative deployment via GitLab k8s integration is detected, however, if I bring an existing cluster that already has knative deployed to it, I cannot take advantage of all the great features of GitLab serverless.

Further details

Proposal

When an existing cluster is added, detect the presence of Knative and enable cluster to be used with all the existing features of GitLab serverless.

Considerations:

  1. Will need to detect knative installation (perhaps look for knative-serving namespace)
  2. Will need to detect istio installation (istio-subsystem namespace)
  3. Will need to detect domain name if any
  4. Will need to offer the ability to input domain name if one does not exist

Ability to add or change domain will mimic current UI/UX:

Screen_Shot_2019-03-28_at_12.33.32_PM

Permissions and Security

Documentation

What does success look like, and how can we measure that?

Links / references

Edited Apr 03, 2019 by Daniel Gruesso
Assignee
Assign to
12.0
Milestone
12.0 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab-foss#58941