supermarket Provide IPv6 endpoints for the public Supermarket

Now that AWS has IPv6 supermarket could use it.

Jan 14 '19 14:01 Lasering

I there anyway I can help to make this happen?

Jul 02 '19 10:07 Lasering

An effort to support IPv6 probably begins with a survey of how the current build misbehaves. In what ways does Supermarket not work in an IPv6 environment?

Jul 02 '19 11:07 robbkidd

Maybe this is not the correct place. I'm not referring to private installations of supermarket but rather the public supermarket. The public supermarket does not have IPv6:

$ host supermarket.chef.io
supermarket.chef.io is an alias for supermarket-chef-io-2027597622.us-west-2.elb.amazonaws.com.
supermarket-chef-io-2027597622.us-west-2.elb.amazonaws.com has address 34.211.74.137
supermarket-chef-io-2027597622.us-west-2.elb.amazonaws.com has address 35.163.90.8
supermarket-chef-io-2027597622.us-west-2.elb.amazonaws.com has address 34.211.249.84

I referred AWS because the public supermarket is deployed there.

Jul 02 '19 12:07 Lasering

A-ha! This is a fine place to track the request for the public Supermarket instance to have IPv6 endpoints.

Jul 02 '19 12:07 robbkidd

This wouldn't actually require Supermarket itself to support IPV6. We'd just enable the endpoint to support it and clients would start communicating over ipv6.

Sep 27 '21 02:09 tas50