Bump Cert-manager version in installation documentation#464
Open
github-actions[bot] wants to merge 2 commits intomainfrom
Open
Bump Cert-manager version in installation documentation#464github-actions[bot] wants to merge 2 commits intomainfrom
github-actions[bot] wants to merge 2 commits intomainfrom
Conversation
Made with ❤️️ by updatecli
✅ Deploy Preview for epinio-docs-staging ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Made with ❤️️ by updatecli
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
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.
Bump Cert-manager version in installation documentation
docs: update cert-manager referenced version v1.20.0
2 file(s) updated with "https://github.com/cert-manager/cert-manager/releases/download/v1.20.0/": * docs/installation/other_inst_scenarios/install_epinio_on_rancher_desktop.md * docs/tutorials/single-dev-workflow.md
v1.20.0
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters. v1.20.0 adds support for the new ListenerSet resource, adds support for Azure Private DNS; parentRefs are no longer required when using ACME with Gateway API, and OtherNames was promoted to Beta. ## Changes by Kind ### Feature - Added a set of flags to permit setting NetworkPolicy across all deployed containers. Remove redundant global IP ranges from example policies. (#8370, @jcpunk) - Added selectable fields to custom resource definitions for .spec.issuerRef.{group, kind, name} (#8256, @tareksha) - Added support for specifying `imagePullSecrets` in the `startupapicheck-job` Helm template to enable pulling images from private registries. (#8186, @mathieu-clnk) - Added 'extraContainers' helm chart value, allowing the deployment of arbitrary sidecar containers within the cert-manager operator pod. This can be used to support, for e.g., AWS IAM Roles Anywhere for Route53 DNS01 verification. (#8355, @dancmeyers) - Added `parentRef` override annotations on the Certificate resource. (#8518, @hjoshi123) - Added support for azure private zones for dns01 issuer. (#8494, @hjoshi123) - Added support for configuring PEM decoding size limits, allowing operators to handle larger certificates and keys. (#7642, @robertlestak) - Added support for unhealthyPodEvictionPolicy in PodDisruptionBudget (#7728, @jcpunk) - For Venafi provider, read `venafi.cert-manager.io/custom-fields` annotation on Issuer/ClusterIssuer and use it as base with override/append capabilities on Certificate level. (#8301, @k0da) - Improve error message when CA issuers are misconfigured to use a clashing secret name (#8374, @majiayu000) - Introduce a new Ingress annotation `acme.cert-manager.io/http01-ingress-ingressclassname` to override `http01.ingress.ingressClassName` field in HTTP-01 challenge solvers. (#8244, @lunarwhite) - Update `global.nodeSelector` to helm chart to perform a `merge` and allow for a single `nodeSelector` to be set across all services. (#8195, @StingRayZA) - Vault issuers will now include the Vault server address as one of the default audiences on generated service account tokens. (#8228, @terinjokes) - Added experimental `XListenerSet` feature gate (#8394, @hjoshi123) ### Documentation - Add GWAPI documentation to NOTES.TXT in helm chart (#8353, @jaxels10) ### Bug or Regression - Adds logs for cases when acme server returns us a fatal error in the order controller (#8199, @Peac36) - Fixed an issue where kind or group in the issuerRef of a Certificate was omitted, upgrading to 1.19.x incorrectly caused the certificate to be renewed (#8160, @inteon) - Changes to the Duration and RenewBefore annotations on ingress and gateway-api resources will now trigger certificate updates. (#8232, @eleanor-merry) - Fix an issue where ACME challenge TXT records are not cleaned up when there are many resource records in CloudDNS. (#8456, @tkna) - Fix unregulated retries with the DigitalOcean DNS-01 solver Add full detailed DNS-01 errors to the events attached to the Challenge, for easier debugging (#8221, @wallrj-cyberark) - Fixed an infinite re-issuance loop that could occur when an issuer returns a certificate with a public key that doesn't match the CSR. The issuing controller now validates the certificate before storing it and fails with backoff on mismatch. (#8403, @calm329) - Fixed an issue where HTTP-01 challenges failed when the Host header contains an IPv6 address. This means that users can now issue IP address certificates for IPv6 address subjects. (#8424, @SlashNephy) - Fixed the HTTP-01 Gateway solver creating invalid HTTPRoutes by not setting spec.hostnames when the challenge DNSName is an IP address. (#8443, @alviss7) - Revert API defaults for issuer reference kind and group introduced in 0.19.0 (#8173, @erikgb) - Security (MODERATE): Fix a potential panic in the cert-manager controller when a DNS response in an unexpected order was cached. If an attacker was able to modify DNS responses (or if they controlled the DNS server) it was possible to cause denial of service for the cert-manager controller. (#8469, @SgtCoDFish) - Update Go to `v1.25.5` to fix `CVE-2025-61727` and `CVE-2025-61729` (#8290, @octo-sts[bot]) - When Prometheus monitoring is enabled, the metrics label is now set to the intended value of `cert-manager`. Previously, it was set depending on various factors (namespace cert-manager is installed in and/or Helm release name). (#8162, @LiquidPL) ### Other (Cleanup or Flake) - Promoted the OtherNames feature to Beta and enabled it by default (#8288, @wallrj-cyberark) - Promoting `xlistenerset` feature gate to `listenerset` (#8501, @hjoshi123) - Rebranding of the Venafi Issuer to CyberArk (#8215, @iossifbenbassat123) - Switched to SSA for challenge finalizer updates (#8519, @inteon) - The default container user (UID) is now 65532 (previously 1000) and the default container group (GID) is now 65532 (previously 0) (#8408, @wallrj-cyberark) - The feature-gate DefaultPrivateKeyRotationPolicyAlways moved from Beta to GA and can no longer be disabled. (#8287, @wallrj-cyberark) - Update cert-manager's ACME client, forked from golang/x/crypto (#8268, @SgtCoDFish) - Use the latest version of Kyverno (1.16.2) in the best-practice installation tests (#8389, @wallrj-cyberark) - We stopped testing with Coutour due to it not supporting the new XListenerSet resource, and moved to kgateway. (#8426, @hjoshi123)v1.20.0-beta.0
v1.20.0-alpha.1
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters. This is a pre-release for cert-manager v1.20.0. Please help with testing! ## Changed since v1.20.0-alpha.0 This alpha release adds experimental XListenerSet support, NetworkPolicy and CRD selectable field features, fixes critical bugs including an infinite re-issuance loop and IPv6 HTTP-01 challenge issues, patches security vulnerabilities (CVE-2025-61727, CVE-2025-61729), promotes OtherNames to Beta and DefaultPrivateKeyRotationPolicyAlways to GA, and changes the default container UID/GID from 1000/0 to 65532/65532. ### Feature - Added experimental `XListenerSet` feature gate (#8394, @hjoshi123) - Add a set of flags to permit setting NetworkPolicy across all deployed containers. Remove redundant global IP ranges from example policies. (#8370, @jcpunk) - Add selectable fields to custom resource definitions for .spec.issuerRef.{group, kind, name} (#8256, @tareksha) - Added 'extraContainers' helm chart value, allowing the deployment of arbitrary sidecar containers within the cert-manager operator pod. This can be used to support, for e.g., AWS IAM Roles Anywhere for Route53 DNS01 verification. (#8355, @dancmeyers) - Added support for unhealthyPodEvictionPolicy in PodDisruptionBudget (#7728, @jcpunk) - For Venafi provider, read `venafi.cert-manager.io/custom-fields` annotation on Issuer/ClusterIssuer and use it as base with override/append capabilities on Certificate level. (#8301, @k0da) - Improve error message when CA issuers are misconfigured to use a clashing secret name (#8374, @majiayu000) - Introduce a new Ingress annotation `acme.cert-manager.io/http01-ingress-ingressclassname` to override `http01.ingress.ingressClassName` field in HTTP-01 challenge solvers. (#8244, @lunarwhite) - Update `global.nodeSelector` to helm chart to perform a `merge` and allow for a single `nodeSelector` to be set across all services. (#8195, @StingRayZA) - Vault issuers will now include the Vault server address as one of the default audiences on generated service account tokens. (#8228, @terinjokes) ### Bug or Regression - Changes to the Duration and RenewBefore annotations on ingress and gateway-api resources will now trigger certificate updates. (#8232, @eleanor-merry) - Fixed an infinite re-issuance loop that could occur when an issuer returns a certificate with a public key that doesn't match the CSR. The issuing controller now validates the certificate before storing it and fails with backoff on mismatch. (#8403, @calm329) - Fixed an issue where HTTP-01 challenges failed when the Host header containing an IPv6 address. This means that users can now issue IP address certificates for IPv6 address subjects. (#8424, @SlashNephy) - Fixed the HTTP-01 Gateway solver creating invalid HTTPRoutes by not setting spec.hostnames when the challenge DNSName is an IP address. (#8443, @alviss7) - Update Go to `v1.25.5` to fix `CVE-2025-61727` and `CVE-2025-61729` (#8290, @octo-sts[bot]) ### Other (Cleanup or Flake) - Promoted the OtherNames feature to Beta and enabled it by default (#8288, @wallrj-cyberark) - The default container user (UID) is now 65532 (previously 1000) and the default container group (GID) is now 65532 (previously 0) (#8408, @wallrj-cyberark) - The feature-gate DefaultPrivateKeyRotationPolicyAlways moved from Beta to GA and can no longer be disabled. (#8287, @wallrj-cyberark) - Update cert-manager's ACME client, forked from golang/x/crypto (#8268, @SgtCoDFish) - Use the latest version of Kyverno (1.16.2) in the best-practice installation tests (#8389, @wallrj-cyberark) - Rebranding of the Venafi Issuer to CyberArk (#8215, @iossifbenbassat123) - Add GWAPI documentation to NOTES.TXT in helm chart (#8353, @jaxels10) - We stopped testing with Coutour due to it not supporting the new XListenerSet resource, and moved to kgateway. (#8426, @hjoshi123) <details> <summary>Dependencies Changes</summary> ### Added - github.com/aws/aws-sdk-go-v2/service/signin: [v1.0.5](https://github.com/aws/aws-sdk-go-v2/service/signin/tree/v1.0.5) - github.com/go-openapi/testify/v2: [v2.0.2](https://github.com/go-openapi/testify/v2/tree/v2.0.2) ### Changed - cloud.google.com/go/auth: v0.17.0 → v0.18.1 - github.com/Azure/azure-sdk-for-go/sdk/azcore: [v1.19.1 → v1.21.0](https://github.com/Azure/azure-sdk-for-go/sdk/azcore/compare/v1.19.1...v1.21.0) - github.com/Azure/azure-sdk-for-go/sdk/azidentity: [v1.13.0 → v1.13.1](https://github.com/Azure/azure-sdk-for-go/sdk/azidentity/compare/v1.13.0...v1.13.1) - github.com/AzureAD/microsoft-authentication-library-for-go: [v1.5.0 → v1.6.0](https://github.com/AzureAD/microsoft-authentication-library-for-go/compare/v1.5.0...v1.6.0) - github.com/GoogleCloudPlatform/opentelemetry-operations-go/detectors/gcp: [v1.29.0 → v1.30.0](https://github.com/GoogleCloudPlatform/opentelemetry-operations-go/detectors/gcp/compare/v1.29.0...v1.30.0) - github.com/Masterminds/semver/v3: [v3.3.1 → v3.4.0](https://github.com/Masterminds/semver/v3/compare/v3.3.1...v3.4.0) - github.com/Venafi/vcert/v5: [v5.12.2 → v5.12.3](https://github.com/Venafi/vcert/v5/compare/v5.12.2...v5.12.3) - github.com/akamai/AkamaiOPEN-edgegrid-golang/v12: [v12.1.0 → v12.3.0](https://github.com/akamai/AkamaiOPEN-edgegrid-golang/v12/compare/v12.1.0...v12.3.0) - github.com/aws/aws-sdk-go-v2/config: [v1.31.16 → v1.32.7](https://github.com/aws/aws-sdk-go-v2/config/compare/v1.31.16...v1.32.7) - github.com/aws/aws-sdk-go-v2/credentials: [v1.18.20 → v1.19.7](https://github.com/aws/aws-sdk-go-v2/credentials/compare/v1.18.20...v1.19.7) - github.com/aws/aws-sdk-go-v2/feature/ec2/imds: [v1.18.12 → v1.18.17](https://github.com/aws/aws-sdk-go-v2/feature/ec2/imds/compare/v1.18.12...v1.18.17) - github.com/aws/aws-sdk-go-v2/internal/configsources: [v1.4.12 → v1.4.17](https://github.com/aws/aws-sdk-go-v2/internal/configsources/compare/v1.4.12...v1.4.17) - github.com/aws/aws-sdk-go-v2/internal/endpoints/v2: [v2.7.12 → v2.7.17](https://github.com/aws/aws-sdk-go-v2/internal/endpoints/v2/compare/v2.7.12...v2.7.17) - github.com/aws/aws-sdk-go-v2/service/internal/accept-encoding: [v1.13.2 → v1.13.4](https://github.com/aws/aws-sdk-go-v2/service/internal/accept-encoding/compare/v1.13.2...v1.13.4) - github.com/aws/aws-sdk-go-v2/service/internal/presigned-url: [v1.13.12 → v1.13.17](https://github.com/aws/aws-sdk-go-v2/service/internal/presigned-url/compare/v1.13.12...v1.13.17) - github.com/aws/aws-sdk-go-v2/service/route53: [v1.59.2 → v1.62.1](https://github.com/aws/aws-sdk-go-v2/service/route53/compare/v1.59.2...v1.62.1) - github.com/aws/aws-sdk-go-v2/service/sso: [v1.30.0 → v1.30.9](https://github.com/aws/aws-sdk-go-v2/service/sso/compare/v1.30.0...v1.30.9) - github.com/aws/aws-sdk-go-v2/service/ssooidc: [v1.35.4 → v1.35.13](https://github.com/aws/aws-sdk-go-v2/service/ssooidc/compare/v1.35.4...v1.35.13) - github.com/aws/aws-sdk-go-v2/service/sts: [v1.39.0 → v1.41.6](https://github.com/aws/aws-sdk-go-v2/service/sts/compare/v1.39.0...v1.41.6) - github.com/aws/aws-sdk-go-v2: [v1.39.5 → v1.41.1](https://github.com/aws/aws-sdk-go-v2/compare/v1.39.5...v1.41.1) - github.com/aws/smithy-go: [v1.23.2 → v1.24.0](https://github.com/aws/smithy-go/compare/v1.23.2...v1.24.0) - github.com/cncf/xds/go: [2ac532f → 0feb691](https://github.com/cncf/xds/go/compare/2ac532f...0feb691) - github.com/digitalocean/godo: [v1.167.0 → v1.173.0](https://github.com/digitalocean/godo/compare/v1.167.0...v1.173.0) - github.com/envoyproxy/go-control-plane/envoy: [v1.32.4 → v1.35.0](https://github.com/envoyproxy/go-control-plane/envoy/compare/v1.32.4...v1.35.0) - github.com/envoyproxy/go-control-plane: [v0.13.4 → 75eaa19](https://github.com/envoyproxy/go-control-plane/compare/v0.13.4...75eaa19) - github.com/go-jose/go-jose/v4: [v4.1.2 → v4.1.3](https://github.com/go-jose/go-jose/v4/compare/v4.1.2...v4.1.3) - github.com/go-openapi/jsonpointer: [v0.22.1 → v0.22.4](https://github.com/go-openapi/jsonpointer/compare/v0.22.1...v0.22.4) - github.com/go-openapi/jsonreference: [v0.21.2 → v0.21.4](https://github.com/go-openapi/jsonreference/compare/v0.21.2...v0.21.4) - github.com/go-openapi/swag/jsonname: [v0.25.1 → v0.25.4](https://github.com/go-openapi/swag/jsonname/compare/v0.25.1...v0.25.4) - github.com/google/gnostic-models: [v0.7.0 → v0.7.1](https://github.com/google/gnostic-models/compare/v0.7.0...v0.7.1) - github.com/google/pprof: [d1b30fe → 27863c8](https://github.com/google/pprof/compare/d1b30fe...27863c8) - github.com/googleapis/enterprise-certificate-proxy: [v0.3.6 → v0.3.11](https://github.com/googleapis/enterprise-certificate-proxy/compare/v0.3.6...v0.3.11) - github.com/googleapis/gax-go/v2: [v2.15.0 → v2.16.0](https://github.com/googleapis/gax-go/v2/compare/v2.15.0...v2.16.0) - github.com/hashicorp/vault/sdk: [v0.20.0 → v0.21.0](https://github.com/hashicorp/vault/sdk/compare/v0.20.0...v0.21.0) - github.com/miekg/dns: [v1.1.68 → v1.1.72](https://github.com/miekg/dns/compare/v1.1.68...v1.1.72) - github.com/onsi/ginkgo/v2: [v2.22.0 → v2.27.2](https://github.com/onsi/ginkgo/v2/compare/v2.22.0...v2.27.2) - github.com/onsi/gomega: [v1.36.1 → v1.38.2](https://github.com/onsi/gomega/compare/v1.36.1...v1.38.2) - github.com/sagikazarmark/locafero: [v0.10.0 → v0.11.0](https://github.com/sagikazarmark/locafero/compare/v0.10.0...v0.11.0) - github.com/spf13/afero: [v1.14.0 → v1.15.0](https://github.com/spf13/afero/compare/v1.14.0...v1.15.0) - github.com/spf13/cast: [v1.9.2 → v1.10.0](https://github.com/spf13/cast/compare/v1.9.2...v1.10.0) - github.com/spf13/cobra: [v1.10.1 → v1.10.2](https://github.com/spf13/cobra/compare/v1.10.1...v1.10.2) - github.com/spf13/viper: [v1.20.1 → v1.21.0](https://github.com/spf13/viper/compare/v1.20.1...v1.21.0) - github.com/spiffe/go-spiffe/v2: [v2.5.0 → v2.6.0](https://github.com/spiffe/go-spiffe/v2/compare/v2.5.0...v2.6.0) - go.etcd.io/bbolt: v1.4.2 → v1.4.3 - go.etcd.io/etcd/api/v3: v3.6.4 → v3.6.5 - go.etcd.io/etcd/client/pkg/v3: v3.6.4 → v3.6.5 - go.etcd.io/etcd/client/v3: v3.6.4 → v3.6.5 - go.etcd.io/etcd/pkg/v3: v3.6.4 → v3.6.5 - go.etcd.io/etcd/server/v3: v3.6.4 → v3.6.5 - go.opentelemetry.io/auto/sdk: v1.1.0 → v1.2.1 - go.opentelemetry.io/contrib/detectors/gcp: v1.36.0 → v1.38.0 - go.opentelemetry.io/otel/metric: v1.37.0 → v1.39.0 - go.opentelemetry.io/otel/sdk/metric: v1.37.0 → v1.39.0 - go.opentelemetry.io/otel/sdk: v1.37.0 → v1.39.0 - go.opentelemetry.io/otel/trace: v1.37.0 → v1.39.0 - go.opentelemetry.io/otel: v1.37.0 → v1.39.0 - go.uber.org/zap: v1.27.0 → v1.27.1 - go.yaml.in/yaml/v2: v2.4.2 → v2.4.3 - golang.org/x/crypto: v0.43.0 → v0.47.0 - golang.org/x/mod: v0.28.0 → v0.31.0 - golang.org/x/net: v0.46.0 → v0.49.0 - golang.org/x/oauth2: v0.32.0 → v0.34.0 - golang.org/x/sync: v0.17.0 → v0.19.0 - golang.org/x/sys: v0.37.0 → v0.40.0 - golang.org/x/telemetry: aef8a43 → 8fff8a5 - golang.org/x/term: v0.36.0 → v0.39.0 - golang.org/x/text: v0.30.0 → v0.33.0 - golang.org/x/tools: v0.37.0 → v0.40.0 - google.golang.org/api: v0.254.0 → v0.262.0 - google.golang.org/genproto/googleapis/api: a7a43d2 → ff82c1b - google.golang.org/genproto/googleapis/bytestream: 3a174f9 → 409b4a9 - google.golang.org/genproto/googleapis/rpc: 3a174f9 → 409b4a9 - google.golang.org/genproto: 513f239 → ff82c1b - google.golang.org/grpc: v1.76.0 → v1.78.0 - google.golang.org/protobuf: v1.36.10 → v1.36.11 - k8s.io/api: v0.34.1 → v0.35.0 - k8s.io/apiextensions-apiserver: v0.34.1 → v0.35.0 - k8s.io/apimachinery: v0.34.1 → v0.35.0 - k8s.io/apiserver: v0.34.1 → v0.35.0 - k8s.io/client-go: v0.34.1 → v0.35.0 - k8s.io/code-generator: v0.34.1 → v0.35.0 - k8s.io/component-base: v0.34.1 → v0.35.0 - k8s.io/gengo/v2: c297c0c → ec3ebc5 - k8s.io/kms: v0.34.1 → v0.35.0 - k8s.io/kube-aggregator: v0.34.1 → v0.35.0 - k8s.io/kube-openapi: 589584f → 4e65d59 - k8s.io/utils: 0af2bda → bc988d5 - sigs.k8s.io/controller-runtime: v0.22.4 → v0.23.1 - sigs.k8s.io/gateway-api: v1.4.0 → v1.4.1 - sigs.k8s.io/structured-merge-diff/v6: v6.3.0 → d9cc664 - software.sslmate.com/src/go-pkcs12: v0.6.0 → v0.7.0 ### Removed - github.com/zeebo/errs: [v1.4.0](https://github.com/zeebo/errs/tree/v1.4.0) </details>v1.20.0-alpha.0
v1.19.4
v1.19.3
Created automatically by Updatecli
Options:
Most of Updatecli configuration is done via its manifest(s).
Feel free to report any issues at github.com/updatecli/updatecli.
If you find this tool useful, do not hesitate to star our GitHub repository as a sign of appreciation, and/or to tell us directly on our chat!