-
Notifications
You must be signed in to change notification settings - Fork 1.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
removed path check as kubectl is handling path in it #5648
removed path check as kubectl is handling path in it #5648
Conversation
Took a look and it looks good to me. Since I am still new, I will leave the approvals to others. |
Sure @everettraven - thank you for reviewing it. |
Signed-off-by: laxmikantbpandhare <[email protected]>
Signed-off-by: laxmikantbpandhare <[email protected]>
Signed-off-by: laxmikantbpandhare <[email protected]>
/lgtm can't get the CI to pass though, it keeps failing on some linkchecking garbage |
thank you @jberkhahn for trying multiple times. Yes, it was some link-checking error. My PR do not have any change in any of the docs. |
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
…ork#5648) * removed this check as kubectl is handling path in it * added changelog * removed test file Signed-off-by: laxmikantbpandhare <[email protected]> Signed-off-by: Venkat Ramaraju <[email protected]>
…r-framework#5648)" This reverts commit 62ac861.
Description of the change:
Previously we added this error to show the user that the Path component is part of proxy server. Now, kubectl made this fix that handles this case and there is no need to throw this error anymore.
Motivation for the change:
The user should be able to run the operator with the proxy path in it.
Checklist
If the pull request includes user-facing changes, extra documentation is required:
changelog/fragments
(seechangelog/fragments/00-template.yaml
)website/content/en/docs