-
Notifications
You must be signed in to change notification settings - Fork 206
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
Include CRDs for openshift.io #185
Include CRDs for openshift.io #185
Conversation
Although we aim to consume directly from upstream repo, we are temporary mirroring upstream API under openshift.io https://github.com/openshift/cluster-api. This PR makes both available for a backward compatible migration
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bison 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 |
/test e2e-aws |
We are transitioning the cluster API types from k8s.io over a machine.openshift.io group. https://github.com/openshift/cluster-api/tree/91fca585a85b163ddfd119fd09c128c9feadddca Although this give us a necessary level of autonomy today, we aim to consolidate back with upstream once there's a release of the API stable enough For reference: Backward compatible changes on machine api operator [openshift/machine-api-operator#185](openshift/machine-api-operator#185) [openshift/machine-api-operator#188](openshift/machine-api-operator#188) [openshift/machine-api-operator#191](openshift/machine-api-operator#191) Libvirt actuator support for new group openshift/cluster-api-provider-libvirt#111
We are transitioning the cluster API types from k8s.io over a machine.openshift.io group. https://github.com/openshift/cluster-api/tree/91fca585a85b163ddfd119fd09c128c9feadddca Although this give us a necessary level of autonomy today, we aim to consolidate back with upstream once there's a release of the API stable enough For reference: Backward compatible changes on machine api operator [openshift/machine-api-operator#185](openshift/machine-api-operator#185) [openshift/machine-api-operator#188](openshift/machine-api-operator#188) [openshift/machine-api-operator#191](openshift/machine-api-operator#191) Libvirt actuator support for new group openshift/cluster-api-provider-libvirt#111
We are transitioning the cluster API types from k8s.io over a machine.openshift.io group. https://github.com/openshift/cluster-api/tree/91fca585a85b163ddfd119fd09c128c9feadddca Although this give us a necessary level of autonomy today, we aim to consolidate back with upstream once there's a release of the API stable enough For reference: Backward compatible changes on machine api operator [openshift/machine-api-operator#185](openshift/machine-api-operator#185) [openshift/machine-api-operator#188](openshift/machine-api-operator#188) [openshift/machine-api-operator#191](openshift/machine-api-operator#191) Libvirt actuator support for new group openshift/cluster-api-provider-libvirt#111
Although we aim to consume directly from upstream repo, we are temporary mirroring upstream API under openshift.io https://github.com/openshift/cluster-api. This PR makes both available for a backward compatible migration