forked from cert-manager/cert-manager
-
Notifications
You must be signed in to change notification settings - Fork 0
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
[pull] master from cert-manager:master #1066
Open
pull
wants to merge
2,127
commits into
next-stack:master
Choose a base branch
from
cert-manager:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
Signed-off-by: Ashley Davis <[email protected]>
Signed-off-by: Ashley Davis <[email protected]>
Cleanup key gen / RSA key sizes
Signed-off-by: cert-manager-bot <[email protected]>
[CI] Merge self-upgrade-master into master
Signed-off-by: Jochen Richter <[email protected]>
Signed-off-by: Ashley Davis <[email protected]>
add tenantID option to azureDNS managedIdentity
Signed-off-by: Nikola <[email protected]>
Resources with applyset labels will be pruned, which is problematic. Instead of a generic annotation to control label propagation, the applyset labels are always excluded. This should be a good middleground whilst an API for doing this in a more generic way is discussed. The label should not ever be propagated, and so is a safe default. Fixes: #7306 Signed-off-by: Thomas Way <[email protected]>
Signed-off-by: Nikolay Mokrinsky <[email protected]>
Do not propagate applyset labels
Includes a lot of comments explaining how the maxima were calculated. This is _very_ conservative, and assumes we're dealing with RSA keys twice the size of what we actually allow as a maximum. From running the included benchmark it seems the pathological runtime is about 13617196ns (13ms) on an M2 Max which seems acceptable. Signed-off-by: Ashley Davis <[email protected]>
Signed-off-by: Ashley Davis <[email protected]>
Restrict max size of PEM inputs
Signed-off-by: cert-manager-bot <[email protected]>
[CI] Merge self-upgrade-master into master
…ated Signed-off-by: henrick <[email protected]>
Signed-off-by: cert-manager-bot <[email protected]>
[CI] Merge self-upgrade-master into master
Signed-off-by: cert-manager-bot <[email protected]>
[CI] Merge self-upgrade-master into master
Setting renewBeforePercentage to x now makes the certificate renew when there is x percent of its duration left *before* its expiry. For example, if the validity duration of a certificate is 180 minutes, and renewBeforePercentage is set to 25, the certificate will renew after 135 minutes, i.e. when there is 25% of its duration left. This now means the behaviour is in accordance with the spec of renewBeforePercentage. Before this patch, the behaviour was reversed, whereby the certificate would renew *after* x percent of its duration, not *before*. For example, for a certificate valid for 180 minutes, it would renew after 45 minutes. Signed-off-by: Adam Sroka <[email protected]>
Signed-off-by: Nikola <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: cert-manager-bot <[email protected]>
[CI] Self-upgrade merging self-upgrade-master into master
fix acme challenge with ipv6
Signed-off-by: cert-manager-bot <[email protected]>
…f request to kube apiserver/Rate limiting per call to kube apiserver (dropping from 2s)/Total reconciles across all control loops Signed-off-by: Josh Soref <[email protected]>
…ts for secrets to kube apiserver (peaking below 25) Signed-off-by: Josh Soref <[email protected]>
…848 end: 1673267347/runtime is 499 seconds Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: battmdpkq <[email protected]>
chore: fix some function names in comment
Signed-off-by: looklose <[email protected]>
refactor: use a more straightforward return value
Signed-off-by: cert-manager-bot <[email protected]>
[CI] Merge self-upgrade-master into master
Signed-off-by: Ashley Davis <[email protected]>
Signed-off-by: ThatsIvan <[email protected]>
Signed-off-by: ThatsIvan <[email protected]>
fix SHAs for upstream bind images
Signed-off-by: ThatsIvan <[email protected]>
Signed-off-by: cert-manager-bot <[email protected]>
[CI] Merge self-upgrade-master into master
Signed-off-by: ThatsIvan <[email protected]>
Signed-off-by: Ashley Davis <[email protected]>
Bump go-jose to address CVE-2025-27144
fix: cache full DNS response and handle TTL expiration in FindZoneByFqdn
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.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )