Uploaded image for project: 'Machine Config Operator'
  1. Machine Config Operator
  2. MCO-1231

Use Kubernetes Job objects for image builds

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • MCO Sprint 259, MCO Sprint 260, MCO Sprint 261, MCO Sprint 262
    • 0
    • 0.000

      Currently, we are using bare pod objects for doing our image builds. While this works, it makes adding retry logic and other things much more difficult since we will have to implement this logic. Instead, we should use Kubernetes Jobs objects.

      Jobs have built-in mechanisms for retrying, exponential backoff, concurrency controls, etc. This frees us from having to implement complicated retry logic for build failures beyond our control such as pod evictions, etc.

       

      Done When:

      • BuildController uses Kubernetes Jobs instead of bare pods to perform builds.
      • All tests have been updated.

              umohnani Urvashi Mohnani
              zzlotnik@redhat.com Zack Zlotnik
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: