XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Obsolete
    • Icon: Major Major
    • OSSM 3.0-TP2
    • None
    • Sail Operator
    • None
    • Automatic upgrades
    • False
    • None
    • False
    • Done
    • 100% To Do, 0% In Progress, 0% Done

      A feature of operators and OpenShift in general, is support for automated upgrades to ensure that applications have the latest security updates without the need for human intervention. Most (all?) other layered products support this, though they have a simpler operand and don't have to deal with restarting proxies. Still, it is a feature we should offer, while giving users options on how automatic they want to make it.

      For example:

      • Distinguish between minor and patch versions. It is more likely that a use would want to apply automatic upgrades to patch versions, while doing a manual minor version update... though some may also want to automate minor upgrades.
      • Automatically restart proxies or not? I assume most updates would require a pod restart to update the proxy. This could have an automatic option, which may be acceptable if the workload has enough replicas to ensure that there are no interruptions during a rollout/restarts.

              Unassigned Unassigned
              dgrimm@redhat.com Daniel Grimm
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: