Skip to content

Commit

Permalink
update to 2.15.0
Browse files Browse the repository at this point in the history
Signed-off-by: nick powell <nickjaypowell@gmail.com>
  • Loading branch information
njayp committed Sep 5, 2023
1 parent c0d5f12 commit 15353e7
Show file tree
Hide file tree
Showing 2 changed files with 96 additions and 21 deletions.
111 changes: 93 additions & 18 deletions docs/latest/releaseNotes.yml
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,81 @@ docDescription: >-
changelog: https://github.com/telepresenceio/telepresence/blob/$branch$/CHANGELOG.md

items:
- version: 2.15.0
date: "2023-08-29"
notes:
- type: security
title: Add ASLR to telepresence binaries
body: >-
ASLR hardens binary sercurity against fixed memory attacks.
- type: feature
title: Added client builds for arm64 architecture.
body: >-
Updated the release workflow files in github actions to including building and publishing the client binaries for arm64 architecture.
docs: https://github.com/telepresenceio/telepresence/issues/3259
- type: bugfix
title: KUBECONFIG env var can now be used with the docker mode.
body: >-
If provided, the KUBECONFIG environment variable was passed to the kubeauth-foreground service as a parameter.
However, since it didn't exist, the CLI was throwing an error when using <code>telepresence connect --docker</code>.
docs: https://github.com/telepresenceio/telepresence/pull/3300
- type: bugfix
title: Fix deadlock while watching workloads
body: >-
The <code>telepresence list --output json-stream</code> wasn't releasing the session's lock after being
stopped, including with a <code>telepresence quit</code>. The user could be blocked as a result.
docs: https://github.com/telepresenceio/telepresence/pull/3298
- type: bugfix
title: Change json output of telepresence list command
body: >-
Replace deprecated info in the JSON output of the telepresence list command.
- version: 2.14.4
date: "2023-08-21"
notes:
- type: bugfix
title: Nil pointer exception when upgrading the traffic-manager.
body: >-
Upgrading the traffic-manager using <code>telepresence helm upgrade</code> would sometimes
result in a helm error message <q>executing "telepresence/templates/intercept-env-configmap.yaml"
at <.Values.intercept.environment.excluded>: nil pointer evaluating interface {}.excluded"</q>
docs: https://github.com/telepresenceio/telepresence/issues/3313
- version: 2.14.2
date: "2023-07-26"
notes:
- type: bugfix
title: Telepresence now use the OSS agent in its latest version by default.
body: >-
The traffic manager admin was forced to set it manually during the chart installation.
docs: https://github.com/telepresenceio/telepresence/issues/3271
- version: 2.14.1
date: "2023-07-07"
notes:
- type: feature
title: Envoy's http idle timout is now configurable.
body: >-
A new <code>agent.helm.httpIdleTimeout</code> setting was added to the Helm chart that controls
the proprietary Traffic agent's http idle timeout. The default of one hour, which in some situations
would cause a lot of resource consuming and lingering connections, was changed to 70 seconds.
- type: feature
title: Add more gauges to the Traffic manager's Prometheus client.
body: >-
Several gauges were added to the Prometheus client to make it easier to monitor
what the Traffic manager spends resources on.
- type: feature
title: Agent Pull Policy
body: >-
Add option to set traffic agent pull policy in helm chart.
- type: bugfix
title: Resource leak in the Traffic manager.
body: >-
Fixes a resource leak in the Traffic manager caused by lingering tunnels between the clients and
Traffic agents. The tunnels are now closed correctly when terminated from the side that created them.
- type: bugfix
title: Fixed problem setting traffic manager namespace using the kubeconfig extension.
body: >-
Fixes a regression introduced in version 2.10.5, making it impossible to set the traffic-manager namespace
using the telepresence.io kubeconfig extension.
docs: https://www.getambassador.io/docs/telepresence/latest/reference/config#manager
- version: 2.14.0
date: "2023-06-12"
notes:
Expand All @@ -49,7 +124,7 @@ items:
exclude a given list of hostnames from resolution, while the mappings field can be used to resolve a hostname with
another.
docs: https://github.com/telepresenceio/telepresence/pull/3172

- type: feature
title: Added the ability to exclude environment variables
body: >-
Expand Down Expand Up @@ -120,7 +195,7 @@ items:

- type: bugfix
title: Fix incorrect error message with local-only mounts
body: >-
body: >-
Running telepresence intercept --local-only --mount false no longer results in an incorrect error message saying "a local-only intercept cannot have mounts".
docs: https://github.com/telepresenceio/telepresence/issues/3171

Expand Down Expand Up @@ -222,57 +297,57 @@ items:
- type: feature
title: Setting of the target IP of the intercept
docs: reference/intercepts/cli
body: >-
There's a new --address flag to the intercept command allowing users to set the target IP of the intercept.
body: >-
There's a new --address flag to the intercept command allowing users to set the target IP of the intercept.
- type: feature
title: Multi-tenant support
body: >-
The client will no longer need cluster wide permissions when connected to a namespace scoped Traffic Manager.
body: >-
The client will no longer need cluster wide permissions when connected to a namespace scoped Traffic Manager.
- type: bugfix
title: Cluster domain resolution bugfix
body: >-
The Traffic Manager now uses a fail-proof way to determine the cluster domain.
body: >-
The Traffic Manager now uses a fail-proof way to determine the cluster domain.
docs: https://github.com/telepresenceio/telepresence/issues/3114

- type: bugfix
title: Windows DNS
body: >-
DNS on windows is more reliable and performant.
DNS on windows is more reliable and performant.
docs: https://github.com/telepresenceio/telepresence/issues/2939

- type: bugfix
title: Agent injection with huge amount of deployments
body: >-
The agent is now correctly injected even with a high number of deployment starting at the same time.
The agent is now correctly injected even with a high number of deployment starting at the same time.
docs: https://github.com/telepresenceio/telepresence/issues/3025

- type: bugfix
title: Self-contained kubeconfig with Docker
body: >-
The kubeconfig is made self-contained before running Telepresence daemon in a Docker container.
The kubeconfig is made self-contained before running Telepresence daemon in a Docker container.
docs: https://github.com/telepresenceio/telepresence/issues/3099

- type: bugfix
title: Version command error
body: >-
The version command won't throw an error anymore if there is no kubeconfig file defined.
body: >-
The version command won't throw an error anymore if there is no kubeconfig file defined.
docs: https://github.com/telepresenceio/telepresence/issues/3095

- version: 2.12.2
date: "2023-04-04"
notes:
- type: security
title: Update Golang build version to 1.20.3
body: >-
body: >-
Update Golang to 1.20.3 to address CVE-2023-24534, CVE-2023-24536, CVE-2023-24537, and CVE-2023-24538
- version: 2.12.1
date: "2023-03-22"
notes:
- type: feature
title: Additions to gather-logs
body: >-
body: >-
Telepresence now includes the kubeauth logs when running
the gather-logs command
- type: bugfix
Expand All @@ -286,7 +361,7 @@ items:
- type: feature
title: Check for service connectivity independently from pod connectivity
body: >-
Telepresence now enables you to check for a service and pod's connectivity independently, so that it can proxy one without proxying the other.
Telepresence now enables you to check for a service and pod's connectivity independently, so that it can proxy one without proxying the other.
docs: https://github.com/telepresenceio/telepresence/issues/2911
- type: bugfix
title: Fix cluster authentication when running the telepresence daemon in a docker container.
Expand All @@ -295,7 +370,7 @@ items:
docs: https://github.com/telepresenceio/telepresence/pull/3055
- type: bugfix
body: >-
Telepresence will not longer panic when a CNAME does not contain the .svc in it
Telepresence will not longer panic when a CNAME does not contain the .svc in it
title: Fix panic when CNAME of kubernetes.default doesn't contain .svc
docs: https://github.com/telepresenceio/telepresence/issues/3015
- version: 2.11.1
Expand Down
6 changes: 3 additions & 3 deletions docs/latest/versions.yml
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
version: "2.14.4"
dlVersion: "v2.14.4"
docsVersion: "2.14"
version: "2.15.0"
dlVersion: "v2.15.0"
docsVersion: "2.15"
branch: release/v2
productName: "Telepresence OSS"

0 comments on commit 15353e7

Please sign in to comment.