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
Bug 2097346: Updates how gather_monitoring obtains SA token #313
Bug 2097346: Updates how gather_monitoring obtains SA token #313
Conversation
problem: Since k8s 1.24 tokens for SA are not automatically generated [1] hence, it's not possible to get a SA token with the command "oc sa get-token default", this breaks the gather_monitoring script as we need the token to make http requests to prometheus solution: use instead the new command "oc create token default" [1] kubernetes/kubernetes#108309
0e2023a
to
b3de331
Compare
@JoaoBraveCoding: This pull request references Bugzilla bug 2097346, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: 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 kubernetes/test-infra repository. |
@JoaoBraveCoding: This pull request references Bugzilla bug 2097346, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: 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 kubernetes/test-infra repository. |
/retest |
/lgtm |
@JoaoBraveCoding: 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. |
e2e looks good :) : $ curl -s https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift_must-gather/313/pull-ci-openshift-must-gather-master-e2e-aws/1537071260243070976/artifacts/e2e-aws/gather-must-gather/artifacts/must-gather.tar | tar tvz | grep /monitoring/
drwxr-xr-x 1009340000/root 0 2022-06-15 08:32 registry-build03-ci-openshift-org-ci-op-qrsrg6hw-stable-sha256-234d5e5abc2088e0e254aec0a5623064003ce9de5efe3d30fa95a9acd017f34b/monitoring/alertmanager
-rw------- 1009340000/root 1814 2022-06-15 08:32 registry-build03-ci-openshift-org-ci-op-qrsrg6hw-stable-sha256-234d5e5abc2088e0e254aec0a5623064003ce9de5efe3d30fa95a9acd017f34b/monitoring/alertmanager/status.json
-rw------- 1009340000/root 0 2022-06-15 08:32 registry-build03-ci-openshift-org-ci-op-qrsrg6hw-stable-sha256-234d5e5abc2088e0e254aec0a5623064003ce9de5efe3d30fa95a9acd017f34b/monitoring/alertmanager/status.stderr
drwxr-xr-x 1009340000/root 0 2022-06-15 08:32 registry-build03-ci-openshift-org-ci-op-qrsrg6hw-stable-sha256-234d5e5abc2088e0e254aec0a5623064003ce9de5efe3d30fa95a9acd017f34b/monitoring/prometheus
-rw------- 1009340000/root 3866 2022-06-15 08:32 registry-build03-ci-openshift-org-ci-op-qrsrg6hw-stable-sha256-234d5e5abc2088e0e254aec0a5623064003ce9de5efe3d30fa95a9acd017f34b/monitoring/prometheus/alertmanagers.json
-rw------- 1009340000/root 0 2022-06-15 08:32 registry-build03-ci-openshift-org-ci-op-qrsrg6hw-stable-sha256-234d5e5abc2088e0e254aec0a5623064003ce9de5efe3d30fa95a9acd017f34b/monitoring/prometheus/alertmanagers.stderr
drwxr-xr-x 1009340000/root 0 2022-06-15 08:32 registry-build03-ci-openshift-org-ci-op-qrsrg6hw-stable-sha256-234d5e5abc2088e0e254aec0a5623064003ce9de5efe3d30fa95a9acd017f34b/monitoring/prometheus/prometheus-k8s-0
... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving this PR. Please make one alteration, though. Change typo in title so it's 'gather_monitoring' instead of 'gether_monitoring', for clarity.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JoaoBraveCoding, RickJWagner, simonpasquier 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 |
@JoaoBraveCoding: All pull requests linked via external trackers have merged: Bugzilla bug 2097346 has been moved to the MODIFIED state. 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 kubernetes/test-infra repository. |
/retitle Bug 2097346: Updates how gather_monitoring obtains SA token |
Issue: https://bugzilla.redhat.com/show_bug.cgi?id=2097346
problem: since k8s 1.24 tokens for SA are not automatically generated [1]
hence, it's not possible to get a SA token with the command
"oc sa get-token default", this breaks the gather_monitoring script as
we need the token to make http requests to prometheus
solution: use instead the new command "oc create token default"
[1] kubernetes/kubernetes#108309