deployKF
kyverno #6287 repeated TLS handshake error resolved by removing and resyncing kyverno
#184
|
A few weeks after upgrading |
Answered by
thesuperzapper
Jul 23, 2024
Replies: 1 comment 1 reply
|
@cameronraysmith there is a lot of discussion about Kyverno issues at the moment (#180, #183). The current plan is to remove the dependency on Kyverno for cloning secrets (but leave it for the other use cases like triggering deployment restarts on secret change) so we can update to a much newer version of Kyverno. The main reason we require exactly version |
1 reply
|
Thank you for the information and pointers. |
Answer selected by
cameronraysmith
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@cameronraysmith there is a lot of discussion about Kyverno issues at the moment (#180, #183).
The current plan is to remove the dependency on Kyverno for cloning secrets (but leave it for the other use cases like triggering deployment restarts on secret change) so we can update to a much newer version of Kyverno.
The main reason we require exactly version
1.10.0is related to it generate type rules, which are poorly implemented.