Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-3110

Unique hostnames in a multi-cluster environment

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • None
    • None
    • qualified hostname
    • False
    • None
    • False
    • Not Selected
    • NEW
    • To Do
    • NEW

      Goals

      Make logging 'hostname' field unique in a multi-cluster setting by adding the cluster base domain: {{oc get dns.config.openshift.io/cluster -o jsonpath='

      {.spec.baseDomain}'}}

      Note this fully-qualified name is not resolvable, but it is a valid fully-qualified DNS name, and as unique as the base domain name of the cluster - internet unique if the cluster is in a valid internet domain.

      This feature is opt-in via a new ClusterLogForwarder field: pipeline.qualifyHostname: true

      h1. Non-Goals

      Host name is not resolvable or routable, only unique.

      h1. Motivation

      Many existing applications rely on hostnames DNS names as unique identifiers. In a multi-cluster setting, hostnames may be re-used in separate clusters. Adding the cluster's base-domain restores uniqueness.

      h1. Alternatives

      Use the separate cluster-id field. This is feasible but requires modification of existing apps that assume host names are unique.

      h1. Acceptance Criteria

      Tests for adding domain.

      h1. Risk and Assumptions

      Assumes {{oc get dns.config.openshift.io/cluster -o jsonpath='{.spec.baseDomain}

      '}}

      is a valid DNS domain.

      Documentation Considerations

      Requires documentation

      Open Questions

      None

      Additional Notes

      None

              Unassigned Unassigned
              rhn-engineering-aconway Alan Conway
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: