Skip to content

Conversation

@smarterclayton
Copy link
Contributor

No description provided.

@openshift-ci-robot openshift-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Dec 3, 2018
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: smarterclayton

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 Dec 3, 2018
@smarterclayton smarterclayton added the lgtm Indicates that a PR is ready to be merged. label Dec 3, 2018
@openshift-merge-robot openshift-merge-robot merged commit 2da8a51 into openshift:master Dec 3, 2018
@openshift-ci-robot
Copy link
Contributor

@smarterclayton: Updated the following 2 configmaps:

  • job-config configmap using the following files:
    • key openshift-service-ca-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/service-ca-operator/openshift-service-ca-operator-master-presubmits.yaml
    • key openshift-router-master-presubmits.yaml using file ci-operator/jobs/openshift/router/openshift-router-master-presubmits.yaml
    • key openshift-cluster-machine-approver-master-presubmits.yaml using file ci-operator/jobs/openshift/cluster-machine-approver/openshift-cluster-machine-approver-master-presubmits.yaml
    • key openshift-cluster-monitoring-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/cluster-monitoring-operator/openshift-cluster-monitoring-operator-master-presubmits.yaml
    • key openshift-machine-config-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/machine-config-operator/openshift-machine-config-operator-master-presubmits.yaml
    • key openshift-origin-master-presubmits.yaml using file ci-operator/jobs/openshift/origin/openshift-origin-master-presubmits.yaml
    • key openshift-service-serving-cert-signer-master-presubmits.yaml using file ci-operator/jobs/openshift/service-serving-cert-signer/openshift-service-serving-cert-signer-master-presubmits.yaml
    • key operator-framework-operator-lifecycle-manager-master-presubmits.yaml using file ci-operator/jobs/operator-framework/operator-lifecycle-manager/operator-framework-operator-lifecycle-manager-master-presubmits.yaml
    • key openshift-cluster-kube-controller-manager-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/cluster-kube-controller-manager-operator/openshift-cluster-kube-controller-manager-operator-master-presubmits.yaml
    • key openshift-cluster-kube-scheduler-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/cluster-kube-scheduler-operator/openshift-cluster-kube-scheduler-operator-master-presubmits.yaml
    • key openshift-cluster-openshift-apiserver-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/cluster-openshift-apiserver-operator/openshift-cluster-openshift-apiserver-operator-master-presubmits.yaml
    • key openshift-cluster-openshift-controller-manager-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/cluster-openshift-controller-manager-operator/openshift-cluster-openshift-controller-manager-operator-master-presubmits.yaml
    • key openshift-installer-master-presubmits.yaml using file ci-operator/jobs/openshift/installer/openshift-installer-master-presubmits.yaml
    • key openshift-machine-api-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/machine-api-operator/openshift-machine-api-operator-master-presubmits.yaml
    • key openshift-cluster-bootstrap-master-presubmits.yaml using file ci-operator/jobs/openshift/cluster-bootstrap/openshift-cluster-bootstrap-master-presubmits.yaml
    • key openshift-cluster-kube-apiserver-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/cluster-kube-apiserver-operator/openshift-cluster-kube-apiserver-operator-master-presubmits.yaml
    • key openshift-cluster-network-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/cluster-network-operator/openshift-cluster-network-operator-master-presubmits.yaml
    • key openshift-cluster-samples-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/cluster-samples-operator/openshift-cluster-samples-operator-master-presubmits.yaml
    • key openshift-cluster-version-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/cluster-version-operator/openshift-cluster-version-operator-master-presubmits.yaml
    • key openshift-console-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/console-operator/openshift-console-operator-master-presubmits.yaml
    • key openshift-pod-checkpointer-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/pod-checkpointer-operator/openshift-pod-checkpointer-operator-master-presubmits.yaml
    • key operator-framework-operator-marketplace-master-presubmits.yaml using file ci-operator/jobs/operator-framework/operator-marketplace/operator-framework-operator-marketplace-master-presubmits.yaml
    • key openshift-cluster-image-registry-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/cluster-image-registry-operator/openshift-cluster-image-registry-operator-master-presubmits.yaml
  • ci-operator-configs configmap using the following files:
    • key openshift-cluster-openshift-apiserver-operator-master.yaml using file ci-operator/config/openshift/cluster-openshift-apiserver-operator/openshift-cluster-openshift-apiserver-operator-master.yaml
    • key openshift-cluster-openshift-controller-manager-operator-master.yaml using file ci-operator/config/openshift/cluster-openshift-controller-manager-operator/openshift-cluster-openshift-controller-manager-operator-master.yaml
    • key openshift-cluster-samples-operator-master.yaml using file ci-operator/config/openshift/cluster-samples-operator/openshift-cluster-samples-operator-master.yaml
    • key openshift-installer-master.yaml using file ci-operator/config/openshift/installer/openshift-installer-master.yaml
    • key openshift-machine-config-operator-master.yaml using file ci-operator/config/openshift/machine-config-operator/openshift-machine-config-operator-master.yaml
    • key openshift-router-master.yaml using file ci-operator/config/openshift/router/openshift-router-master.yaml
    • key openshift-cluster-bootstrap-master.yaml using file ci-operator/config/openshift/cluster-bootstrap/openshift-cluster-bootstrap-master.yaml
    • key openshift-cluster-kube-scheduler-operator-master.yaml using file ci-operator/config/openshift/cluster-kube-scheduler-operator/openshift-cluster-kube-scheduler-operator-master.yaml
    • key openshift-service-ca-operator-master.yaml using file ci-operator/config/openshift/service-ca-operator/openshift-service-ca-operator-master.yaml
    • key openshift-service-serving-cert-signer-master.yaml using file ci-operator/config/openshift/service-serving-cert-signer/openshift-service-serving-cert-signer-master.yaml
    • key openshift-cluster-monitoring-operator-master.yaml using file ci-operator/config/openshift/cluster-monitoring-operator/openshift-cluster-monitoring-operator-master.yaml
    • key operator-framework-operator-marketplace-master.yaml using file ci-operator/config/operator-framework/operator-marketplace/operator-framework-operator-marketplace-master.yaml
    • key openshift-pod-checkpointer-operator-master.yaml using file ci-operator/config/openshift/pod-checkpointer-operator/openshift-pod-checkpointer-operator-master.yaml
    • key operator-framework-operator-lifecycle-manager-master.yaml using file ci-operator/config/operator-framework/operator-lifecycle-manager/operator-framework-operator-lifecycle-manager-master.yaml
    • key openshift-cluster-kube-apiserver-operator-master.yaml using file ci-operator/config/openshift/cluster-kube-apiserver-operator/openshift-cluster-kube-apiserver-operator-master.yaml
    • key openshift-origin-master.yaml using file ci-operator/config/openshift/origin/openshift-origin-master.yaml
    • key openshift-cluster-machine-approver-master.yaml using file ci-operator/config/openshift/cluster-machine-approver/openshift-cluster-machine-approver-master.yaml
    • key openshift-cluster-network-operator-master.yaml using file ci-operator/config/openshift/cluster-network-operator/openshift-cluster-network-operator-master.yaml
    • key openshift-cluster-version-operator-master.yaml using file ci-operator/config/openshift/cluster-version-operator/openshift-cluster-version-operator-master.yaml
    • key openshift-console-operator-master.yaml using file ci-operator/config/openshift/console-operator/openshift-console-operator-master.yaml
    • key openshift-machine-api-operator-master.yaml using file ci-operator/config/openshift/machine-api-operator/openshift-machine-api-operator-master.yaml
    • key openshift-cluster-image-registry-operator-master.yaml using file ci-operator/config/openshift/cluster-image-registry-operator/openshift-cluster-image-registry-operator-master.yaml
    • key openshift-cluster-kube-controller-manager-operator-master.yaml using file ci-operator/config/openshift/cluster-kube-controller-manager-operator/openshift-cluster-kube-controller-manager-operator-master.yaml
Details

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.

@smarterclayton smarterclayton deleted the router_cleanup branch April 24, 2019 14:01
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. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants