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

Bug 1813894: Stop using service ca from service account token #130

Merged
merged 1 commit into from May 23, 2020

Conversation

marun
Copy link
Contributor

@marun marun commented May 13, 2020

@openshift-ci-robot openshift-ci-robot added the bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. label May 13, 2020
@openshift-ci-robot
Copy link
Contributor

@marun: This pull request references Bugzilla bug 1813894, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.5.0) matches configured target release for branch (4.5.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1813894: Stop using service ca from service account token

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 the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label May 13, 2020
@mfojtik
Copy link
Member

mfojtik commented May 13, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label May 13, 2020
@Miciah
Copy link
Contributor

Miciah commented May 14, 2020

/lgtm
/hold
Before we merge this PR, we need to fix the operator to configure the service CA bundle from the proper location.

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 14, 2020
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 14, 2020
@marun
Copy link
Contributor Author

marun commented May 14, 2020

@miabbott @Miciah Should the default be cleared as proposed and the flag/env var be set by the operator to the configmap-sourced file, or should the default be the configmap-sourced file?

I'll leave you to coordinate landing updates to the router and operator, but I'll leave this PR up as a placeholder until your PRs are proposed.

@Miciah
Copy link
Contributor

Miciah commented May 14, 2020

@marun, I think you mean to @ me (Miciah, not Micah). We should clear the default so that the router can be started without creating the configmap or specifying the environment variable or command-line option. Some Origin tests do this (deploy a router pod with some special configuration, without using the operator), and I could imagine developers or community users doing the same.

@Miciah
Copy link
Contributor

Miciah commented May 22, 2020

I manually tested a cluster built with #130 and openshift/origin#24956 and did not have any test failures.
/lgtm

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: marun, mfojtik, Miciah

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

@Miciah
Copy link
Contributor

Miciah commented May 22, 2020

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 22, 2020
@Miciah
Copy link
Contributor

Miciah commented May 22, 2020

And, for the record, openshift/cluster-ingress-operator#399 (merged) addresses #130 (comment).

@Miciah
Copy link
Contributor

Miciah commented May 22, 2020

ci-operator failure:

could not initialize namespace: could not create role binding for: rolebindings.rbac.authorization.k8s.io is forbidden: User "system:serviceaccount:ci:ci-operator" cannot create resource "rolebindings" in API group "rbac.authorization.k8s.io" in the namespace "ci-op-zfqqgl57"

/test unit

@marun
Copy link
Contributor Author

marun commented May 22, 2020

/retest

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 65fd11d into openshift:master May 23, 2020
@openshift-ci-robot
Copy link
Contributor

@marun: Some pull requests linked via external trackers have merged: . The following pull requests linked via external trackers have not merged:

In response to this:

Bug 1813894: Stop using service ca from service account token

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/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants