Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • ink-api ink-api
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • INK
  • ink-apiink-api
  • Issues
  • #63

Closed
Open
Created Jan 23, 2018 by Sam Galson@g-samMaintainer

Decouple ink and sideqik

Currently ink and sideqik need to share a volume. While I'm not sure what the thinking was behind how ink would scale up for multiple workers it seems like a shared volume might inhibit this. The classic pattern would be to use something like s3 for file storage and share references to files stored on s3.

Until this is fixed ink and sideqik will need to be run in the same pod or use AWS EFS. This is not natively supported by kubernetes but an addon is here.

Edited Jan 24, 2018 by Sam Galson
Assignee
Assign to
Time tracking