Skip to content

GitLab Next

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 2
    • Merge requests 2
  • Requirements
    • Requirements
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Code review
    • Insights
    • Issue
    • Repository
    • Value stream
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #58941

Closed
Open
Created Mar 14, 2019 by Daniel Gruesso@danielgruessoContributor

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
Time tracking