Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-4853

Research spike for bringing Container template API to KogitoService interface

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • 1.4.0.Final
    • Operator
    • None
    • False
    • False
    • Undefined

      See KOGITO-4741 for context.

      Users might have specifics requirements for how the application container/pod spec needs to be created in their cluster. KOGITO-4741 is one of them. Another good reference for this scenario is https://github.com/m88i/nexus-operator/issues/28.

      Instead of cherry-picking these attributes and adding them to our interface, it would be better to expose the entire container spec, similarly to what Knative Serving already does: https://knative.dev/docs/serving/getting-started-knative-app/#creating-your-deployment-with-yaml.

              vajain Vaibhav Jain
              rhn-support-zanini Ricardo Zanini
              Karel Suta Karel Suta
              Karel Suta Karel Suta
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: