Etcd version 3.1.12 always gets installed, even when overriden about puppetlabs-kubernetes HOT 4 CLOSED

There is a limitation when substituting variables in the params.pp. We received some negative feedback about the way we were hardcoding the etcd archive and source for users using air-gapped systems or wanted to use an internal repo

At the moment you can get around this by hardcoding the full archive and source url with the version you want.

We considered putting this into the kubetool and having it generated as part of the hiera, but equally there seems to have been some criticism about the reliance on kubetool for this module.

Happy to take a WIP PR to clean it up, or discuss further what might be a more viable option.

from puppetlabs-kubernetes.

I first noticed this when trying to bootstrap a cluster on our production systems, but I managed to reproduce it on a local Vagrant box. The info above is of the Vagrant environment.

from puppetlabs-kubernetes.

@davejrt Thank you for your response. I hardcoded the archive and source URL and it works like a charm.
I might open a PR with a proposal for cleaning things up a bit. I was thinking about adding a flag for enabling/disabling the management of Etcd via this module

from puppetlabs-kubernetes.

I'm going to close this issue, any further discussions we can have on the community slack or a PR.

from puppetlabs-kubernetes.