Comment 1 for bug 1831007

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.