Readme elaboration

[jlgrock]

Few major issues that I would like clarification on so I can help provide feedback and use this as well

• TPDK is not a well known acronym (please, try googling). Please expand acronym and/or link to the associated reference.
• This states that it is a TPDK plugin. I believe this is a Koffer plugin, not a TPDK plugin, but am definitely not sure. Please clarify.
• Doesn't actually say what the plugin does.

[usrbinkat]

Thank you for enumerating questions that should be answered by docs as they mature. The best maintained source for documentation can be found on the codectl.io website.

You are right that Trusted Platform Delivery Kit or TPDK (Koffer + CloudCtl) includes Koffer and the sparta iac is Koffer compliant.

Sparta iac is also CloudCtl compliant meaning that koffer can run against the repo low side (internet connected) and the resulting "bundle" can leverage CloudCtl during deploy time high side.

To be transparent with our current state I'll elaborate on the state of TPDK/Koffer/ShipperD which represent an end to end reference framework and disconnected distribution spec prototype.

These framework connections & specs are under heavy development at this time. As of this week we were able to complete our evaluation of existing roadmaps under way across other community projects intended to establish standard practices in overcoming the disconnected / airgap use case.

With the evaluation complete we also did a proof of concept viability test based on our observations and a prototype architecture for both deploy time needs as well as post-deploy day2+ operations.

You can read about this path forward on the ShipperD README.

This protype & roadmap planning was necessary before taking on the big picture documentation tasks. As the bundle spec itself impacts everything from day zero to final sunset of a platform deployment, we have primarily focused effort on field testing, enhancement, and lifecycle evaluation testing on this crux of the framework before writing a mature set of documentation around capabilities and flexibility exposed by the spec.

Going forward please feel free to engage directly on the brand new CodeCtl Slack channel. Our comms are mostly still all over Red Hat internal platforms but we are making headway into opening that up for closer community integration.

Please keep an eye out for new documentation updates as the overhaul starts rolling out over the next couple of months.