Best practice proposal: avoid static reference to external resources

[tomkivlin]

Instead look to use dynamic approaches, e.g. labels.

• Don’t statically configure network addresses for example
  • https://github.com/cncf/cnf-certification/blob/main/docs/CNFCertification-1.0-beta.md#hardcoded-ip-addresses-in-k8s-runtime-configuration
  • https://github.com/cncf/cnf-testsuite/blob/main/RATIONALE.md#to-test-if-there-are-any-non-declarative-hardcoded-ip-addresses-or-subnet-masks-in-the-k8s-runtime-configuration-hardcoded_ip_addresses_in_k8s_runtime_configuration
• Don't reference external resources by static name (in case names change over hosts) - use labels / features / etc.

Need to be clear about what is dynamic configuration vs hard-coded static configuration.

[tomkivlin]

Created a google doc to act as a working document for anyone looking to add content to just some sections: https://docs.google.com/document/d/1FbEeaF9ztJecWaVekQ4pm2JvkJLOyoI5nzevGXcD9sE/edit?usp=sharing

[taylor]

Keep. good first issue