Upgrading to latest memcached image which uses debian buster

[adusumillipraveen]

Moving to latest image as debian stretch has vulnerabilities( which our CSP keeps warning us about ) and also because it has other advantages.

[2opremio]

I think it may be better to drop the patch version number and simply use 1.5. Mutable tags are an anti-pattern, but ensuring implicit patch upgrades through semver is probably worth it (we already do it, intentionally or not, when building our Alpine-based Flux image).

@squaremo thoughts?

[squaremo]

I think it may be better to drop the patch version number and simply use 1.5

You can certainly do that for a particular installation; that's an easier decision to endorse than making it so for everyone.

[2opremio]

Actually, after thinking about it further, it's not like we do when building Flux. The base image used by Flux is immutable but it's always the same when deploying (so, you cannot end up with different images when re-deploying, for instance).

[2opremio]

LGTM (after reverting the chart change)

[2opremio]

I had to regenerate pkg/install/generated_templates.gogen.go and push it to master directly (see d16d92e) because this missed it.

It should had been automatically detected by CI, but make check-generated didn't work in the latest build of this PR (https://circleci.com/gh/fluxcd/flux/8813 ) nor in the merge build in master ( https://circleci.com/gh/fluxcd/flux/8819 )

I noticed when working on a later, unrelated PR (#2626 ) for which make check-generated did work ( https://circleci.com/gh/fluxcd/flux/8826 ). Why that happen is beyond me at this point.