Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gitlab-runner gitlab-runner
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 2,506
    • Issues 2,506
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 122
    • Merge requests 122
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • gitlab-runnergitlab-runner
  • Issues
  • #27215
Closed
Open
Issue created Nov 11, 2020 by Steve Azzopardi@steveazzMaintainer

Create readiness probes for services in kubernetes executor

Overview

The user can specify services for their jobs. These services can be databases, webservers, anything they want. This service is needed to run the job of the user for example tests. The service might take a while to boot up and be ready and can cause a flaky scenario where the job fails because the service hasn't started yet. We need to provide some mechanism so that the user script doesn't start until all the services are ready.

Proposal

We can use a combination of readiness probes and the new probe syntax so that the user can specify when a service is ready to accept traffic. If we use kubernetes readiness probes that would mean that the pod will not be marked as "ready" until the readiness probe is successful, so the user script won't start running until then.

Assignee
Assign to
Time tracking