-
Notifications
You must be signed in to change notification settings - Fork 99
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
Expanded Letsencrypt certificate chain breaks kubernetes-reflector #191
Labels
Comments
I'm also interested in a fix here. |
Automatically marked as stale due to no recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Automatically closed stale item. |
winromulus
added a commit
that referenced
this issue
Oct 16, 2021
- New multi-arch pipeline with proper tagging convention - Removed cert-manager extension (deprecated due to new support from cert-manager) Fixes: #191 - Fixed healthchecks. Fixes: #208 - Removed Slack support links (GitHub issues only). Fixes: #199 - Simplified startup and improved performance. Fixes: #194 - Huge improvements in performance and stability. Fixes: #187 #182 #166 #150 #138 #121 #108
Merged
winromulus
added a commit
that referenced
this issue
Oct 16, 2021
- New multi-arch pipeline with proper tagging convention - Removed cert-manager extension (deprecated due to new support from cert-manager) Fixes: #191 - Fixed healthchecks. Fixes: #208 - Removed Slack support links (GitHub issues only). Fixes: #199 - Simplified startup and improved performance. Fixes: #194 - Huge improvements in performance and stability. Fixes: #187 #182 #166 #150 #138 #121 #108
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As mentioned here of may 4th letsencrypt increased the size of their certificate chain and are now including 3 certificates rather than 2.
This causes the reflector to fail when watching the secret and never update secrets in other namespaces.
In this case this is evidenced by the following error message:
as cert manager now provides these by default this breaks any cert-manager integration. Also should we only reflect a 2 certificate chain we will lose compatibility with older android operating systems
This may be the cause of #187
@winromulus are you able to help here?
The text was updated successfully, but these errors were encountered: