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.

Sign up for GitHub

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

Jump to bottom

[Bug] EC2 provisioner does not open client port #45

Closed
adamjohnson01 opened this issue Jan 22, 2020 · 3 comments · Fixed by #49
Closed

[Bug] EC2 provisioner does not open client port #45

adamjohnson01 opened this issue Jan 22, 2020 · 3 comments · Fixed by #49

Comments

@adamjohnson01
Copy link
Contributor

The version of inletsctl used by the operator does not allow access to any client ports in the security group that gets created. A PR that fixes this has now been merged.

Expected Behaviour

Connections to the Kubernetes service succeed.

Current Behaviour

Access to the client port is being blocked so connections fail.

Possible Solution

Steps to Reproduce (for bugs)

  1. Deploy an EC2 exit node with the operator
  2. Create a loadbalancer service
  3. Attempt to connect to the service using the exit node public IP

Your Environment

  • Operator 0.5.6
  • kind v0.6.0 go1.13.4 darwin/amd64
  • Kubernetes: v1.16.0
  • Operating System: MacOS 10.15.1 (19B88)
  • Cloud provisioner: AWS EC2
@alexellis
Copy link
Member

@adamjohnson01 would you be able to take this please?

@adamjohnson01
Copy link
Contributor Author

@alexellis, sure. Will do.

@alexellis
Copy link
Member

@adamjohnson01 since we have a couple of projects, I wanted to check in - is this working now, or is work still needed? is inletsctl affected?

alexellis added a commit that referenced this issue Feb 10, 2020
@alexellis
Bump provision package
14e7f04 
The latest provision package contains fixes from inletsctl
for GCP exit-nodes and the ports opened for inlets-pro. A fix
for opening ports on EC2 is also brought across at the same
time.

Fixes: #46
Fixes: #45

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>
@alexellis alexellis mentioned this issue Feb 10, 2020
Merged
alexellis added a commit that referenced this issue Feb 10, 2020
@alexellis
Bump provision package
7cbc350 
The latest provision package contains fixes from inletsctl
for GCP exit-nodes and the ports opened for inlets-pro. A fix
for opening ports on EC2 is also brought across at the same
time.

Fixes: #46
Fixes: #45

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Bump provision package inlets/inlets-operator
2 participants
@alexellis @adamjohnson01