many improvements and bugfixes, see CHANGELOG.md

Author: travisghansen

.env.example

@@ -3,3 +3,5 @@
 # PFSENSE_PASSWORD="secret"
 # PFSENSE_INSECURE="false"
 # PFSENSE_DEBUG="false"
+# CONTROLLER_NAME="kubernetes-pfsense-controller"
+# CONTROLLER_NAMESPACE="kube-system"

CHANGELOG.md

@@ -1,3 +1,16 @@
+# v0.2.0
+
+Released 2020-04-11
+
+- use `->createList()` vs simple `->request()` throughout to support resource types that may have many resources
+- fix multi-host issues with `pfsense-dns-haproxy-ingress-proxy` (see #8)
+- Allow setting `CONTROLLER_NAME` and `CONTROLLER_NAMESPACE` `env` vars to support multiple deploys and deployments to
+alternative namespaces (see #7)
+- support the `frr` `bgp-implementation` for `metallb` plugin
+- support custom `configMap` for `metallb` plugin
+- better logic for `haproxy-declarative` to support service changes including being created **after** the `ConfigMap`
+- support service port names (vs port number) in `haproxy-declarative` `ConfigMap`s
+
 # v0.1.9
 
 Released 2019-11-30

README.md

@@ -24,14 +24,18 @@ combination of Layer2 or BGP type configurations.  Layer2 requires no integratio
 leverage the BGP implementation you need a BGP server along with neighbor configuration.  `kpc` *dynamically* updates
 bgp neighbors for you in pfSense by continually monitoring cluster `Node`s.
 
-The plugin assumes you've already installed openbgp and configured it as well as created a `group` to use with MetalLB.
+The plugin assumes you've already installed openbgp or frr and configured it as well as created a `group` to use with
+MetalLB.
 
 ```yaml
       metallb:
         enabled: true
         nodeLabelSelector:
         nodeFieldSelector:
+        #configMap: "metallb-system/config"
+        # pick 1 implementation
         bgp-implementation: openbgp
+        # bgp-implementation: frr
         options:
           openbgp:
             template:
@@ -41,13 +45,16 @@ The plugin assumes you've already installed openbgp and configured it as well as
               row:
                 - parameters: announce all
                   parmvalue:
+          frr:
+            template:
+              peergroup: metallb
 ```
 
 ## haproxy-declarative
 `haproxy-declarative` plugin allows you to declaratively create HAProxy frontend/backend definitions as `ConfigMap`
 resources in the cluster.  When declaring backends however, the pool of servers can/will be dynamically created/updated
 based on cluster nodes.  See [declarative-example.yaml](examples/declarative-example.yaml) for an example.
- 
+
 ```yaml
       haproxy-declarative:
         enabled: true

composer.json

@@ -17,7 +17,7 @@
         "ext-json": "*",
         "ext-bz2": "*",
         "travisghansen/kubernetes-controller-php": "0.1.*",
-        "travisghansen/kubernetes-client-php": "0.1.*",
+        "travisghansen/kubernetes-client-php": "0.2.*",
         "zendframework/zend-xmlrpc": "^2.7",
         "vlucas/phpdotenv": "^2.5",
         "composer/semver": "^1.5"