v0.7.0 Now requires Kubernetes provider

Add full namespace support @Nuru (#34)

Possibly Breaking Change

This release now requires that you provision a Kubernetes provider as well as a Helm provider. If you were not already doing this, you can do it by copying the kubernetes section of your helm provider configuration and making it your kubernetes provider configuration:

You have:

provider "helm" {
  kubernetes {
   #### whatever Kubernetes configuration you have ####
  }
}

You add:

provider "kubernetes" {
  #### whatever Kubernetes configuration you have ####
}

what

• Provide control over Kubernetes namespace configuration and lifecycle
• Ensure created IAM role is preserved while resources are being cleaned up

why

• Previously, you were not able to add annotations or labels to namespaces
• Namespaces created by this module are now deleted when this module was deleted, previously they were left abandoned, possibly containing abandoned resources
• Previously, the IAM role the deployed service was using to clean up resources could have been deleted before the resource was done cleaning up, causing delays and errors during the terraform destroy process and possibly leaving abandoned AWS resources such as load balancers.