Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab Chart GitLab Chart
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 652
    • Issues 652
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 41
    • Merge requests 41
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • charts
  • GitLab ChartGitLab Chart
  • Issues
  • #37
Closed (promoted) (promoted)
Open
Issue created Nov 14, 2017 by Joshua Lambert@joshlambertDeveloper

GitLab Pages Cloud Native support

Pages currently requires shared NFS-like storage to function. This is not available in our Kubernetes deployments, the only shared storage we have is Object Storage.

So in order for Pages to be available in the Kubernetes deployment of GitLab, it needs to support Object Storage.

The epic currently tracking the Release Management team portion of this effort is here: gitlab-org&1316 (closed).

There are a number of steps we can take to reach cloud native support for Pages.

  1. Resolve the known blockers identified in gitlab-org&4283 (closed)
  2. Create a Pages container that can be used to identify additional blockers
  3. Add Pages configuration to Rails containers
  4. Document an experimental hybrid deployment as an interim solution. This would use Omnibus to deploy Pages and Helm to deploy other GitLab services. This documentation could be made available after .com has deployed and proven out the hybrid approach cc @awthomas
  5. Create a Helm chart for Pages

Note: this is a multi layer project - ~"group::release management" is working on the first phase which is research of serving the pages files from a url and then we will build the new object storage. Finally, groupdistribution can take that and make it possible to deploy. It would be foolish for me to give you a date but we are hopeful for end of year, 2020.

Edited Aug 31, 2020 by Steven Wilson
Assignee
Assign to
Time tracking