Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cant see the renewal event in the describe certificate #773

Closed
habeebshk opened this issue Jul 26, 2018 · 7 comments · Fixed by #1017
Closed

Cant see the renewal event in the describe certificate #773

habeebshk opened this issue Jul 26, 2018 · 7 comments · Fixed by #1017
Labels
kind/documentation Categorizes issue or PR as related to documentation.

Comments

@habeebshk
Copy link

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug
/kind feature

What happened:
I deployed the cert-manager in the GKE cluster and was supposed to see the renewal line at the end that shows in how many days my certificate is gonna be auto-renewed.
What you expected to happen:
rn,

How to reproduce it (as minimally and precisely as possible):
and this is what i have
rn2

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version):
  • Cloud provider or hardware configuration**:
  • Install tools:
  • Others:
@kragniz
Copy link
Contributor

kragniz commented Jul 27, 2018

@habeebshk this information is now only shown in cert-manager controller logs, eg:

I0727 15:23:13.413745   17988 sync.go:207] Certificate default/kgz-cert scheduled for renewal in 1438 hours

@habeebshk
Copy link
Author

@kragniz hey thanks for that, can you comment the command on how to check the cert-manager controller logs, i tried finding it online but nothing useful. Thanks

@kragniz
Copy link
Contributor

kragniz commented Jul 27, 2018

something like

kubectl logs -n your-namespace -l app=cert-manager -c cert-manager

replacing your-namespace with the namespace you deployed cert-manager to

@munnerz
Copy link
Member

munnerz commented Jul 28, 2018

We should update the migrating from kube-lego guide accordingly with this info.

Related to #742 - because we should still surface this information to users somehow, even if it is not through Events.

@munnerz
Copy link
Member

munnerz commented Jul 28, 2018

/kind documentation

@jetstack-bot jetstack-bot added the kind/documentation Categorizes issue or PR as related to documentation. label Jul 28, 2018
@ahmetb
Copy link

ahmetb commented Oct 11, 2018

The event on the Cerificate is from cert-manager; not kube-lego. From the screenshots, it looks like events have changed recently (from 0.3 to 0.5)?

@floyd-may
Copy link
Contributor

Got really confused by this as well; made the above PR =)

munnerz pushed a commit to munnerz/cert-manager that referenced this issue Oct 31, 2018
Related to cert-manager#773 - the previous instructions guide the user to look for events on the certificate related to when renewals are scheduled. This change directs them to view the logs to see the renewal schedule messages.
Signed-off-by: Floyd May <fmay@asemio.com>
mtpereira pushed a commit to mtpereira/cert-manager that referenced this issue Feb 12, 2019
Related to cert-manager#773 - the previous instructions guide the user to look for events on the certificate related to when renewals are scheduled. This change directs them to view the logs to see the renewal schedule messages.
Signed-off-by: Floyd May <fmay@asemio.com>
kinolaev pushed a commit to kinolaev/cert-manager that referenced this issue Feb 23, 2019
Related to cert-manager#773 - the previous instructions guide the user to look for events on the certificate related to when renewals are scheduled. This change directs them to view the logs to see the renewal schedule messages.
Signed-off-by: Floyd May <fmay@asemio.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Categorizes issue or PR as related to documentation.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants