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

MON-3866: create separate metrics client cert for metrics server #2329

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

slashpai
Copy link
Member

  • I added CHANGELOG entry for this change.
  • No user facing changes, so no entry in CHANGELOG was needed.

@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Apr 23, 2024
@openshift-ci-robot
Copy link
Contributor

@slashpai: This pull request references Jira Issue OCPBUGS-32510, which is invalid:

  • expected the bug to target the "4.16.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:

  • I added CHANGELOG entry for this change.
  • No user facing changes, so no entry in CHANGELOG was needed.

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.

@slashpai
Copy link
Member Author

cc @machine424

@slashpai
Copy link
Member Author

/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 Apr 23, 2024
@openshift-ci-robot
Copy link
Contributor

@slashpai: This pull request references Jira Issue OCPBUGS-32510, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.16.0) matches configured target version for branch (4.16.0)
  • bug is in the state ASSIGNED, 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 openshift-eng/jira-lifecycle-plugin repository.

data := make(map[string]string)

for k, v := range tlsSecret.Data {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is followup change as in #2315

Copy link
Contributor

openshift-ci bot commented Apr 23, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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 Apr 23, 2024
slashpai added a commit to slashpai/api that referenced this pull request Apr 23, 2024
slashpai added a commit to slashpai/api that referenced this pull request Apr 23, 2024
@slashpai
Copy link
Member Author

/test e2e-aws-ovn-techpreview

@slashpai
Copy link
Member Author

/payload-job periodic-ci-openshift-hypershift-release-4.16-periodics-e2e-aws-ovn-conformance

Copy link
Contributor

openshift-ci bot commented Apr 23, 2024

@slashpai: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-hypershift-release-4.16-periodics-e2e-aws-ovn-conformance

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/d9e6b810-015c-11ef-8aff-ee7e9eefe979-0

@slashpai
Copy link
Member Author

/payload-job periodic-ci-openshift-hypershift-release-4.16-periodics-e2e-aws-ovn-conformance openshift/api#1865

Copy link
Contributor

openshift-ci bot commented Apr 23, 2024

@slashpai: 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.

@jan--f
Copy link
Contributor

jan--f commented Apr 23, 2024

/payload-job-with-prs periodic-ci-openshift-hypershift-release-4.16-periodics-e2e-aws-ovn-conformance openshift/api#1865

Sorry I missed the different command name.

Copy link
Contributor

openshift-ci bot commented Apr 23, 2024

@jan--f: An error was encountered. No known errors were detected, please see the full error message for details.

Full error message. unable to get additional pr info from string: I: string: I doesn't match expected format: org/repo#number

Please contact an administrator to resolve this issue.

@jan--f
Copy link
Contributor

jan--f commented Apr 23, 2024

/payload-job-with-prs periodic-ci-openshift-hypershift-release-4.16-periodics-e2e-aws-ovn-conformance openshift/api#1865

Copy link
Contributor

openshift-ci bot commented Apr 23, 2024

@jan--f: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-hypershift-release-4.16-periodics-e2e-aws-ovn-conformance

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/d8dbc4d0-0169-11ef-80b3-937f07d81a34-0

Copy link
Contributor

openshift-ci bot commented Apr 24, 2024

@slashpai: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/e5caf660-0214-11ef-8541-c562082f3eaa-0

@slashpai
Copy link
Member Author

@machine424 Please take a look again if latest changes are good

@slashpai slashpai force-pushed the OCPBUGS-32510 branch 3 times, most recently from fb321d1 to 11936a2 Compare April 24, 2024 14:44
// is rotated.
dep.Spec.Template.Annotations["monitoring.openshift.io/metrics-client-cert-hash"] = hashByteMap(metricsClientCert.Data)
// TODO(slashpai): Remove this line release after metrics server is GA
dep.Spec.Template.Annotations["monitoring.openshift.io/metrics-client-certs-hash-"] = ""
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My bad, we're not using library-go's utils for Deployement resources yet. So no need for this. I'll give this a try locally.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested with 4dcd2e4 on the cluster bot, all seem ok.

Got some "dial tcp 172.30.0.1:443: connect: connection refused", but as I explain on the ticket, they're not metrics-server specific.

We just need to check out the payload tests.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just realized that CMO never creates these secrets (the prometheus' one as well), it delegates that to the CSR controller.

Apparently there is an issue there, the metrics-server CSR controller is not able to create the secret.

kubeInformersOperatorNS.Core().V1().Secrets(),
o.client.KubernetesInterface().CoreV1(),
o.client.EventRecorder(),
"OpenShiftMonitoringClientCertRequester",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe chose another name to differentiate it from the other one.

@slashpai slashpai force-pushed the OCPBUGS-32510 branch 2 times, most recently from 4775411 to 74d3a50 Compare April 25, 2024 01:58
@slashpai
Copy link
Member Author

/payload-job-with-prs periodic-ci-openshift-hypershift-release-4.16-periodics-e2e-aws-ovn-conformance openshift/api#1865

Copy link
Contributor

openshift-ci bot commented Apr 25, 2024

@slashpai: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-hypershift-release-4.16-periodics-e2e-aws-ovn-conformance

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/f972a990-02a7-11ef-85c8-8a3d6e2fa727-0

@slashpai slashpai force-pushed the OCPBUGS-32510 branch 2 times, most recently from f430ce4 to d6dc8a2 Compare April 25, 2024 02:28
@slashpai
Copy link
Member Author

/payload-job-with-prs periodic-ci-openshift-hypershift-release-4.16-periodics-e2e-aws-ovn-conformance openshift/api#1865

Copy link
Contributor

openshift-ci bot commented Apr 25, 2024

@slashpai: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-hypershift-release-4.16-periodics-e2e-aws-ovn-conformance

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/aaa566b0-02b4-11ef-86e4-14f7e6cef418-0

@slashpai
Copy link
Member Author

I am working on update for this

Signed-off-by: Jayapriya Pai <janantha@redhat.com>
Copy link
Contributor

openshift-ci bot commented Apr 25, 2024

@slashpai: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-ovn e77a644 link true /test e2e-aws-ovn
ci/prow/e2e-agnostic-operator e77a644 link true /test e2e-agnostic-operator
ci/prow/e2e-aws-ovn-single-node e77a644 link false /test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-techpreview e77a644 link true /test e2e-aws-ovn-techpreview
ci/prow/versions e77a644 link false /test versions
ci/prow/e2e-aws-ovn-upgrade e77a644 link true /test e2e-aws-ovn-upgrade

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.

@machine424
Copy link
Contributor

/payload-job-with-prs periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node openshift/api#1865

let's re-test single-noie, I think I saw it fail

Copy link
Contributor

openshift-ci bot commented Apr 25, 2024

@machine424: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/b85820b0-02ee-11ef-8b3a-9bacb4e24e64-0

@machine424
Copy link
Contributor

machine424 commented Apr 29, 2024

/hold
needs openshift/cluster-policy-controller#148
EDIT: a temp workaround is available here #2334, awaiting for the CPO PR.

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 29, 2024
@slashpai slashpai changed the title OCPBUGS-32510: create separate metrics client cert for metrics server MON-3866: create separate metrics client cert for metrics server May 17, 2024
@openshift-ci-robot openshift-ci-robot removed jira/severity-critical Referenced Jira bug's severity is critical 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. labels May 17, 2024
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 17, 2024

@slashpai: This pull request references MON-3866 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set.

In response to this:

  • I added CHANGELOG entry for this change.
  • No user facing changes, so no entry in CHANGELOG was needed.

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.

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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants