Articles in this section

See more

How to renew the container registry certificate

Updated
Follow

About this article

Templafy updates periodically the container registry certificate which is used for pulling the Docker images from the Templafy container repository during AKS or Email Signature Server version upgrades.

This certificate update is not affecting any working environment, but it will prevent any update to the Email Signature Server container version since the call to the repository to get the Docker image will fail due the expired certificate.

Per that, this could make the Docker image update failing for the Email signature server and could make it to stop functioning.

 

Prerequisites

 
  • Templafy Email Signature Server Client-Hosted
  • Any deployment done before April 18th, 2023.

 

Per that, this could make the Docker image update failing for the Email signature server and could make it to stop functioning.

Recreating templafy-container-registry certificate will ensure there is no issue during a future AKS upgrade or ESS upgrade in the cluster, it's highly recommended to get it done on time.

 
  • The existent certificate is expiring on April 20th, 2023.
  • The new certificate is Valid until March 21st, 2025.
  • It's highly recommended to keep track of this date and to renew the certificate on time whenever it's getting close to its expiration.
  • The Article will be kept up to date with the working certificate.

 

Delete the existing templafy-container-registry in the AKS cluster

  1. Navigate to the Resource group containing the templafyemailsignatureserver Kubernetes service
  2. Select the Configuration under the Kubernetes resources section of the left hand panel
  3. Select Secrets Tab in the main panel on the right
  4. Select templafy-container-registry in the main panel on the right
  5. Click on Delete button 

 

Generate a templafy-container-registry based on the new certificate

 
  • Make sure to replace in the command lines below <resource_group> and <subscription name or id>by the values collected in the step 2.

 

  1. Navigate to the templafyemailsignatureserver Kubernetes service
  2. Save the value of subscription name and the Resource group name from the templafyemailsignatureserver Kubernetes service page

     

  3. Start Cloud Bash Shell mceclip0.png

     

  4. Set the right MS Azure subscription with the following command:
    az account set --subscription <subscription name or id>

  5. In Cloud Shell navigate to the clouddrive directory:
    cd clouddrive

  6. Get to access to the Kubernetes control service:
    az aks get-credentials --name templafyemailsignatureserver --resource-group <resource_group>
  7. Set the context around the name space of the Email signature server deployment in Kubernetes:
    kubectl config set-context templafyemailsignatureserver --namespace=templafy-emailsignature
  8. Generate the new certificate:
    kubectl create secret docker-registry templafy-container-registry --docker-server=templafyprod.azurecr.io --docker-username=9b311d08-17e0-49d0-982c-8a35aca686e9 --docker-password=iOC8Q~nW-MwNfCw~lBAfj9T~kwufdgbktHAIdbgM --docker-email=support@templafy.com -n templafy-emailsignature

 

Related articles

 

 

Related articles

Comments

0 comments

Please sign in to leave a comment.