image-automation-controller icon indicating copy to clipboard operation
image-automation-controller copied to clipboard

Published 20 hours ago • verified publisher icon fluxcd

Explicit relation between ImagePolicy and ImageUpdateAutomation

Open tun0 opened this issue 2 years ago • 1 comments

Scenario:

Application consisting of a combination in-house developed software (think: PHP application) and third-party software (think: Elasticsearch, Redis, etc). For the in-house developed stuff, we want IUA to actively deploy the latest versions based on ImagePolicies. For third-party stuff, we want IUA to create branches/PRs based on ImagePolicies.

Current workarounds:

  • Hard separation between in-house and third-party stuff directory-wise, and have specific ImageUpdateAutomation resources pointing at those respective directories.
  • Separate them by using different namespaces for both instead.

Suggested solution:

Think: Ingress classes In each ImagePolicy you explicitly (with perhaps some optional default) configure which ImageUpdateAutomation is supposed to "process" this ImagePolicy.

tun0 avatar Mar 21 '23 14:03 tun0