Skip to content
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

Network Policy corrected for Ingress-Nginx #913

Merged
merged 1 commit into from Nov 16, 2020

Conversation

Ropes
Copy link
Contributor

@Ropes Ropes commented Nov 14, 2020

An incorrect Network Policy namespace selector for Nginx's Ingress
controller was blocking connections. This small fix corrects the
selector allowing traffic to pass through Ingress.

fixes: #911

An incorrect Network Policy namespace selector for Nginx's Ingress
controller was blocking connections. This small fix corrects the
selector allowing traffic to pass through Ingress.

fixes: #911

Signed-off-by: Josh Roppo <josh@akash.network>
@Ropes Ropes added the kind/bug Something is not working as expected label Nov 14, 2020
@codecov
Copy link

codecov bot commented Nov 14, 2020

Codecov Report

Merging #913 (9332e66) into master (bb5f8ea) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #913   +/-   ##
=======================================
  Coverage   39.78%   39.78%           
=======================================
  Files         175      175           
  Lines        8986     8986           
=======================================
  Hits         3575     3575           
  Misses       4997     4997           
  Partials      414      414           

@Ropes Ropes merged commit b283bb8 into master Nov 16, 2020
@Ropes Ropes deleted the ropes/911-ingress-firewall-rule branch November 16, 2020 15:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something is not working as expected
Projects
None yet
2 participants