Not aware of any changes between 6 and 7

odd

This might be a dumb question, but does anyone know if this is supported by PE? https://github.com/puppetlabs/puppetserver-helm-chart

This might be a dumb question, but does anyone know if this is supported by PE? https://github.com/puppetlabs/puppetserver-helm-chart

Putting Puppet Enterprise in K8s would be pretty cool

supported as in works or as in you get payed help by Puppet?

running it in kubernetes/containers works. for FOSS Puppet there are some recorded talks on youtube and pubished containers. they might exist for PE as well

Kubernetes isn’t a supported deployment architecture for PE at this time. It’d be nice, especially for auto-scaling and auto-recovery, but there’s a lot of “state” in PE that would have to be adapted for containerized deployment. So, it’s not a matter of just installing some packages in a container image and heading off the races.

Yeah, makes sense. Supported as in works and getting support if there are issues. We do have PE already, but just looking at other ways to scale.

This message was deleted.

i'm hoping the answer is "yes", maybe if dependabot starts screaming about how outdated our puppet code is, management will finally let me finish re-structuring things so we can upgrade away from PE 2016.2.0

nope it doesnt

nope it doesnt

but you can easily scan them by yourself

Started but not merged

https://github.com/voxpupuli/ra10ke haa some rake tasks to check you Puppetfile

https://github.com/voxpupuli/ra10ke haa some rake tasks to check you Puppetfile

hrmmm... i was hoping the answer would be "yes". i've been trying since august 2016 to make management let me spend the time it would take to re-organize our puppet modules from being jammed together in three git repos, to each having their own git repo, so i can start using

r10k

and have a

Puppetfile

to scan from.

they're paying for a several hundred seat PE license and i'm not even able to open support tickets, because as soon as somebody at puppet sees "PE 2016" their first, last, and only response is "you need to upgrade, we can't support that anymore".

i've gotten pretty good at working around this, including writing my own script that builds environment directories instead of

r10k

, which knows about our three specific repos, but i keep trying to find ways to convince managment to let me switch everything over so i can do it "the right way".

anyway, i'm ranting here ... i guess thanks for listening? it's 1730 here in florida, i'm calling it ... have a good evening all

Thinking out loud here, but you could probably use a scheduled github action to run OnceOver to display your modules and which are out of date. Maybe you can write something to create an issue or something if a module is outdated

Thinking out loud here, but you could probably use a scheduled github action to run OneOver to display your modules and which are out of date. Maybe you can write something to create an issue or something if a module is outdated

Thinking out loud here, but you could probably use a scheduled github action to run OnceOver to display your modules and which are out of date. Maybe you can write something to create an issue or something if a module is outdated

Thinking out loud here, but you could probably use a scheduled github action to run OnceOver to display your modules and which are out of date. Maybe you can write something to create an issue or something if a module is outdated

Thinking out loud here, but you could probably use a scheduled github action to run OnceOver to display your modules and which are out of date. Maybe you can write something to create an issue or something if a module is outdated

we also have https://github.com/ekohl/metadata_json_deps to scan metadata.jsom for outdazed deps

we also have https://github.com/ekohl/metadata_json_deps to scan metadata.jsom for outdazed deps