https://www.puppet.com/community logo
Join Slack
Powered by
# voxpupuli
  • v
    Ananace: does it do anything differently/better than the puppetlabs/kubernetes module?
  • v
    bastelfreak: It actually sets up a Kubernetes cluster, instead of just running a bunch of `exec`s against kubeadm
  • v
    bastelfreak: Basically, the puppetlabs-kubernetes/kubeadm method had far too many concessions for the university's usage, so the k8s module is a lower-level one that manages the components directly instead
  • d
  • v
    sounds nice
  • v
    For reference; https://github.com/ananace/puppet-k8s/ - currently running three clusters on it, with different sizes
  • s
    This message was deleted.
    m
    b
    • 3
    • 8
  • m
    hey 👋 ! I try to push this one again (reason being, it's not a feature request, but it's currently broken): https://github.com/voxpupuli/puppet-ipset/pull/66
  • j
  • m
    hey 👋 I try to push this one again (reason being, it's not a feature request, but it's currently broken): https://github.com/voxpupuli/puppet-ipset/pull/66
  • v
    maxadamo: I fixed same bug here - https://github.com/pmuller/puppet-ipset/pull/9 , should migrate the voxpup one.
  • v
    bastelfreak: want an nftables release now?
  • v
    yes please :)
  • v
    just found MR so yes.
  • v
    the design of our puppet-yum repo is a bit... unintuitive
  • d
  • v
    what's the easiest way to manage just one default repo
  • v
    I don't use puppet-yum to manage repos, if I were managing repos I would just use yumrepo directly
  • d
  • v
    I was hoping it's less hazzle with our module
  • v
    I'd only use the yum module if I needed to manage config
  • v
    that said, if the upstream provides a release rpm, I'm also quite likely to just install the release rpm... unless I am at work, then it all goes into katello/foreman and we just use a subscription-manager module to manage all of it
  • v
    actually I just need to enable the powertools default repo, for borgbackup
  • v
    ahhhhhhhh this puppetserver
  • v
    fiddling around for half an hour, then remembering that I've to clean the environment cache...
  • v
    curl -i --cert $(puppet config print hostcert) --key $(puppet config print hostprivkey) --cacert $(puppet config print cacert) -X DELETE https://$(puppet config print server):8140/puppet-admin-api/v1/environment-cache?environment=production <3
  • v
    the puppetserver command should have support for that IMHO
  • v
    yes, that would be nice
  • v
    and there are a few more api endpoints that I would like to see in the cli
  • v
1...979899...648Latest