Consul api gateway on vm based installation

[thatsk]

Consul api gateway installation and configuration should be on vm based installation also which is binary based itself. Otherwise it will only stick to k8s not with vm based workloads

[thatsk]

It should be uniform based for both the infrastructure like container workload and non container workload based services

[david-yu]

Hi thanks for the feedback. Could you tell us more about your VM infrastructure (OS and Cloud Provider). What kind of tcp load balancer would you use to load balance traffic across the VMs?

[thatsk]

so we are basically using centos7 with consul binary and we have nomad based workload for container and we are not using k8s. and we are using basically f5 for loadbalancer.

[ashwinkupatkar]

Yes we need support for consul api gateway for VM based workloads.

[Jeff-Apple]

@thatsk and @ashwinkupatkar,

We plan to support running Consul API Gateway on Linux VMs later this year.

[thatsk]

Eagerly waiting for this feature

[Esity]

@Jeff-Apple Looking for an update on this one also. Would be useful to allow for things like VMs and Nomad(issue hashicorp/consul#16421) to expand more use cases. Only allowing K8s limits adoption of the api gateway IMO

CC @wjpatton

[thatsk]

So are we talking this in quarter

[Esity]

@Jeff-Apple is there an update on this one?

[Esity]

Still looking for an update on this one

[Esity]

For anyone watching this issue, sounds like this is slated for the Consul 1.15 release

[andrewstucki]

Closing as we're releasing beta support for using API gateways as a native Consul gateway type that can be run in non-Kubernetes workloads in 1.15 🎉