-
Notifications
You must be signed in to change notification settings - Fork 125
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
[RS-2338] Update WAF docs following changes to configmap name and format #1886
Conversation
✅ Deploy Preview for calico-docs-preview-next ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
❌ Deploy Preview for tigera failed. Why did it fail? →Built without sensitive environment variables
|
227e397
to
4bb2cbb
Compare
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.
LGTM. Ready to merge?
Do we need to copy this to the corresponding CC location? Currently, that's calico-cloud
.
This is not available in Calico Cloud and will be when 3.21 EP2 is validated (not yet) and used in CC (not listed in https://tigera.atlassian.net/projects/PMREQ?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page, so I assume early May release at the earliest). I assume it's too early to update the docs? If there is nothing to do, yes, that's ready to merge. |
@gantony We're ready now to take changes related to 3.21 ep2 in the CC next directory ( |
LGTM, thanks! |
Product Version(s):
3.21 EP2 (so master only for now)
Issue:
https://tigera.atlassian.net/browse/RS-2338
Epic: https://tigera.atlassian.net/browse/PMREQ-704
Link to docs preview:
SME review:
DOCS review:
Additional information:
Merge checklist: