-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
docs: Update description in egress gateway guide #23616
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.
Thanks for the PR!
Could we make it a warning please? You can find an example here:
cilium/Documentation/network/egress-gateway.rst
Lines 252 to 254 in 666100d
.. warning:: | |
The egress IP must be assigned to a network device on the node. |
Sure, thanks for the review 😄 |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
874498c
to
93159f2
Compare
@jibi I have updated the file, please review it. |
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.
Looks good, thanks!
Can you please fix the formatting for the flag name and Helm value?
Can you also please squash your commits and make sure you keep only one Signed-off-by:
tag in the description? Can you also extend that description by mentioning why this change is needed, please?
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
1 similar comment
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
@qmonnet I'm so sorry for how messy my PR has gotten. I was able to squash the first 3 commits into one but there are a few merges before the last commit (where I remove the warning). Is there any way to squash that too? |
Yes there is, probably more than one way to do it. Please have a look at my example above. |
f9b7098
to
ba1b4ae
Compare
…EKS ENI mode Signed-off-by: Deepesha Burse <deepesha.3007@gmail.com>
ba1b4ae
to
076ad21
Compare
@qmonnet It worked! Thank you so much for walking me through every step so patiently. I really appreciate it. I finally understood the entire process. 😄 |
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.
@qmonnet It worked! Thank you so much for walking me through every step so patiently. I really appreciate it. I finally understood the entire process. smile
Awesome to hear, thanks for all your efforts! Looks all good this time, and the CI test for documentation is passing.
@deepeshaburse Thanks for your contribution! |
Signed-off-by: Deepesha Burse deepesha.3007@gmail.com
Please ensure your pull request adheres to the following guidelines:
description and a
Fixes: #XXX
line if the commit addresses a particularGitHub issue.
Fixes: #23256