Skip to content

GitLab Next

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

Closed
Open
Created Nov 02, 2020 by Thong Kuah@tkuahDeveloper

Have a dedicated sub-domain for kas address

Drop /-/kubernetes-agent, and setup kas.<gitlab-host> for Agent

In charts gitlab-org/charts/gitlab#2373 (closed), we are shifting to a separate sub-domain for the kas listen address. Do the same for Omnibus.

Do we need this for GitLab.com rollout ?

No

Why do we want to do this ?

To match charts, for consistency

/cc @mattkasa @nicholasklick

Edited Nov 09, 2020 by Thong Kuah
Assignee
Assign to
Time tracking