I installed a 3CX instance over the summer with the assistance of the 3CX Google Marketplace cloud launcher.
(https://www.3cx.com/blog/news/google-marketplace/ )
It's been working fine. I received an alert from Google a few weeks ago titled,
"[Action Required] Legacy GCE Metadata Server endpoints will be shut down on January 15, 2020",
and it referenced this deployed instance as one that will require attention. I wasn't sure how this applied to me so I reached out to Google support, which didn't help much other than to point me to the same Google documentation I'd already read, and to explain that the metadata in question is found under the VM instance details->Custom metadata.
There are several lines in that section that I presume were added automatically when the launcher app created the VM. Other 3CX VM's that I've created manually do not have anything listed there.
Does anyone know what needs to be done to address this? Google support insisted there must be something within the Debian VM that needs to be adjusted...
Here is more information from the alert email:
Hello Google Compute Engine Customer,
We are writing to let you know that the v0.1 and v1beta1 endpoints of the Compute Engine Metadata Server will be shut down on January 15, 2020. From January 15, 2020, requests to the v0.1 and v1beta1 endpoints will no longer be supported, and may return HTTP 404 NOT FOUND responses.
Our records show that you own projects that have requests to these endpoints. You will need to update your requests to the v1 endpoint before January 15, 2020.
You can check the Metadata Server URI to which you’re making requests to determine which endpoint you’re calling:
To ensure minimal interruption to your instances, please update your requests (listed below) to the v1 endpoint before January 15, 2020.
How to upgrade from v1beta1 to v1:
curl "http://metadata.google.internal/computeMetadata/v1beta1/instance/id"
Upgrade to v1 as follows:
curl "http://metadata.google.internal/computeMetadata/v1/instance/id" -H "Metadata-Flavor: Google"
How to upgrade from v0.1 to v1:
curl "http://metadata.google.internal/0.1/meta-data/instance-id"
Upgrade to v1 as follows:
curl "http://metadata.google.internal/computeMetadata/v1/instance/id" -H "Metadata-Flavor: Google"
Turn off the v0.1 and v1beta1 endpoints ahead of January 15, 2020
You may want to turn off the v0.1 and v1beta1 endpoints ahead of January 15, 2020 - for example, to ensure that no further development happens against them in the interim.
Set the disable-legacy-endpoints=true metadata value on either the instance or the project, as documented in our Disabling legacy endpoints page. When set, requests to the v0.1 or v1beta1 endpoints will return HTTP 403 FORBIDDEN responses.
Our records show that your projects listed below made requests to the v0.1 or v1beta1 endpoints in the last 90 days and may be affected by this change:
(https://www.3cx.com/blog/news/google-marketplace/ )
It's been working fine. I received an alert from Google a few weeks ago titled,
"[Action Required] Legacy GCE Metadata Server endpoints will be shut down on January 15, 2020",
and it referenced this deployed instance as one that will require attention. I wasn't sure how this applied to me so I reached out to Google support, which didn't help much other than to point me to the same Google documentation I'd already read, and to explain that the metadata in question is found under the VM instance details->Custom metadata.
There are several lines in that section that I presume were added automatically when the launcher app created the VM. Other 3CX VM's that I've created manually do not have anything listed there.
Does anyone know what needs to be done to address this? Google support insisted there must be something within the Debian VM that needs to be adjusted...
Here is more information from the alert email:
Hello Google Compute Engine Customer,
We are writing to let you know that the v0.1 and v1beta1 endpoints of the Compute Engine Metadata Server will be shut down on January 15, 2020. From January 15, 2020, requests to the v0.1 and v1beta1 endpoints will no longer be supported, and may return HTTP 404 NOT FOUND responses.
Our records show that you own projects that have requests to these endpoints. You will need to update your requests to the v1 endpoint before January 15, 2020.
You can check the Metadata Server URI to which you’re making requests to determine which endpoint you’re calling:
What do I need to do?
To ensure minimal interruption to your instances, please update your requests (listed below) to the v1 endpoint before January 15, 2020.
How to upgrade from v1beta1 to v1:
- Change the request URI to use v1 instead of v1beta1
- Add this header to your request: “Metadata-Flavor: Google”
curl "http://metadata.google.internal/computeMetadata/v1beta1/instance/id"
Upgrade to v1 as follows:
curl "http://metadata.google.internal/computeMetadata/v1/instance/id" -H "Metadata-Flavor: Google"
How to upgrade from v0.1 to v1:
- Change the request URI to use v1 instead of v0.1
- Add this header to your request: “Metadata-Flavor: Google”
- Use these instructions to map the v0.1 properties to the v1 properties
curl "http://metadata.google.internal/0.1/meta-data/instance-id"
Upgrade to v1 as follows:
curl "http://metadata.google.internal/computeMetadata/v1/instance/id" -H "Metadata-Flavor: Google"
Turn off the v0.1 and v1beta1 endpoints ahead of January 15, 2020
You may want to turn off the v0.1 and v1beta1 endpoints ahead of January 15, 2020 - for example, to ensure that no further development happens against them in the interim.
Set the disable-legacy-endpoints=true metadata value on either the instance or the project, as documented in our Disabling legacy endpoints page. When set, requests to the v0.1 or v1beta1 endpoints will return HTTP 403 FORBIDDEN responses.
Our records show that your projects listed below made requests to the v0.1 or v1beta1 endpoints in the last 90 days and may be affected by this change:
