Charm does not detect Kubernetes secret name changes

Bug #1831007 reported by Ryan Finnie
Affects Status Importance Assigned to Milestone

Bug Description

If cert_kubernetes_names is updated to change an existing cert to point to a new secret name, it appears this will not be detected and applied to the new name (but presumably would eventually once the cert comes up for renewal).

Revision history for this message
Tom Haddon (mthaddon) wrote :

From what I can see it detects it and configures the config file correctly (e.g. /etc/autocert/kubernetes/${sitename}.ini) but doesn't actually run the configured cert_action_cmd to update the secret. Note that if it was to do this, it would also need to track the previous secret name, and either rename it or remove the old name when creating the new one.

Changed in autocert-charm:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.