Skip to content

Conversation

@sdodson
Copy link
Member

@sdodson sdodson commented Jan 7, 2019

When performing BYO RHEL installations we only call create ignition-configs and we'd like to have the generated kubeconfig created at that point as well. I had initially proposed moving it but it was suggested to add it rather than move it.

When performing BYO RHEL installations we only call `create
ignition-configs` and we'd like to have the generated kubeconfig created
at that point as well. I had initially proposed moving it but it was
suggested to add it rather than move it.
@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jan 7, 2019
@sdodson sdodson requested review from abhinavdahiya, russellb and wking and removed request for russellb and wking January 7, 2019 15:36
Copy link
Member

Choose a reason for hiding this comment

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

This seems fine to me. We'll probably stuff manifest.json in here too once we have it pulled out into its own asset structure. But I'm fine handling that in follow-up work.

@wking
Copy link
Member

wking commented Jan 10, 2019

/lgtm

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sdodson, wking

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 10, 2019
@sdodson
Copy link
Member Author

sdodson commented Jan 11, 2019

/retest

No retest bot on this repo?

@wking
Copy link
Member

wking commented Jan 11, 2019

No retest bot on this repo?

It's attached to this repo. I suspect the recent, enigmatic "We are investigating reports of degraded performance" GitHub issue delaying webhook delivery. But just in case the previous event was lost:

/retest

@openshift-bot
Copy link
Contributor

/retest

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

5 similar comments
@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

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/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