Uploaded image for project: 'Managed Service - Streams'
  1. Managed Service - Streams
  2. MGDSTRM-10249

Set ExpiresAt on Kafka creation for developer instances

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • 3
    • False
    • None
    • False
    • No
    • MGDSRVS-341 - Enable customers to evaluate OpenShift Application Services
    • ---
    • ---
    • MK - Sprint 230

      WHAT

      Set ExpiresAt value during Kafka creation if lifespanSeconds is defined for the requested Kafka instance type.

      WHY

      expires_at is immediately returned with a value for developer instances on create. If we don't set this during Kafka create, the expires_at will be empty for a few moments until the reconciler sets it.

      We need to set this during Kafka creation to keep the existing behaviour.

      HOW

      Set the kafkaRequest.ExpiresAt value during Kafka creation when the lifespanSeconds is defined for the requested Kafka instance type.

      Note that this currently only applies for developer instances (lifespanSeconds is set for this instance type). This currently cannot apply for long lived eval instances as its not possible to know when a user/organisations subscription expires in advance.

      DONE

      • ExpiresAt is set during Kafka creation
      • Unit/Integration tests updated if necessary

              msorianod Miguel Soriano
              jbriones@redhat.com Jameel Briones
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: