2019/12/01 12:17:34 [WARN] Provider "kubernetes" produced an invalid plan for kubernetes_deployment.sample-deployment, but we are tolerating it because it is using the legacy plugin SDK.
    The following problems may be the cause of any confusing errors from downstream operations:
      - .spec[0].template[0].spec[0].image_pull_secrets: block count in plan (1) disagrees with count in config (0)
      - .spec[0].template[0].spec[0].container[0].resources: block count in plan (1) disagrees with count in config (0)
      - .spec[0].strategy: block count in plan (1) disagrees with count in config (0)

.spec[0].template[0].spec[0].image_pull_secrets: block count in plan (1) disagrees with count in config (0)

resource "aws_eip_association" "aws_eip_home" {
  instance_id   = aws_instance.application-instance.id
  allocation_id = var.application-eip
}

Error: Error associating EIP: MissingParameter: Either public IP or allocation id must be specified
        status code: 400, request id: 57f7983a-f813-4111-8d70-0000c5d1bd70

  on eip.tf line 2, in resource "aws_eip_association" "aws_eip_home":
   2: resource "aws_eip_association" "aws_eip_home" {

resource "aws_eip_association" "aws_eip_home" {
  count         = "${var.application-eip != "" ? 1 : 0}"
  instance_id   = aws_instance.application-instance.id
  allocation_id = var.application-eip
}

provider "aws" {
  region = "${var.aws_region}"
}