Add example for Role, RoleBinding and Secret to configure BGP passwords

[paketb0te]

Product Version(s):
Calico

Issue:
fixes projectcalico/calico#6893

Link to docs preview:
CLICK

SME review:

• An SME has approved this change.

DOCS review:

• A member of the docs team has approved this change.

Additional information:

The Docs (in the reource definition for BGP peers) show that BGP Passwords must be stored in a Secret and then be referenced via the KeyRef (name of the secret and the key within that secret).

BUT it does not mention that this requires additional privileges for the calico-node ServiceAccount to access this secret.

It obviously makes sense if you think about it, but IMO it would make a lot of sense to mention that somewhere - see also @caseydavenport comments in projectcalico/calico#6893

I think the included example might be a bit over the top, maybe there is a way to make it show only partially by default and expand on click or something?

I am not exactly familiar with mdx unfortunately.

Merge checklist:

• Deploy preview inspected wherever changes were made
• Build completed successfully
• Test have passed

[netlify]

✅ Deploy Preview succeeded!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	8ed924f
🔍 Latest deploy log	https://app.netlify.com/sites/tigera/deploys/67866f899141c90008781956
😎 Deploy Preview	https://deploy-preview-1837--tigera.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 26 (🔴 down 1 from production) Accessibility: 90 (no change from production) Best Practices: 83 (no change from production) SEO: 92 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ Deploy Preview for calico-docs-preview-next ready!

Name	Link
🔨 Latest commit	8ed924f
🔍 Latest deploy log	https://app.netlify.com/sites/calico-docs-preview-next/deploys/67866f890c88d90008bb7c0d
😎 Deploy Preview	https://deploy-preview-1837--calico-docs-preview-next.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[ctauchen]

Thanks for this contribution, @paketb0te! I'll let @caseydavenport vet the technical side before I follow up with a docs review.

[ctauchen]

@caseydavenport I expect this new information would be universal. Am I right thinking we should eventually pick these changes to all products / versions?

[caseydavenport]

I think we want to default to calico-system (most new installs use the calico-system namespace).

Perhaps this is a use-case for Tabs for "Operator" and "Manifest" installs? We have those elsewhere in the docs.

[paketb0te]

Sure, I don't mind which one is used as example :)

Maybe we could even make it extra-explicit by using something like $NAMESPACE_IN_WHICH_CALICO_IS_RUNNING

That would
a) make it non-copy-paste-able, and thus
b) ensure that people look up the namespace calico is actually running in.

I like these Tabs for the different installation methods because they help keep the docs a bit clearer, but I also think they are better used in the "explanatory" sections of the docs and could be confusing in the Resource Definition Reference.

[caseydavenport]

I'd be happy with that approach :)

I'll leave it up to @ctauchen as to what the preferred style guideline would be in this case.