Hello Mark,
I have done this solution before but the issue is still the same and also I managed to create a new certificate using SAN but still the issue is still valid.
Thanks,
MK
------------------------------
mohamed khalil
------------------------------
Original Message:
Sent: Wed April 12, 2023 07:55 AM
From: Mark Scherfling
Subject: AppHost Upgrade Kubectl Issue
Hi Mohamed,
Without digging into the logs, are you using your own (insecure) registry? It's possible that the new App Host no longer supports insecure registries by default. There are two options, either upgrade your registry so that it's secure, or identify your registry with "insecure-registries"
. Refer to the documentation associated with your registry implementation on how to make that identification.
Hope this helps,
Mark
------------------------------
Mark Scherfling
Original Message:
Sent: Mon April 10, 2023 01:30 PM
From: mohamed khalil
Subject: AppHost Upgrade Kubectl Issue
Hello,
I have faced an issue after installing Apphost from version 1.8 to 1.12 regarding the images. All images have Error: ImagePullBackOff and when checked kubectl describe for one of the images the error msg was ( failed to do request" Head "docker local repo url" x509: certificate relies on legacy Common Name field, use SANs instead. ) Appreciate if anyone faced this issue before.
Thanks.
------------------------------
mohamed khalil
------------------------------