-
Notifications
You must be signed in to change notification settings - Fork 187
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
Adopt Kubernetes style TLS Secrets #1194
Merged
Merged
Conversation
This file contains 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
4 tasks
aryan9600
force-pushed
the
tls-secret
branch
2 times, most recently
from
August 10, 2023 08:20
5bde40e
to
bba3179
Compare
hiddeco
reviewed
Aug 10, 2023
sftim
reviewed
Aug 12, 2023
sftim
reviewed
Aug 12, 2023
sftim
reviewed
Aug 12, 2023
aryan9600
force-pushed
the
tls-secret
branch
3 times, most recently
from
August 16, 2023 10:19
19902cc
to
77a31f4
Compare
darkowlzz
reviewed
Aug 16, 2023
aryan9600
force-pushed
the
tls-secret
branch
3 times, most recently
from
August 18, 2023 11:17
fc31743
to
7857297
Compare
aryan9600
added
enhancement
New feature or request
area/security
Security related issues and pull requests
area/api
API related issues and pull requests
labels
Aug 18, 2023
aryan9600
changed the title
Adopt Kubernetes style TLS Secret
Adopt Kubernetes style TLS Secrets
Aug 18, 2023
darkowlzz
reviewed
Aug 21, 2023
aryan9600
force-pushed
the
tls-secret
branch
2 times, most recently
from
August 22, 2023 08:56
0dbcd4e
to
185d9ea
Compare
darkowlzz
reviewed
Aug 22, 2023
aryan9600
force-pushed
the
tls-secret
branch
2 times, most recently
from
August 22, 2023 11:55
6384bf3
to
23f6764
Compare
darkowlzz
approved these changes
Aug 22, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Adopt Kubernetes TLS secrets API to check for TLS data in the Secret referred to by `.spec.certSecretRef`, i.e. check for keys `tls.crt` and `tls.key` for the certificate and private key. Use `ca.crt` for the CA certificate. Signed-off-by: Sanskar Jaiswal <[email protected]>
Adopt Kubernetes TLS secrets API to check for TLS data in the Secret referred to by `.spec.certSecretRef`, i.e. check for keys `tls.crt` and `tls.key` for the certificate and private key. Use `ca.crt` for the CA certificate. Deprecate the usage of `caFile`, `certFile` and `keyFile` keys. Signed-off-by: Sanskar Jaiswal <[email protected]>
Check the auth secret for the `ca.crt` key for CA certificate data. `ca.crt` takes precdence over `caFile`. Signed-off-by: Sanskar Jaiswal <[email protected]>
stefanprodan
approved these changes
Aug 22, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks @aryan9600 🥇
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/api
API related issues and pull requests
area/security
Security related issues and pull requests
enhancement
New feature or request
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.
Modify
.spec.certSecretRef
HelmRepository and OCIRepository to use the keys expected in a Kubernetes Secret of type TLS,tls.crt
andtls.key
. Furthermore useca.crt
for specifying the CA certificate.Deprecate the usage of
certFile
,keyFile
andcaFile
for OCIRepository. BothcaFile
andca.crt
are supported for GitRepository with the latter taking precedence.Part of: fluxcd/flux2#4137