Skip to content

NO-ISSUE: [bot] Bump openshift/prometheus-operator to v0.93.1 - #391

Merged
openshift-merge-bot[bot] merged 7 commits into
openshift:mainfrom
rhobs:automated-updates-main
Aug 10, 2026
Merged

NO-ISSUE: [bot] Bump openshift/prometheus-operator to v0.93.1#391
openshift-merge-bot[bot] merged 7 commits into
openshift:mainfrom
rhobs:automated-updates-main

Conversation

@openshift-monitoring-bot

Copy link
Copy Markdown

Description

This is an automated version bump from CI.
The logs for this run can be found in the syncbot repo actions.

archy-rock3t-cloud and others added 7 commits August 5, 2026 12:29
Signed-off-by: Artem Muterko <artem@sopho.tech>
…belet-endpoints-ip-family

fix: restrict kubelet Endpoints to the service's primary IP family
The --grpc-server-tls-ciphers and --grpc-server-tls-curves flags in
Thanos are defined with kingpin's StringsVar, which accumulates values
from repeated flag invocations. It does not split a single
comma-separated value.

Previously the operator joined all cipher suites and curves into a
single comma-separated value (e.g.
--grpc-server-tls-ciphers=cipher1,cipher2), causing Thanos to treat the
entire string as one cipher name and fail with 'invalid cipher suite'.

Emit one flag per value instead, producing repeated flags that kingpin
can parse correctly (e.g. --grpc-server-tls-ciphers=cipher1
--grpc-server-tls-ciphers=cipher2).

Assisted-by: claude-opus-4-6
Signed-off-by: Jan Fajerski <jfajersk@redhat.com>
…pc-tls-repeated-flags

fix: emit repeated flags for Thanos gRPC TLS ciphers and curves
Signed-off-by: Simon Pasquier <spasquie@redhat.com>
v0.93.1

# -----BEGIN PGP SIGNATURE-----
#
# iQIzBAABCgAdFiEE/jCAc0MNZY5toBt1AZCmbAoQ/E8FAmp51voACgkQAZCmbAoQ
# /E+1VBAA2YTezwJuPPqJ+7KaU9Bhh5JtNPJXoRK4u8yzrjYpfL5hIoOTSfGPMhr9
# pQOOp12DsHeQe5B5vwoBW+oeNp6ZBrxMnrhVC82B10R/d3ZUdO7Q3nIIei5KKAv2
# ClzPnOTWMETwCMRJTvobfjEEoiEiZWZ51l21NjhNJfEd4+lxmZ3+iQ1jYIkjDTi9
# iFtcWk+VB5bKSpVfTFF+wWowq9uxaUjzZpaBiwJhqHfHUN/MsPcUTS/ULAHIVdp3
# VzPN4kRneSLvbrdGsuBwARITd2Vh8daKBU2OuQgx8n+9cNLJpSaCo90CuQOmRM8C
# RQEnD9XVsLy/pg0+7vBz+xX/92JY6gwtqkEYjXmv6tI4Z2HAoQp80hBiwmZZQvrg
# /ENv4jtEFn4ACZeHasTj/4i0WpCD1tsW2xVVKlkVUmL1JqQgaW/j5t63rM2LULUM
# DoGMOp1FklDPxIfPaFldZZxZvUt0EnEWhzYxuhtGuWcJitDNKwFJP0OO61YOQapK
# RyNpRf2+B2Theuw+KIF4lmF9EA4K8M2XQhDtjg3TxAqDxgE2kSuzvRicXN4Knr+d
# lYxCJz4N3NbGXQ4/hWrTjmkRiwfTrxgOtb2iItrUjTcRhaIH//XNSYhYLK20T3QE
# 4KQS/bjsMPNMfGDovfjxIz4XaOOuGz9lYUZCnVq2sEb6UFLObss=
# =SgkN
# -----END PGP SIGNATURE-----
# gpg: directory '/home/runner/.gnupg' created
# gpg: keybox '/home/runner/.gnupg/pubring.kbx' created
# gpg: Signature made Mon Aug 10 13:49:46 2026 UTC
# gpg:                using RSA key FE308073430D658E6DA01B750190A66C0A10FC4F
# gpg: Can't check signature: No public key
@openshift-merge-bot

Copy link
Copy Markdown

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@simonpasquier

Copy link
Copy Markdown

/approve
/lgtm
/verified by CI
/retitle NO-ISSUE: [bot] Bump openshift/prometheus-operator to v0.93.1

@openshift-ci openshift-ci Bot changed the title [bot] Bump openshift/prometheus-operator to v0.93.1 NO-ISSUE: [bot] Bump openshift/prometheus-operator to v0.93.1 Aug 10, 2026
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Aug 10, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@simonpasquier: This PR has been marked as verified by CI.

Details

In response to this:

/approve
/lgtm
/verified by CI
/retitle NO-ISSUE: [bot] Bump openshift/prometheus-operator to v0.93.1

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 10, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@openshift-monitoring-bot[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

Description

This is an automated version bump from CI.
The logs for this run can be found in the syncbot repo actions.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 10, 2026
@openshift-merge-bot

Copy link
Copy Markdown

Scheduling required tests:
/test e2e-agnostic-cmo
/test e2e-aws
/test e2e-aws-upgrade

@openshift-ci

openshift-ci Bot commented Aug 10, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

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

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

The pull request process is described here

Details 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 Aug 10, 2026
@openshift-merge-bot

Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 49894fa and 2 for PR HEAD 6e3371b in total

@openshift-ci

openshift-ci Bot commented Aug 10, 2026

Copy link
Copy Markdown

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

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot
openshift-merge-bot Bot merged commit 67895c7 into openshift:main Aug 10, 2026
11 checks passed
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/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants