Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCPBUGS-18707: [bot] Bump openshift/prometheus-operator to v0.69.0 #255

Merged
merged 148 commits into from Nov 7, 2023

Conversation

openshift-monitoring-bot[bot]
Copy link

Description

This is an automated version bump from CI.
If you wish to perform this manually, execute the following commands from openshift/prometheus-operator repo,

git fetch https://github.com/prometheus-operator/prometheus-operator --tags
if ! git merge refs/tags/v0.69.0 --no-edit; then
  git checkout --theirs CHANGELOG.md Documentation VERSION bundle.yaml example go.mod go.sum pkg
  git checkout --ours 
  git add CHANGELOG.md Documentation VERSION bundle.yaml example go.mod go.sum pkg 
  git merge --continue
fi
go mod tidy
go mod vendor

if [ -f scripts/rh-manifest.sh ]; then
  bash scripts/rh-manifest.sh
  git add rh-manifest.txt
  git diff --cached --exit-code || git commit -s -m "[bot] update rh-manifest.txt"
fi

simonpasquier and others added 30 commits September 8, 2023 17:25
Signed-off-by: Simon Pasquier <spasquie@redhat.com>
* alertmanager: add missing types

alertmanager v0.26 introduced some new types in receiver configuration

Fixes prometheus-operator#5857

* pkg/alertmanager: add BotTokenFile to telegramConfig

alertmanager v0.26 introduced some new types in receiver configuration

* pkg/alertmanager: add input sanitize and unit test

add input sanitize and unit test for new alertmanager types
Telegram: bot_token_file
Webhook: url_file
Pushover: user_key_file and token_file

fix: prometheus-operator#5857

* fix format

* pkg/alertmanger: remove changes for telegram bot_toke_file

The telegram bot_token_file is already handle in prometheus-operator#5882

* pkg/alertmanager: revert name change in telegramconfig

---------

Co-authored-by: Hendrik Ferber <ferber@synyx.de>
The `--as` argument allows to run the operator while impersonating a
different user. It's useful to run the operator outside of the cluster
as a service account instead of `kubeadmin`.

Signed-off-by: Simon Pasquier <spasquie@redhat.com>
…r#5907)

Bumps [docker/login-action](https://github.com/docker/login-action) from 2 to 3.
- [Release notes](https://github.com/docker/login-action/releases)
- [Commits](docker/login-action@v2...v3)

---
updated-dependencies:
- dependency-name: docker/login-action
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…onate-user

feat: add `--as` CLI argument
…er errors (prometheus-operator#5883)

---------

Signed-off-by: Mario Fernandez <mariofer@redhat.com>
Co-authored-by: Simon Pasquier <spasquie@redhat.com>
Signed-off-by: Mario Fernandez <mariofer@redhat.com>
This change is a pre-requisite for prometheus-operator#5898.

Signed-off-by: Simon Pasquier <spasquie@redhat.com>
…or-crd-checks

chore: refactor CRD and RBAC checks
…tor#5913)


Signed-off-by: Mario Fernandez <mariofer@redhat.com>
…r#5912)


Signed-off-by: Mario Fernandez <mariofer@redhat.com>
Bumps [gotest.tools/v3](https://github.com/gotestyourself/gotest.tools) from 3.5.0 to 3.5.1.
- [Release notes](https://github.com/gotestyourself/gotest.tools/releases)
- [Commits](gotestyourself/gotest.tools@v3.5.0...v3.5.1)

---
updated-dependencies:
- dependency-name: gotest.tools/v3
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps [sigs.k8s.io/controller-runtime](https://github.com/kubernetes-sigs/controller-runtime) from 0.16.1 to 0.16.2.
- [Release notes](https://github.com/kubernetes-sigs/controller-runtime/releases)
- [Changelog](https://github.com/kubernetes-sigs/controller-runtime/blob/main/RELEASE.md)
- [Commits](kubernetes-sigs/controller-runtime@v0.16.1...v0.16.2)

---
updated-dependencies:
- dependency-name: sigs.k8s.io/controller-runtime
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps [github.com/brancz/kube-rbac-proxy](https://github.com/brancz/kube-rbac-proxy) from 0.14.2 to 0.14.3.
- [Release notes](https://github.com/brancz/kube-rbac-proxy/releases)
- [Changelog](https://github.com/brancz/kube-rbac-proxy/blob/master/CHANGELOG.md)
- [Commits](brancz/kube-rbac-proxy@v0.14.2...v0.14.3)

---
updated-dependencies:
- dependency-name: github.com/brancz/kube-rbac-proxy
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
…dependabot/go_modules/gotest.tools/v3-3.5.1

build(deps): bump gotest.tools/v3 from 3.5.0 to 3.5.1
…dependabot/go_modules/sigs.k8s.io/controller-runtime-0.16.2

build(deps): bump sigs.k8s.io/controller-runtime from 0.16.1 to 0.16.2
…dependabot/go_modules/github.com/brancz/kube-rbac-proxy-0.14.3

build(deps): bump github.com/brancz/kube-rbac-proxy from 0.14.2 to 0.14.3
Bumps [github.com/evanphx/json-patch/v5](https://github.com/evanphx/json-patch) from 5.6.0 to 5.7.0.
- [Release notes](https://github.com/evanphx/json-patch/releases)
- [Commits](evanphx/json-patch@v5.6.0...v5.7.0)

---
updated-dependencies:
- dependency-name: github.com/evanphx/json-patch/v5
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
…dependabot/go_modules/github.com/evanphx/json-patch/v5-5.7.0

build(deps): bump github.com/evanphx/json-patch/v5 from 5.6.0 to 5.7.0
Bumps [github.com/thanos-io/thanos](https://github.com/thanos-io/thanos) from 0.32.2 to 0.32.3.
- [Release notes](https://github.com/thanos-io/thanos/releases)
- [Changelog](https://github.com/thanos-io/thanos/blob/main/CHANGELOG.md)
- [Commits](thanos-io/thanos@v0.32.2...v0.32.3)

---
updated-dependencies:
- dependency-name: github.com/thanos-io/thanos
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
…dependabot/go_modules/github.com/thanos-io/thanos-0.32.3

build(deps): bump github.com/thanos-io/thanos from 0.32.2 to 0.32.3
Signed-off-by: Arthur Silva Sens <arthur.sens@coralogix.com>
When the operator was configured to select only a limited number of
namespaces, it would not watch for namespace changes. It means that the
operator may not reconcile when a namespace label is added/removed
(affecting which objects should be selected or not).

This change enables the operator to use a privileged namespace
lister/watcher whenever the service account has the needed permissions.

**IMPORTANT:** it also requires Kubernetes >= 1.22 to be effective but
the operator will degrade to the suboptimal implementation without watch
if this condition isn't met.

Closes prometheus-operator#3847

Signed-off-by: Simon Pasquier <spasquie@redhat.com>
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@openshift-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Nov 6, 2023
Copy link

openshift-ci bot commented Nov 6, 2023

Hi @openshift-monitoring-bot[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@slashpai
Copy link
Member

slashpai commented Nov 6, 2023

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Nov 6, 2023
@slashpai
Copy link
Member

slashpai commented Nov 7, 2023

/retest

Copy link

openshift-ci bot commented Nov 7, 2023

@openshift-monitoring-bot[bot]: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@slashpai
Copy link
Member

slashpai commented Nov 7, 2023

/lgtm
cc @simonpasquier

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 7, 2023
Copy link

openshift-ci bot commented Nov 7, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-monitoring-bot[bot], slashpai

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 7, 2023
@simonpasquier
Copy link

/retitle OCPBUGS-18707: [bot] Bump openshift/prometheus-operator to v0.69.0

@openshift-ci openshift-ci bot changed the title [bot] Bump openshift/prometheus-operator to v0.69.0 OCPBUGS-18707: [bot] Bump openshift/prometheus-operator to v0.69.0 Nov 7, 2023
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Nov 7, 2023
@openshift-ci-robot
Copy link

@openshift-monitoring-bot[bot]: This pull request references Jira Issue OCPBUGS-18707, which is invalid:

  • expected the bug to target the "4.15.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Description

This is an automated version bump from CI.
If you wish to perform this manually, execute the following commands from openshift/prometheus-operator repo,

git fetch https://github.com/prometheus-operator/prometheus-operator --tags
if ! git merge refs/tags/v0.69.0 --no-edit; then
 git checkout --theirs CHANGELOG.md Documentation VERSION bundle.yaml example go.mod go.sum pkg
 git checkout --ours 
 git add CHANGELOG.md Documentation VERSION bundle.yaml example go.mod go.sum pkg 
 git merge --continue
fi
go mod tidy
go mod vendor

if [ -f scripts/rh-manifest.sh ]; then
 bash scripts/rh-manifest.sh
 git add rh-manifest.txt
 git diff --cached --exit-code || git commit -s -m "[bot] update rh-manifest.txt"
fi

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Nov 7, 2023
@simonpasquier
Copy link

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Nov 7, 2023
@openshift-ci-robot
Copy link

@simonpasquier: This pull request references Jira Issue OCPBUGS-18707, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.15.0) matches configured target version for branch (4.15.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @juzhao

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci openshift-ci bot requested a review from juzhao November 7, 2023 08:54
@openshift-merge-bot openshift-merge-bot bot merged commit 3eeb332 into openshift:master Nov 7, 2023
7 checks passed
@openshift-ci-robot
Copy link

@openshift-monitoring-bot[bot]: Jira Issue OCPBUGS-18707: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-18707 has been moved to the MODIFIED state.

In response to this:

Description

This is an automated version bump from CI.
If you wish to perform this manually, execute the following commands from openshift/prometheus-operator repo,

git fetch https://github.com/prometheus-operator/prometheus-operator --tags
if ! git merge refs/tags/v0.69.0 --no-edit; then
 git checkout --theirs CHANGELOG.md Documentation VERSION bundle.yaml example go.mod go.sum pkg
 git checkout --ours 
 git add CHANGELOG.md Documentation VERSION bundle.yaml example go.mod go.sum pkg 
 git merge --continue
fi
go mod tidy
go mod vendor

if [ -f scripts/rh-manifest.sh ]; then
 bash scripts/rh-manifest.sh
 git add rh-manifest.txt
 git diff --cached --exit-code || git commit -s -m "[bot] update rh-manifest.txt"
fi

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-merge-robot
Copy link

Fix included in accepted release 4.15.0-0.nightly-2023-11-07-162411

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet