Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-1648

Don't hardcode openshift.DNS_PING service name

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Major
    • 7.5.0.CR2
    • 7.5.0.CR1
    • container image
    • None
    • Documentation (Ref Guide, User Guide, etc.), Release Notes
    • AMQ Broker 1833

    Description

      User Story:

      As a System Administrator

      I would like to be able to configure the DNS Service to use different protocols and ports etc

      so that I can have more than 1 AMQ 7 Clusters within the same Openshift namespace

      More Info:

      As there is no technical reason why it shouldn't be possible to have two separate AMQ clusters in the same namespace, the DNS ping service should not be hardcoded to "ping" , but instead be parameterized in the templates

      Also, the ping service name should be prefixed by ${APPLICATION_NAME}- in the templates, so that it is possible to instantiate the template more than once for separate clusters in the single namespace.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. CLOUD-2662 [AMQ7] don't hardcode openshift.DNS_PING service name

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-2778 Secret credential name not dynamic preventing multiple deployments per project namespace

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-2875 Static headless and ping service names prevent more than one custom resource instance per namespace

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. ENTMQBR-1857 Document 7.5 Operator: Document don't hardcode openshift.DNS_PING service name

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQBR-2980 Ensure name and label generation works for the multi-statefulset case

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JGRP-2363 DNS Ping cannot lookup SRV record for service port

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-4029 Different exceptions related to DNS SRV raised at the startup of the broker

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. ENTMQBR-3400 Doc: [OCP] Ensure name and label generation works for the multi-statefulset case

          • Critical - To be worked on immediately following BLOCKER issues.
          • New

          Activity

            People

              gaohoward Howard Gao
              maschmid@redhat.com Marek Schmidt
              Roman Vais Roman Vais
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 4 hours
                  4h
                  Remaining:
                  Remaining Estimate - 4 hours
                  4h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified