cleanup of controller owned firewalls

Open
#2 1 comment 1 reaction 1 assignee View on GitHub

@hcwagner is already working on this.

Since Sep 18, 2024.

Assessment

This issue has not been assessed yet.

Description

enhancement

Running helm uninstall or rollback will delete the controller and associated manifests from the cluster, but will leave existing firewalls deployed in the cloud infra (Cloud Manager/Linode API).

When deleting the installation of the controller it should check for all CloudFirewalls that are not imported (i.e. owned by something else) and delete them prior to removing the controller.

This will require:

  • finalizer for the controller
  • ownership information to be persisted in the CloudFirewall object state
Dominant language
Go
Stars
16
Forks
9
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linode/cloud-firewall-controller

All issues in linode/cloud-firewall-controller

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.