RATATOSK
← 전체 릴리스

Emissary-Ingressv3.10.0

호환성 변경 2중요 수정 1기능·개선 1의존성 갱신 3기타 5

Emissary-Ingress 알림 받기

확인할 변경이 있을 때만 주 1회, critical 보안 공지는 즉시 발송

업그레이드 전 확인

업그레이드 안내1
신규 설치 및 업그레이드 빠른 시작
    See the [Quickstart](https://emissary-ingress.dev/docs/3.10/quick-start/) for more details.
github.com/emissary-ingress/emissary/releases/tag/v3.10.0

호환성 변경2

공개된 YAML 매니페스트에서 Ambassador Agent 기본 설치 제외

영향 대상공개된 YAML 매니페스트로 Emissary-ingress를 설치하는 경우

Ambassador Agent는 Emissary-ingress에 추가 기능을 제공합니다.

원문 보기
- Change: Emissary-ingress will no longer publish YAML manifest with the Ambassador Agent being
  installed by default. This is an optional component that provides additional features on top of
  Emissary-ingress and we recommend installing it using the instructions found in the <a
  href="https://github.com/datawire/ambassador-agenty">Ambassador Agent Repo</a>.
github.com/emissary-ingress/emissary/blob/v3.10.0/CHANGELOG.md

Emissary 이미지와 Helm 차트의 GHCR 등록

영향 대상Emissary 이미지 또는 Helm 차트 배포(추정)

Emissary 이미지는 DockerHub에서 호스팅되었습니다. 이번 릴리스 노트에는 메인 이미지가 ghcr.io/emissary-ingress/emissary:3.10.0에, CRD 차트와 컨트롤 플레인 차트가 각각 ghcr.io/emissary-ingress/emissary-crds-charts와 ghcr.io/emissary-ingress/emissary-chart에 기재되어 있습니다. 차트의 이전 위치는 노트에 나와 있지 않습니다.

원문 보기
- Change: The Emissary images are now hosted at GHCR rather than at DockerHub.
    - The main Emissary image is at `ghcr.io/emissary-ingress/emissary:3.10.0`
    - The (new) Helm chart for the Emissary CRDs is at `ghcr.io/emissary-ingress/emissary-crds-charts`
    - The Helm chart for the Emissary control plane is at `ghcr.io/emissary-ingress/emissary-chart`
github.com/emissary-ingress/emissary/releases/tag/v3.10.0

중요 수정1

  • ambex 라우트 해싱 중 MD5 패닉 수정
    영향 대상ambex로 V3 리스너를 RDS 리스너로 변환하는 Emissary 설치 환경(추정)

    FIPS와 같이 암호화가 제한된 환경에서 필터 체인 매치를 해싱할 때 ambex가 openssl: MD5 failed 오류와 함께 패닉을 일으킬 수 있었습니다.

    - Change: The `ambex` component of Emissary-ingress now uses `xxhash64` instead of `md5`, since
      `md5` can cause problems in crypto-restricted environments (e.g. FIPS) ([Remove usage of md5])
    [Remove usage of md5]: https://github.com/emissary-ingress/emissary/pull/5794
    github.com/emissary-ingress/emissary/blob/v3.10.0/CHANGELOG.md

기능·개선1

의존성 갱신3

    그 외 3건 · 보안 언급 없음
    • - Feature: This upgrades Emissary-ingress to be built on Envoy v1.28.0 which provides security, performance and feature enhancements. You can read more about them here: <a href="https://www.envoyproxy.io/docs/envoy/v1.28.0/version_history/version_history">Envoy Proxy 1.28.0 Release Notes</a>
    • - Change: Upgraded Emissary-ingress to the latest release of Golang as part of our general dependency upgrade process.
    • - Change: Upgraded Emissary-ingress to the latest release of Golang as part of our general dependency upgrade process.
    기타5
    • 공개 YAML 매니페스트에서 Ambassador Agent 기본 설치 중단
      - Change: Emissary-ingress will no longer publish YAML manifests with the Ambassador Agent being
        installed by default.
      github.com/emissary-ingress/emissary/releases/tag/v3.10.0
    • 정규식 헤더 Mapping의 캐시 키에 Mapping 이름 사용
      - Bugfix: Emissary-ingress was incorrectly caching Mappings with regex headers using the header name
        instead of the Mapping name, which could reduce the cache's effectiveness. This has been fixed so
        that the correct key is used. ([Incorrect Cache Key for Mapping])
      github.com/emissary-ingress/emissary/releases/tag/v3.10.0
    • 정규식 헤더 Mapping의 캐시 키에 Mapping 이름 사용
      - Bugfix: Emissary-ingress was incorrectly caching Mappings with regex headers using the header name
        instead of the Mapping name, which could reduce the cache's effectiveness. This has been fixed so
        that the correct key is used. ([Incorrect Cache Key for Mapping])
      [Incorrect Cache Key for Mapping]: https://github.com/emissary-ingress/emissary/issues/5714
      - Bugfix: Emissary-ingress was incorrectly caching Mappings with regex headers using the header name
        instead of the Mapping name, which could reduce the cache's effectiveness. This has been fixed so
        that the correct key is used. ([Incorrect Cache Key for Mapping])
      [Incorrect Cache Key for Mapping]: https://github.com/emissary-ingress/emissary/issues/5714
      github.com/emissary-ingress/emissary/releases/tag/v3.10.0
    • Envoy v1.28.0 기반 Emissary-ingress
      - Feature: This upgrades Emissary-ingress to be built on Envoy v1.28.0 which provides security,
        performance and feature enhancements. You can read more about them here: <a
        href="https://www.envoyproxy.io/docs/envoy/v1.28.0/version_history/version_history">Envoy Proxy
        1.28.0 Release Notes</a>
      github.com/emissary-ingress/emissary/blob/v3.10.0/CHANGELOG.md
    • 외부 인증 서비스로 전달되는 클라이언트 TLS 정보
      - Feature: Emissary-ingress now passes the client TLS certificate and SNI, if any, to the external
        auth service. These are available in the `source.certificate` and `tls_session.sni` fields, as
        described in the <a
        href="https://www.envoyproxy.io/docs/envoy/latest/api-v3/service/auth/v3/attribute_context.proto">
        Envoy extauth documentation</a>.
      github.com/emissary-ingress/emissary/blob/v3.10.0/CHANGELOG.md

    정리 내용은 AI가 작성하므로 틀릴 수 있으며, 보증 없이 제공합니다.