Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • magnum magnum
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 12
    • Issues 12
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Jira
    • Jira
  • Merge requests 7
    • Merge requests 7
  • 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
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • kuberneteskubernetes
  • magnummagnum
  • Merge requests
  • !221

Infere dns_service_ip from service_cluster_ip_range

  • Review changes

  • Download
  • Email patches
  • Plain diff
Open Radu Carpa requested to merge rcarpa/magnum:infere_dns_service_ip into cern/train Jan 13, 2023
  • Overview 3
  • Commits 2
  • Pipelines 0
  • Changes 4

when setting a custom service_cluster_ip_range label, the default cluster dns service ip (10.254.0.10) may end being outside the service IP range which results in DNS not working in the cluster.

Heat templates already support setting the needed variable. Automatically take the 10th ip address from the service range. This should fix the issue of DNS not working for people who set the service_cluster_ip_range label while keeping things unchanged for those who don't set it.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: infere_dns_service_ip