Uploaded image for project: 'HPCC'
  1. HPCC
  2. HPCC-23303

Component level Fully qualified DNS names - Cloud

    XMLWordPrintable

Details

    • New Feature
    • Status: Accepted
    • Minor
    • Resolution: Unresolved
    • None
    • None
    • cloud, Init system
    • Minor
    • Not applicable
    • na

    Description

      To some degree this may be a tracking issue to follow and make sure the way we do kubernetes uses FQDNs as expected.  Or there may be separate work to be done.

      Automatically register fully qualified domain names for each component.

      These should be well defined names, for example not incorporating the pod instance so that we can logically build the dns name for any component.  In kubernetes these are probably service instances.

      So esp101.dataland.mydomain routes to that ESP even as the cloud environment and pod instances change.

      Open to ideas on what the FQDN actually looks like, but they should be built in a consistent manner.  I should be able to guess the FQDN by looking at the component name and other info in the topolgy.

      Needs investigation into bust practices for kubernetes and other cloud environments.

      Attachments

        Activity

          People

            Michael-Gardner Michael Gardner
            afishbeck Anthony Fishbeck
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: