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-3814: Follow-up #2293 #2315

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

Conversation

slashpai
Copy link
Member

Follow-up from #2293

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

@openshift-bot openshift-bot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 11, 2024
@openshift-bot
Copy link
Contributor

openshift-bot commented Apr 11, 2024

@slashpai: This pull request references MON-3814 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:

Follow-up from #2293

  • 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.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 11, 2024
Copy link
Contributor

openshift-ci bot commented Apr 11, 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 11, 2024
@slashpai slashpai changed the title WIP: MON-3814: update request-header flags in metrics-server MON-3814: update request-header flags in metrics-server Apr 18, 2024
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 18, 2024
@slashpai
Copy link
Member Author

/assign @machine424

@@ -2106,6 +2106,8 @@ func (f *Factory) MetricsServerDeployment(apiAuthSecretName string, kubeletCABun
"--requestheader-extra-headers-prefix="+requestheaderExtraHeadersPrefix,
"--requestheader-group-headers="+requestheaderGroupHeaders,
"--requestheader-username-headers="+requestheaderUsernameHeaders,
"--tls-cert-file=/etc/client-ca-bundle/tls.crt",
Copy link
Contributor

Choose a reason for hiding this comment

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

No test was failing when using /etc/tls/private/xxx, do they have the same content? Is testing this difficult?

Copy link
Member Author

Choose a reason for hiding this comment

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

Thinking about it again. I think what we need here is cleanup as we are using it in volume mount
https://github.com/openshift/cluster-monitoring-operator/pull/2293/files#r1557090512

Copy link
Member Author

Choose a reason for hiding this comment

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

'service.beta.openshift.io/serving-cert-secret-name': 'metrics-server-tls',
(metrics-server-tls) is been mounted at /etc/tls/private ( )

In the updated approach as well it uses the same secret https://github.com/openshift/cluster-monitoring-operator/pull/2293/files#diff-0bbbc0b6e7ee4c4efe218030b64c2ef604fda58d92e51e52c206b6c5c0a4a5a3R158

Copy link
Member Author

Choose a reason for hiding this comment

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

Signed-off-by: Jayapriya Pai <janantha@redhat.com>
@slashpai slashpai changed the title MON-3814: update request-header flags in metrics-server MON-3814: Follow-up #2293 Apr 19, 2024
@@ -2162,16 +2162,14 @@ func (f *Factory) MetricsServerSecret(tlsSecret *v1.Secret, apiAuthConfigmap *v1
var (
clientCA = r.value("client-ca-file")
requestheaderClientCA = r.value("requestheader-client-ca-file")
tlsCA = r.value("tls.crt")
tlsKey = r.value("tls.key")
)
Copy link
Member Author

Choose a reason for hiding this comment

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

removing these as it not used and we mount this in assets already

'--tls-cert-file=/etc/tls/private/tls.crt',
'--tls-private-key-file=/etc/tls/private/tls.key',

Follow-up https://github.com/openshift/cluster-monitoring-operator/pull/2293/files#r1557090512

Copy link
Member

@rexagod rexagod Apr 19, 2024

Choose a reason for hiding this comment

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

True, and I believe the tlsSecret can be dropped now.

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 we didin't need that wait. as we already waited for that secret here

scas, err := t.client.WaitForSecretByNsName(
ctx,
types.NamespacedName{
Namespace: s.Namespace,
Name: s.Annotations["service.beta.openshift.io/serving-cert-secret-name"],
},
)
)

@slashpai
Copy link
Member Author

Closing in favour of #2329

@slashpai
Copy link
Member Author

/close

@openshift-ci openshift-ci bot closed this Apr 24, 2024
Copy link
Contributor

openshift-ci bot commented Apr 24, 2024

@slashpai: Closed this PR.

In response to this:

/close

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.

@machine424
Copy link
Contributor

Because we put #2329 on hold for now, we can revive this PR if you want.

@machine424
Copy link
Contributor

I'll
/reopen
this, it'll be nice to have this cleaning in 4.17

@openshift-ci openshift-ci bot reopened this Jun 5, 2024
Copy link
Contributor

openshift-ci bot commented Jun 5, 2024

@machine424: Reopened this PR.

In response to this:

I'll
/reopen
this, it'll be nice to have this cleaning in 4.17

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.

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jun 5, 2024

@slashpai: This pull request references MON-3814 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.17.0" version, but no target version was set.

In response to this:

Follow-up from #2293

  • 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.

@machine424
Copy link
Contributor

I think we can merge this once tlsSecret is dropped as an argument to MetricsServerSecret.

@machine424
Copy link
Contributor

/hold

@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 Jun 5, 2024
Copy link
Contributor

openshift-ci bot commented Jul 1, 2024

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

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

5 participants