API types and basic controller/actuator scaffolding#2
API types and basic controller/actuator scaffolding#2detiber wants to merge 1 commit intoopenshift:masterfrom
Conversation
|
/cc @displague |
|
@detiber: GitHub didn't allow me to request PR reviews from the following users: displague. Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs. DetailsIn 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. |
|
The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the openshift org. You can then trigger verification by writing
|
openshift-ci-robot
added
the
do-not-merge/invalid-owners-file
There was a problem hiding this comment.
I'm mainly interested in the starting point that this PR provides for the Equinix Metal provider types that will be used by openshift/installer#3914.
This is a sufficient starting point upon which we can build.
| @@ -0,0 +1,9 @@ | |||
| FROM registry.svc.ci.openshift.org/ocp/builder:rhel-8-golang-openshift-4.6 AS builder | |||
| WORKDIR /go/src/github.com/openshift/cluster-api-provider-packet | |||
There was a problem hiding this comment.
Who can help us rename this project to cluster-api-provider-equinix-metal? (or unhyphenated equinixmetal, I don't know if there is a preference for technical or historical reasons)
|
Closing this in favor of #1 |
3 participants
Adds the initial basic API types and minimal scaffolding for the controller/actuators.