Skip to content

Bump pebble (2.6.0 to 2.8.0), coredns, and openssl #47

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Jul 26, 2025
Merged

Bump pebble (2.6.0 to 2.8.0), coredns, and openssl #47

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8a491e4
Bump pebble (2.6.0 to 2.8.0), coredns, and openssl
consideRatio Jul 26, 2025
f08337d
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] Jul 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion DEVELOPMENT_HISTORY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,6 @@ To facilitate testing against an ACME server, we need partial control over DNS r
1. **ACME client independent configuration**

Many ways to configuring Pebble and a DNS requires information about the ACME client's Kubernetes Service's ClusterIP. This information in turn can require _hardcoding_ of a ClusterIP or _first installing the ACME client_.

- Hardcoding the ACME clients ClusterIP isn't great because it requires you to be able to do it, as well as knowledge about the Kubernetes clusters allowed network ranges for Services.
- First installing the ACME client isn't great because it will then startup without the ACME server ready, which may put it in a failure state which needs to be cleared.

Expand Down
2 changes: 1 addition & 1 deletion pebble/Chart.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ version: 0.0.1-set.by.chartpress
## appVersion should be updated along with pebble releases
## ref: https://github.com/letsencrypt/pebble/releases
##
appVersion: "2.6.0"
appVersion: "2.8.0"
description: |
This Helm chart bootstraps Pebble: an ACME server (like Let's Encrypt) meant
for testing. Pebble is also coupled to rely on pebble-challtestsrv as a DNS
Expand Down
7 changes: 4 additions & 3 deletions pebble/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,10 +7,11 @@ pebble:
repository: ghcr.io/letsencrypt/pebble
tag: "" # default is the chart's appVersion, this is an override

# Image for creating certificates
## Image for creating certificates
## ref: https://hub.docker.com/r/alpine/openssl/tags
openssl:
repository: docker.io/alpine/openssl
tag: "3.3.2"
tag: "3.5.1"

## config ref: https://github.com/letsencrypt/pebble/blob/52b92744eaad895ac25b19dae429c0bdd134b764/cmd/pebble/main.go#L17
config:
Expand Down Expand Up @@ -57,7 +58,7 @@ coredns:
## image ref: https://hub.docker.com/r/coredns/coredns/tags
image:
repository: coredns/coredns
tag: "1.11.3"
tag: "1.12.2"

## corefileSegment allow you to inject logic into CoreDNS's configuration
## file, called a Corefile. The example below will resolve all lookups of
Expand Down