Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-20653

[7.4.beta][OpenShift][Docs] Configuring DNS_PING service should include "publishNotReadyAddresses": true

    XMLWordPrintable

Description

    See also https://issues.jboss.org/browse/CLOUD-3017

    The Configuring DNS_PING chapter https://doc-stage.usersys.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.2/html-single/getting_started_with_jboss_eap_for_openshift_container_platform/#configuring_dns_ping

    should be updated with the new publishNotReadyAddresses property (should be set to true), which replaces the "service.alpha.kubernetes.io/tolerate-unready-endpoints" annotation used in older OCP versions.

    We should recommend using both service.alpha.kubernetes.io/tolerate-unready-endpoints annotation and publishNotReadyAddresses: true so it works in both the older and newer OCP versions (the current EAP 7.2 templates use both )

    kind: Service
    apiVersion: v1
    spec:
        publishNotReadyAddresses: true
        clusterIP: None
        ports:
        - name: ping
          port: 8888
        selector:
            deploymentConfig: eap-app
    metadata:
        name: eap-app-ping
        annotations:
            service.alpha.kubernetes.io/tolerate-unready-endpoints: "true"
            description: "The JGroups ping port for clustering."
    

    Attachments

      Issue Links

        Activity

          People

            snelluli@redhat.com Sreelatha Nelluli
            snelluli@redhat.com Sreelatha Nelluli
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: