4 ms·

Check out https://github.com/skateco/skate https://github.com/skateco/skate I'm building it for exactly that reason. Multihost and supports k8s manifests.

• mdaniel 2y ago
  I'm not trying to yuck your yum, but you'll want to be _very careful_ about the uncanny valley of squatting on k8s manifests since there is a ton of functionality in those files and (as best I can tell) only by reading your readme can one tell which features actually work versus are just silently(?) swallowed
  • byrnedo 2y ago
    Yeah, you're right, I'd need to at least have some kind of table of supported attributes, or even mint my own schema with the subset that's valid for skate.
    • ttymck 2y ago
      Perhaps a tool that processes a k8s manifest and produces a modified manifest containing only the attributes that are supported?
      • byrnedo 2y ago
        You mean so the user can see themselves what will be applied?
        • ttymck 2y ago
          Sure. Looking at the output would make clear which properties are actually recognized, and it could be commited to version control to avoid confusion
  • byrnedo 2y ago
    I just remembered that a big reason I did this was because podman supports controlling pods directly via subset of some k8s resources manifests (podman kube play). Squatting, as you put it, on the same version. https://docs.podman.io/en/latest/markdown/podman-kube-play.1.html#podman-kube-play-support https://docs.podman.io/en/latest/markdown/podman-kube-play.1... I suppose I could tighten things up at my end anyway though.