# Understanding use cases behind k8s and openshift inventory design

**URL:** <https://forum.ansible.com/t/understanding-use-cases-behind-k8s-and-openshift-inventory-design/30830>\
**Category:** Ansible Project\
**Tags:** kubernetes\
**Created:** [July 20, 2019, 4:39pm UTC](https://forum.ansible.com/t/understanding-use-cases-behind-k8s-and-openshift-inventory-design/30830 "2019-07-20T16:39:02Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andrew\_Feller](https://avatars.discourse-cdn.com/v4/letter/a/7ea924/32.png) [@Andrew\_Feller](https://forum.ansible.com/u/Andrew_Feller)\
**Post date:** [July 20, 2019, 4:39pm UTC](https://forum.ansible.com/t/understanding-use-cases-behind-k8s-and-openshift-inventory-design/30830/1 "2019-07-20T16:39:02Z")

</div>

I’ve been working on an Ansible role to facilitate managing OpenShift projects, secrets, etc for applications under the notion that projects correlate to inventory hosts similar to what k8s and openshift inventories generate. I can model inventories of projects across multiple clusters and facilitate customizing each to a fair extent, however I’ve come up short when asked about why this approach versus some homegrown data structure and loading var files.

I’d appreciate anyone who’s used these inventories can share how this approach offers objective benefits.