This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/go_modules/k8s.io/client-go-0.26.2
in repository https://gitbox.apache.org/repos/asf/apisix-ingress-controller.git
omit ad01dfe4 chore(deps): bump k8s.io/client-go from 0.26.1 to 0.26.2
add 7d62b7e4 chore(deps): bump github.com/gavv/httpexpect/v2 in /test/e2e
(#1706)
add 13d2b5d1 docs: monitoring apisix with helm chart (#1683)
add 879b4338 chore(deps): bump github.com/stretchr/testify from 1.8.1 to
1.8.2 (#1689)
add 5ec21c1e chore(deps): bump golang.org/x/text in /test/e2e/testbackend
(#1684)
add d8f73534 chore(deps): bump k8s.io/client-go from 0.26.1 to 0.26.2 in
/test/e2e (#1705)
add 6ac74e48 chore(deps): bump k8s.io/client-go from 0.26.1 to 0.26.2
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (ad01dfe4)
\
N -- N -- N
refs/heads/dependabot/go_modules/k8s.io/client-go-0.26.2 (6ac74e48)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
docs/en/latest/monitoring.md | 142 +++++++++++++++++++++++++++++++++++++++++++
go.mod | 2 +-
go.sum | 3 +-
test/e2e/go.mod | 4 +-
test/e2e/go.sum | 17 ++++--
test/e2e/testbackend/go.mod | 2 +-
test/e2e/testbackend/go.sum | 23 ++++++-
7 files changed, 182 insertions(+), 11 deletions(-)
create mode 100644 docs/en/latest/monitoring.md
