-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Clarify secret naming in EKS Fargate sidecar injection doc #19871
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you see my suggestion for updating the line about the secret name? Telling users what happens when they break the rules helps them understand why they need to do what we recommend.
Co-authored-by: Ursula Chen <[email protected]>
Review from sblumenthal is dismissed.
Related teams and files:
- container-integrations
- eks_fargate/README.md
Review from urseberry is dismissed.
Related teams and files:
- eks_fargate/README.md
- documentation
- eks_fargate/README.md
Co-authored-by: Ursula Chen <[email protected]>
@urseberry, sorry missed to add your commits. Updated now. |
What does this PR do?
Clarifying secret naming.
DataDog/datadog-operator#1688
Motivation
Review checklist (to be filled by reviewers)
qa/skip-qa
label if the PR doesn't need to be tested during QA.backport/<branch-name>
label to the PR and it will automatically open a backport PR once this one is merged