Currently, all docs in the building-operators section are separated by type (golang, ansible, helm). Some of the advice (crd scope, operator scope, maybe some others) are generally applicable, or contain subsections that could be applied to different types. As a follow-up to #4812 and #4699 it would be nice to bring those up to the base building operators dir, and add some headings to the subsections to identify which types they work with (e.g. in crd scope say that setting the scope at the types.go level is best for golang operators, and at the crd yaml level for other operator types).
Currently, all docs in the building-operators section are separated by type (golang, ansible, helm). Some of the advice (crd scope, operator scope, maybe some others) are generally applicable, or contain subsections that could be applied to different types. As a follow-up to #4812 and #4699 it would be nice to bring those up to the base building operators dir, and add some headings to the subsections to identify which types they work with (e.g. in crd scope say that setting the scope at the types.go level is best for golang operators, and at the crd yaml level for other operator types).