Bootstrap an OpenShift conventions document for the project

[jwforres]

No description provided.

[smarterclayton]

Developers of the platform expect this consistency in the code to quickly identify issues across codebases.

Maybe a comment too about how consistency simplifies explanation, reduces accidental complexity.

[jwforres]

cc @derekwaynecarr @markmc @crawford @eparis @russellb since your names are on it as authors / approvers / reviewers

[derekwaynecarr]

we can add this as a follow-on PR, but I want to capture outcomes for some discussions.

When should an operand tolerate all taints?

1. if the operand is required to form a functional Kubernetes node
2. if the operand is required to support workloads sourced from an internal or external registry that core components depend upon

An operand that tolerates all taints must implicitly tolerate in their component:

1. a node that is not configured by an external cloud provider
2. a node whose network is not configured

/cc @Miciah - i think this covers what we discussed.

[jwforres]

@derekwaynecarr yeah lets do that in a follow-on, it will need a new section

[smarterclayton]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jwforres, smarterclayton

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [jwforres,smarterclayton]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment