It's a good idea to focus on the RHCOS content first as that should be the priority first.
Since Kubernetes is the orchestration engine for worker nodes, RHEL content should exist under the OCP product as Kubernetes will be manage everything. Just like the CoreOS content is done right now. On Tue, Mar 17, 2020 at 12:33 PM Jakub Hrozek <[email protected]> wrote: > On Tue, Mar 17, 2020 at 05:15:23PM +0100, Marek Haicman wrote: > > Good question :) I'd say RHEL8 in OCP cluster should be derivative > > (extension in CaC terms) of the main content. As every difference should > be > > clearly visible, and number of differences minimized. > > OK, we talked about this a bit on chat with Ozz and decided to wait and > see what the actual differences are between the content. Given our time > constraints it is unlikely that we would start working on RHEL content > sooner than in a couple of weeks anyway, so we'll keep polishing the > RHCOS content first to get a better idea. > > Thank you for the discussion nonetheless, it's very useful. > _______________________________________________ > scap-security-guide mailing list -- > [email protected] > To unsubscribe send an email to > [email protected] > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedorahosted.org/archives/list/[email protected] >
_______________________________________________ scap-security-guide mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/[email protected]
