jw-maynard

@dak1n1 I'm getting the same errors with the following: ``` Terraform version: 0.14.6 Kubernetes provider version: 2.0.2 EKS version: v1.18.9 -> v1.19.6 ``` As you can see the the only...

Did some further digging and we may be barking in the wrong place: https://github.com/hashicorp/terraform-provider-aws/issues/10269#issuecomment-777906069

@dak1n1 It never gets that far because the plan errors but I know that version upgrades in EKS are an update in place scenario for sure. I guess they could...

@joshdover I was directed to this issue from https://github.com/elastic/helm-charts/issues/1594. It seems like the team at Elasic is phasing out helm charts in favor of a k8s operator. That makes perfect...

We have a use case that would benefit simply by step 3 in the above. It would be nice to have the CNI able to assign a Elastic IP (EIP)...

@apparentlymart Can we get this merged? I'm in a situation where I need to create a CRD in k8s but currently the k8s provider does not support CRDs. To work...

@appilon Would you be the correct person to review and merge this?

@ksatirli I've always understood that you need to install Ansible on the machine you're running packer on to use the ansible provisioner. It is not installed in either the base...

@oba11 The packer GitHub action runs inside a docker container that runs inside the GitHub Action runner instance. You're workflow is installing Ansible in the runner instance but since packer...

That was my experience.