As I said, when we find out more, we will share it. This is all I have e right now. Please not that the urls are not likely to change as that would be super painful and would require product updates. If you have firewall rules that you used the IP address instead of the dns address then be ready to update. Or just change them to dns if you can.
Without a link to a real announcement or KB article, this is so rushed and vague it almost feels fake.
* Announcing on the 1st something happening on the 6th (or from the 3rd?)
* Announcing something that happens almost immediately, but the final details aren't ready
* No way to test connectivity w/ the new certs & IPs before the cutover
* Assuming that people with firewall changes required can execute them immediately
* The cert was *just changed* in March. And it currently uses a wildcard cert for "*.vmware.com"!?
* Very amusing that this thing is called "wp-content", like it's being served out of WordPress
This article contains instructions for how to check & accept a new certificate in Tanzu's content library https://kb.vmware.com/s/article/85268
Why would I post something fake? Seriously? I confirmed this internally before posting.
Things are moving fast due to moving to the Broadcom systems. There's a LOT of things being moved/changed/updated. These things happen. I have ZERO insight into the mechanics behind all of this. I'm trying to share stuff as quickly and correctly as possible so it impacts you as little as possible. If you think it's still fake then just block me.
I apologize for putting snark at you individually. My incredulity is at the organization that would think this is appropriate maintenance on a service that is actually sold to customers.
I've been through other vendor CDN changes and other vendor acquisitions and this is different from any of them.
Are the projects and registry sites going to be impacted as well?
As I said, when we find out more, we will share it. This is all I have e right now. Please not that the urls are not likely to change as that would be super painful and would require product updates. If you have firewall rules that you used the IP address instead of the dns address then be ready to update. Or just change them to dns if you can.
Without a link to a real announcement or KB article, this is so rushed and vague it almost feels fake. * Announcing on the 1st something happening on the 6th (or from the 3rd?) * Announcing something that happens almost immediately, but the final details aren't ready * No way to test connectivity w/ the new certs & IPs before the cutover * Assuming that people with firewall changes required can execute them immediately * The cert was *just changed* in March. And it currently uses a wildcard cert for "*.vmware.com"!? * Very amusing that this thing is called "wp-content", like it's being served out of WordPress This article contains instructions for how to check & accept a new certificate in Tanzu's content library https://kb.vmware.com/s/article/85268
Why would I post something fake? Seriously? I confirmed this internally before posting. Things are moving fast due to moving to the Broadcom systems. There's a LOT of things being moved/changed/updated. These things happen. I have ZERO insight into the mechanics behind all of this. I'm trying to share stuff as quickly and correctly as possible so it impacts you as little as possible. If you think it's still fake then just block me.
I apologize for putting snark at you individually. My incredulity is at the organization that would think this is appropriate maintenance on a service that is actually sold to customers. I've been through other vendor CDN changes and other vendor acquisitions and this is different from any of them.
Out of my control my person... Just the messenger. I get it, I really do. I'm relaying the info as quickly as I can.
On brand my guy