Skip to content

Commit

Permalink
Release v0.5.1
Browse files Browse the repository at this point in the history
  • Loading branch information
wvengen committed Jan 8, 2024
1 parent ba64708 commit 689fbf8
Show file tree
Hide file tree
Showing 5 changed files with 16 additions and 6 deletions.
10 changes: 10 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,16 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html),
and is generated by [Changie](https://github.com/miniscruff/changie).

## v0.5.1 - 2024-01-08

### Changed

* Allow configuration of HAProxy image

### Fixed

* Fixed HAProxy image reference

## v0.5.0 - 2024-01-08

### Changed
Expand Down
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ If you've had problems with ingress-nginx, cert-manager, LetsEncrypt ACME HTTP01
## One-line install

```shell
kubectl apply -f https://raw.githubusercontent.com/q-m/hairpin-proxy/v0.5.0/deploy.yml
kubectl apply -f https://raw.githubusercontent.com/q-m/hairpin-proxy/v0.5.1/deploy.yml
```

If you're using [ingress-nginx](https://kubernetes.github.io/ingress-nginx/) and [cert-manager](https://github.com/jetstack/cert-manager), it will work out of the box. See detailed installation and testing instructions below.
Expand Down Expand Up @@ -74,7 +74,7 @@ The `dig` should show the external load balancer IP address. The first `curl` sh
### Step 1: Install hairpin-proxy in your Kubernetes cluster

```shell
kubectl apply -f https://raw.githubusercontent.com/q-m/hairpin-proxy/v0.5.0/deploy.yml
kubectl apply -f https://raw.githubusercontent.com/q-m/hairpin-proxy/v0.5.1/deploy.yml
```

Note that this hairpin-proxy fork discovers ingress controllers and sets `TARGET_SERVER` automatically.
Expand Down Expand Up @@ -131,7 +131,7 @@ To resolve this, we need to rewrite the DNS on the Node itself. The Node does no
To install this DaemonSet:

```shell
kubectl apply -f https://raw.githubusercontent.com/q-m/hairpin-proxy/v0.5.0/deploy-etchosts-daemonset.yml
kubectl apply -f https://raw.githubusercontent.com/q-m/hairpin-proxy/v0.5.1/deploy-etchosts-daemonset.yml
```

_untested with this fork_
Expand Down
2 changes: 1 addition & 1 deletion deploy-etchosts-daemonset.yml
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ spec:
spec:
serviceAccountName: hairpin-proxy-controller-sa
containers:
- image: ghcr.io/q-m/hairpin-proxy-controller:0.5.0
- image: ghcr.io/q-m/hairpin-proxy-controller:0.5.1
name: main
command: ["/app/src/main.rb", "--etc-hosts", "/app/etchosts"]
volumeMounts:
Expand Down
2 changes: 1 addition & 1 deletion deploy.yml
Original file line number Diff line number Diff line change
Expand Up @@ -127,7 +127,7 @@ spec:
runAsUser: 405
runAsGroup: 65533
containers:
- image: ghcr.io/q-m/hairpin-proxy-controller:0.5.0
- image: ghcr.io/q-m/hairpin-proxy-controller:0.5.1
name: main
resources:
requests:
Expand Down
2 changes: 1 addition & 1 deletion hairpin-proxy-controller/src/main.rb
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
require "socket"
require "digest"

VERSION = "0.5.0"
VERSION = "0.5.1"

class HairpinProxyController
COMMENT_LINE_SUFFIX = "# Added by hairpin-proxy"
Expand Down

0 comments on commit 689fbf8

Please sign in to comment.