Skip to content

chore(deps): bump k8s.io/client-go from 0.34.1 to 0.35.0#9

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/k8s.io/client-go-0.35.0
Closed

chore(deps): bump k8s.io/client-go from 0.34.1 to 0.35.0#9
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/k8s.io/client-go-0.35.0

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Dec 18, 2025

Bumps k8s.io/client-go from 0.34.1 to 0.35.0.

Commits
  • 9bcb694 Update dependencies to v0.35.0 tag
  • 2d83546 Merge remote-tracking branch 'origin/master' into release-1.35
  • 56b4af2 Merge pull request #135591 from p0lyn0mial/upstream-watchlist-reflector-log-f...
  • 891f94c Merge remote-tracking branch 'origin/master' into release-1.35
  • 65ffe04 Merge pull request #135580 from serathius/client-go-transformer
  • 2fe4ac2 downgrade reflector watchlist fallback log to V(4)
  • 97256a6 Bump golang.org/x/crypto to v0.45.0
  • 46360b5 Merge pull request #135131 from Dev1622/sig-storage/mock-expand-flake-fix
  • 171ef8c Use transformer in consistency checker
  • 3878a64 vendor: update vendor and license metadata after replacing BeTrue usage in cs...
  • Additional commits viewable in compare view

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

Bumps [k8s.io/client-go](https://github.com/kubernetes/client-go) from 0.34.1 to 0.35.0.
- [Changelog](https://github.com/kubernetes/client-go/blob/master/CHANGELOG.md)
- [Commits](kubernetes/client-go@v0.34.1...v0.35.0)

---
updated-dependencies:
- dependency-name: k8s.io/client-go
  dependency-version: 0.35.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update go code labels Dec 18, 2025
@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github Feb 11, 2026

Superseded by #14.

@dependabot dependabot Bot closed this Feb 11, 2026
@dependabot dependabot Bot deleted the dependabot/go_modules/k8s.io/client-go-0.35.0 branch February 11, 2026 06:14
pigri added a commit that referenced this pull request May 17, 2026
…ress/gateway

Follow-up improvements on the synapse-as-ingress/Gateway controller,
all unit-tested and verified live in k3s.

#1 Gateway API backendRef weight semantics (conformance fix). Was:
   weight 0 treated as equal-weight (0-weight backend still received
   traffic). Now: if any backendRef sets a weight, an unset weight
   defaults to 1 and weight 0 means "receive no traffic" (the backend
   is excluded); only when NO weight is set anywhere is the pool
   rendered unweighted. (k3s: a 0-weight backend is excluded; explicit
   weights and unset->1 are honored.)

#2 Path-match fidelity. rulePaths now honors HTTPRoute Path.Type:
   PathPrefix as-is, Exact used best-effort + warning (synapse v1
   matches longest-prefix), RegularExpression dropped + warning (no
   regex path support, and NOT defaulted to "/"), and header/method/
   queryParam match conditions warned (dropped — synapse v1 routes on
   host+path only). Ingress Exact pathType likewise warned. No more
   silent mis-routing.

#3 IngressClass resolution. isOurs now follows Kubernetes precedence:
   explicit spec.ingressClassName wins; otherwise the legacy
   kubernetes.io/ingress.class annotation; otherwise the default
   IngressClass (ingressclass.kubernetes.io/is-default-class=true with
   spec.controller == ours, resolved once per render). Foreign classes
   are still ignored.

#4 Ingress .status.loadBalancer publishing. Opt-in
   --publish-status-address (csv; IP vs hostname auto-classified),
   patched onto matched Ingresses only on change. Empty = no status
   (never a bogus address).

#7 Observability. Prometheus metrics on controller-runtime's Registry
   (render/changed/errors/reloads/conflicts/unsupported/backend-
   unresolved counters; hosts/routes/last-render/ready gauges).
   Kubernetes Events: Normal Programmed on matched Ingresses on a
   changed render; Warning RouteConflict / BackendUnresolved /
   UnsupportedMatch. Readiness gated on the first successful render via
   a manager Runnable primer (flips even on a zero-Ingress cluster, so
   the proxy isn't advertised ready before synapse has upstreams).
   Event recorder is nil-safe for --render-once.

#8 Service watch. The controller now also watches Services (and
   IngressClasses) so a named-port / Service change re-renders without
   waiting for an unrelated Ingress event.

#9 Reload robustness. --reload-process-name makes the SIGHUP target
   configurable (default "synapse"). A leading+trailing debouncer
   (--reload-debounce, default 500ms) collapses SIGHUP bursts (e.g.
   cert-manager solver churn) while GUARANTEEING the final state is
   applied (trailing edge always fires).

Tests: weight semantics (0/unset/none), rulePaths (exact/regex/
header), isOurs precedence (explicit/legacy/default/foreign), default
IngressClass render, publishStatus IP/hostname + idempotency,
ReadyCheck gating, reloadDebouncer leading/trailing + window<=0,
findReloadTargets named process. go build/vet/test ./... green
(race-clean, gofmt-clean). No new direct deps beyond promoting
prometheus/client_golang (already an indirect dep) to direct.

k3s e2e (host synapse + in-cluster operator sidecar): 33 use-case
assertions — weight-0 exclusion, Exact/regex/header warnings, legacy-
annotation & default-class capture, foreign-class ignored, Ingress
status address, /readyz + full metrics family, Programmed/RouteConflict
/BackendUnresolved events, named-port resolution, Service-only-change
re-render, debounced SIGHUP burst (6 changes -> coalesced, final value
live), public domain still serving 200 end-to-end.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file go Pull requests that update go code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants