Skip to content

Conversation

@ricardomaraschini
Copy link
Contributor

@ricardomaraschini ricardomaraschini commented Jan 15, 2020

Kubernetes client-go requires only one authentication method to be present therefore this patch zeroes the content of BearerTokenFile as basic auth is used during prune.

In a nutshell: or we use token based authentication or basic auth, never both at the same time.

Note: This patch is also necessary to fix Bug 1762837

@openshift-ci-robot
Copy link

@ricardomaraschini: This pull request references Bugzilla bug 1790978, 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.

Details

In response to this:

Bug 1790978: Setting placeholder user only when no token exist.

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.

@openshift-ci-robot openshift-ci-robot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jan 15, 2020
@ricardomaraschini
Copy link
Contributor Author

/assign @soltysh @dmage

Kubernetes client-go requires only one authentication method to be present
therefore this patch zeroes the content of BearerTokenFile as basic auth
is used during prune.

In a nutshell: or we use token based authentication or basic auth, never
both at the same time.
@ricardomaraschini ricardomaraschini changed the title Bug 1790978: Setting placeholder user only when no token exist. Bug 1790978: Zeroing BearerTokenFile for prune. Jan 16, 2020
@openshift-ci-robot
Copy link

@ricardomaraschini: This pull request references Bugzilla bug 1790978, which is valid.

Details

In response to this:

Bug 1790978: Zeroing BearerTokenFile for prune.

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.

1 similar comment
@openshift-ci-robot
Copy link

@ricardomaraschini: This pull request references Bugzilla bug 1790978, which is valid.

Details

In response to this:

Bug 1790978: Zeroing BearerTokenFile for prune.

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.

Copy link
Contributor

@soltysh soltysh left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 16, 2020
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ricardomaraschini, soltysh

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-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 16, 2020
@openshift-merge-robot openshift-merge-robot merged commit e17af88 into openshift:master Jan 16, 2020
@openshift-ci-robot
Copy link

@ricardomaraschini: All pull requests linked via external trackers have merged. Bugzilla bug 1790978 has been moved to the MODIFIED state.

Details

In response to this:

Bug 1790978: Zeroing BearerTokenFile for prune.

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.

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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants