Adding Tip not to enable global sds

[rjshrjndrn]

While deploying certmanager, if somebody enables sds in values.yml rather than passing it via cli, their pods never become healthy as it'll enable mtls.

[ ] Configuration Infrastructure
[ x ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[istio-testing]

Hi @rjshrjndrn. Thanks for your PR.

I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[rjshrjndrn]

@googlebot I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[geeknoid]

/ok-to-test

[rjshrjndrn]

@geeknoid Can you please help me to fix the error. I'm literally in oblivion.

 - ./public/docs/tasks/traffic-management/ingress/ingress-certmgr/index.html
  *  31983:134: ERROR: Unexpected end tag : p (line 31983) 

[geeknoid]

You've hit a bug in Hugo that happens on rare occasions with specific compositions of text blocks.

Instead of , try <text_hack yaml>. That may well work around the problem.

[rjshrjndrn]

@geeknoid No luck even with that.
I tried

{{<text_hack yaml>}}
----
{{</text>}}

{{<text_hack yaml>}}
----
{{</text_hack>}}

Both are failing.

[geeknoid]

The error you're seeing now is very different than before. Now, all you have is a spelling error:

./en/docs/tasks/traffic-management/ingress/ingress-certmgr/index.md
35 | If you're editing the values.yml file, don't enable

Just put values.yml in backticks and that should get things working.

[rjshrjndrn]

/retest

[rjshrjndrn]

@geeknoid Thank you