VC-32931: Gather Istio's secret keys #538
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
maelvls force-pushed the VC-32931-istio-cacerts branch from 20e8916 to 7e2ed66 Compare Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Ref: VC-32931
Istio can be operated using a self-signed CA (with the secret
istio-ca-secret) or using the Plugin CA with the secretcacerts. Both these secrets use non-standard keys unknown to the agent.I've detailed what the contents of these two secrets are in https://venafi.atlassian.net/wiki/spaces/~862991627/pages/2429878323/VC-32931+Agent+to+capture+Istio+CA+info+and+send+to+cloud.
I'm not sure what tests are needed here, I'd need help on that.