Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-74176

Cluster DNS operator caching upstream aligned documentation

    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • None
    • All
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      OCP CoreDNS documentation on caching improved alignment for undestanding of the phrase caching.

      Version-Release number of selected component (if applicable):

      4.x

      How reproducible:

      Everytime  

      Steps to Reproduce:

      Reading the documentation of OpenShift CoreDNS caching setting in the DNS operator is misleading Customers on what caching in that sense means.

      Actual results:

      Setting the DNS operator cache leads to misunderstood behavior.     

      Expected results:

      As documented in https://issues.redhat.com/browse/OCPBUGS-62919 by Engineering Management, following additional statement could be provided in our docs to clarify on the expected behavior of setting a DNS operator cache values in OpenShift
      
      A user can shorten the TTL of the DNS record by setting a lower positive cache but they cannot increase the TTL on the DNS record by setting a higher positive cache. The maximum cache is the lower of the TTL of the DNS record or the positive cache.

      Additional info:

          

              jmanthei@redhat.com Jessica Manthei
              rhn-support-milang Michaela Lang
              None
              None
              Hongan Li Hongan Li
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: