0.6.0

• Allow dynamic configuration of security list management via annotations. [#217]
• Migrate to Zap logger. [#223]
• Runtime checks around providerID. [#228]
• Support request rate limiting. [#201]
• Bump dependencies to Kubernetes 1.11.1. [#234]

0.5.1

• Fixes panic on startup when security lists aren't managed [#213]
• Update oci-go-sdk to 2.0.0 which includes support for load balancer tagging.

0.5.0

• Allow load balancer functionality to be disabled. [#198]
• Allow subnets in configuration to be optional. [#202]

0.4.0

• Implement loadbalancer.securityListManagementMode: Frontend which only
  manages security list rules for load balancer ingress. [#180]
• Depreciate loadbalancer.disableSecurityListManagement in favour of
  loadbalancer.securityListManagementMode: None. [#180]
• Implement loadbalancer.securityLists to allow explicit configuration of the
  security lists that the CCM manages on a per-subnet basis [#164].
• Implement support for instance principles authentication [#155]

0.3.2

• [BUG] Fix panic when EnsureLoadBalancer() called with 0 Nodes [#176]
• [BUG] Fix panic when GetInstanceByNodeName() encountered an instance without
  either a public IP or a hostname [#167]
• [BUG] Fix regression where compartment OCID was no longer looked up from
  metadata when not provided in cloud-provider config [#168]
• Depreciate cloud-provider config property auth.key_passphrase replacing it
  with auth.passphrase [#142]
• Depreciate cloud-provider config property auth.compartment replacing it
  with compartment [#170]

0.3.1

• Remove redundant --cluster-cidr flag from DaemonSet [#163]

0.3.0

• Create load balancers using a single OCI API request significantly reducing fresh load balancer creation time [#148]
• Fix failure to delete security list rules when deleting a Service type=LoadBalancer or changing its NodePort(s) [#151]
• Move to ConfigMap based leader election [#160]
• Fix potential panic when a load balancer had no backends [#157]

0.2.1

• Add OCI proxy support (#135)
• Add security rules for a services health check port (#125)

0.2.0

Config for Wercker release (#131)

* Remove unused pod file
* Clean makefile to add version/build
* Add checks to all target, verbose build
* Configure for release
* Add release process and content type
* Move copy to step

0.1.2

• Fixes a bug where existing security list rules with no destination port range set would cause the CCM to fail when update security lists whilst ensuring load balancer state [#112]