-
Notifications
You must be signed in to change notification settings - Fork 27
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
ArgoCD sync trying convert 87600h0m0s back to 87600h #190
Comments
Hi, |
This issue has been automatically marked as stale because it has not had any activity for 30 days. It will be closed in a week if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to inactivity. Please feel free to reopen this issue (or open a new one) if this still requires investigation. Thank you for your contribution. |
It accepts shorter format like Yh, but the mutating webhook, if installed/enabled will convert it to the full format, causing potential endless reconciliation loops with tools like ArgoCD Fixes topolvm#190
It accepts shorter format like Yh, but the mutating webhook, if installed/enabled will convert it to the full format, causing potential endless reconciliation loops with tools like ArgoCD Fixes topolvm#190 Signed-off-by: Philippe M. Chiasson <gozer@ectoplasm.org>
It accepts shorter format like Yh, but the mutating webhook, if installed/enabled will convert it to the full format, causing potential endless reconciliation loops with tools like ArgoCD Fixes topolvm#190 Signed-off-by: Philippe M. Chiasson <gozer@ectoplasm.org> Signed-off-by: Philippe M. Chiasson <gozer@lacework.net>
Hello
Im using argocd to deploy pvc-autoresizer
In argocd sync the certificate get into the cluster with the duration parameter as
duration: 87600h0m0s
Instead
duration: 87600h
What it means that the application in argo is always in a "not synced" state
Same goes to controller certificate
I guess to overcome it need to set minutes and seconds in the value in helm chart
Image attached:
The text was updated successfully, but these errors were encountered: