Uploaded image for project: 'Marathon'
  1. Marathon
  2. MARATHON-1717

healtheck on custom ports in host mode doesn't work

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Medium
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Health & Readiness
    • Labels:

      Description

      The doc says:

      > For MESOS_HTTP, MESOS_HTTPS, MESOS_TCP, TCP, HTTP and HTTPS health checks, either port or portIndex may be used. If none is provided, portIndex is assumed. If port is provided, it takes precedence overriding any portIndex option.

      However it fails to deploy when only port is specified, and not portIndex:

      "Health check port indices must address an element of the ports array or container port mappings."
      

      It works if I set portIndex: 0 and then override it with port: X, but that's likely not expected behaviour.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                GitHub_vavrusa Marek V (Inactive)
                Team:
                Orchestration Team
                Watchers:
                Ken Sipe
              • Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: