add ability to import existing firewalls
Assessment
This issue has not been assessed yet.
Description
Currently the controller only supports a single firewall defined and owned by itself. The controller should be able to import an existing firewall when given the ID of the firewall to import.
Upon importing the firewall the controller should not manage the rules of the firewall, but instead only update the device list to include the nodes in the cluster.
- Dominant language
- Go
- Stars
- 16
- Forks
- 9
- Avg merge
- 5m
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from linode/cloud-firewall-controller
-
Using to many rulesOpen
Difficulty 3/5 1-2 days Newbie friendliness 35/100
linode/cloud-firewall-controller#28 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
linode/cloud-firewall-controller#18 · 1 comment · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
linode/cloud-firewall-controller#17 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
linode/cloud-firewall-controller#16 · 1 comment ·
-
cleanup of controller owned firewallsMay be free again @hcwagner claimed this 746 days ago, and no pull request is open. Openenhancement
linode/cloud-firewall-controller#2 · 1 comment · 1 reaction · 1 assignee ·
All issues in linode/cloud-firewall-controller
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
prime-radiant-inc/evener#3726 ·
Maintainers usually reply within 1 day
-
[BUG] Async engine endpoint-label relationship counts include pending relationships of every typeOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
modelcontextprotocol/go-sdk#1340 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
gravitational/teleport#69829 ·
Maintainers usually reply within 11 days
-
🪲 bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
binwiederhier/ntfy#1992 ·
Maintainers usually reply within 2 days