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
  • #2229
Closed
Open
Issue created Mar 13, 2017 by James Goodhouse@jamesgoodhouse

Kubernetes executor should expose services via HostAliases

Description

Job services are always exposed on localhost instead of service name (or alias) when running on k8s.

Moving a working job definition form a docker executor to a k8s executor will likely fail if services are involved.

Proposal

If running on k8s >= 1.7 we should create Pods with HostAliases pointing each defined service to 127.0.0.1.

Links to related issues and merge requests / references

Adding entries to Pod /etc/hosts with HostAliases

https://gitlab.com/gitlab-org/gitlab-ce/issues/34419

Edited Jun 28, 2019 by Steve Azzopardi
Assignee
Assign to
Time tracking