OCPNODE-2100: jsonnet: update crio port to TLS port 9637 #2257
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@rphillips: This pull request references OCPNODE-2022 which is a valid jira issue. In response to this:
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
bot
added
the
do-not-merge/work-in-progress
|
/payload help |
|
/payload-aggregate periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade |
|
/payload-aggregate periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade 10 |
|
@rphillips: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/5c020710-c5c5-11ee-922b-dca000ede010-0 |
|
/payload-aggregate-with-prs periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade 10 openshift/machine-config-operator#4175 |
|
@rphillips: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/820f5280-c6d5-11ee-97cb-3e05c7124d92-0 |
|
/payload-aggregate-with-prs periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade 10 openshift/machine-config-operator#4175 |
1 similar comment
|
/payload-aggregate-with-prs periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade 10 openshift/machine-config-operator#4175 |
|
/payload-aggregate-with-prs periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade 10 openshift/machine-config-operator#4175 |
|
@rphillips: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/896bb770-c93d-11ee-8788-320a5f153a65-0 |
|
/payload-aggregate-with-prs periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade 10 openshift/machine-config-operator#4175 |
|
@rphillips: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0d734920-c9ca-11ee-824a-026157b75804-0 |
|
/payload-aggregate-with-prs periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade 10 openshift/machine-config-operator#4175 |
|
@rphillips: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/56f50e00-ca7c-11ee-974b-7cd8f62e7155-0 |
|
/payload-aggregate-with-prs periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade 10 openshift/machine-config-operator#4175 |
|
@rphillips: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/71d442f0-d03e-11ee-95a3-a9525782e9b1-0 |
|
Another set of test runs: /payload-aggregate-with-prs periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade 10 openshift/machine-config-operator#4175 |
|
@rphillips: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/ee6ad150-d046-11ee-8944-22e78ea98d14-0 |
|
Trying out the payload test on a new PR /payload-aggregate-with-prs periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade 10 openshift/machine-config-operator#4209 |
|
/payload-aggregate-with-prs periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade 10 openshift/machine-config-operator#4209 |
|
@rphillips: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/947aaa00-d0bc-11ee-8a88-f4397baa2cbc-0 |
|
/payload-aggregate-with-prs periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade 10 openshift/machine-config-operator#4175 |
|
@rphillips: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/2fe383e0-d0bd-11ee-810a-f5690c54df5d-0 |
rphillips
force-pushed
the
add_crio_secure_port_3
branch
from
7a56053
to
1c0aa30
Compare
rphillips
changed the title
|
@rphillips: This pull request references OCPNODE-2100 which is a valid jira issue. In response to this: 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
added
the
jira/valid-reference
|
/hold for openshift/machine-config-operator#4175 |
openshift-ci
bot
added
the
do-not-merge/hold
|
@rphillips: The following tests failed, say
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. |
|
/payload-aggregate-with-prs periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade 10 |
|
@rphillips: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info. |
|
/payload-aggregate periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade 10 |
|
@rphillips: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/b0a66fe0-e005-11ee-9e0d-e60f3f7a9b45-0 |
|
/payload-aggregate periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade 10 |
|
@rphillips: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0001cb10-e07f-11ee-9aca-a93d433e5341-0 |
|
This should be testing with 4.15.3 now (with crio static pods) /payload-aggregate periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade 10 |
|
@rphillips: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0e213a50-e09d-11ee-9437-435f617d856c-0 |
|
Test passed from 4.15 to master... I need to get 2 more PRs into 4.14 so that EUS upgrades work. |
|
4.14 merged. This PR is now ready. /hold cancel |
openshift-ci
bot
removed
the
do-not-merge/hold
|
@rphillips: This pull request references OCPNODE-2100 which is a valid jira issue. In response to this:
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. |
|
/retest-required |
|
/lgtm thanks! |
openshift-ci
bot
added
the
approved
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danielmellado, harche, rphillips 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 |
openshift-merge-bot
bot
merged commit e761b9e
into
openshift:master
|
[ART PR BUILD NOTIFIER] This PR has been included in build cluster-monitoring-operator-container-v4.16.0-202403230015.p0.ge761b9e.assembly.stream.el9 for distgit cluster-monitoring-operator. |
This PR switches monitoring over to use the secure 9637 metrics port for crio (backed by kube-rbac-proxy). It also changes the authentication to use the client certificate auth, since static pods cannot mount secrets.