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
OSASINFRA-3243: add ephemeral storage support #88
Conversation
/test e2e-openstack |
/retest-required |
/test e2e-openstack |
2cfff0b
to
99f6a97
Compare
@EmilienM: This pull request references OSASINFRA-3243 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.15.0" version, but no target version was set. 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. |
@EmilienM: This pull request references OSASINFRA-3243 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.15.0" version, but no target version was set. 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. |
@mandre should we get a new tag in downstream CAPO? I pulled it from the main branch, I don't think we want that. |
@EmilienM: This pull request references OSASINFRA-3243 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.15.0" version, but no target version was set. 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. |
/lgtm |
/hold |
/lgtm cancel holds are not being enforced |
/lgtm |
@@ -120,5 +120,5 @@ require ( | |||
replace ( | |||
github.com/elazarl/goproxy => github.com/elazarl/goproxy v0.0.0-20230731152917-f99041a5c027 | |||
sigs.k8s.io/cluster-api => sigs.k8s.io/cluster-api v1.5.2 | |||
sigs.k8s.io/cluster-api-provider-openstack => github.com/openshift/cluster-api-provider-openstack v0.8.0 | |||
sigs.k8s.io/cluster-api-provider-openstack => github.com/openshift/cluster-api-provider-openstack v0.8.0-beta.0.0.20231030165925-6fdfd82f7ad4 |
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.
@mandre should we get a new tag in downstream CAPO? I pulled it from the main branch, I don't think we want that.
I theory we want the next OCP branch to be based on a stable version of CAPO but we can't really do that here, unless upstream releases a new stable version containing the additional storage changes before our feature freeze. Our choices are:
- base OCP 4.15 on an unreleased version of CAPO (future v0.9.0, currently
main
) and benefit from new features like additional storage, at the expense of potentially higher maintaining cost. - base OCP 4.15 on the last stable CAPO version and forget about new features.
We'll have to go with the dev-branch in 4.15 because we need the new features. We can switch it to the stable v0.9.0
once it is released.
The fact that it is now showing v0.8.0-beta.0.0.20231030165925-6fdfd82f7ad4
here is because the last known tag commit in main was v0.8.0-beta
. Strangely, the v0.8.0
tag (commit 686923cc1a8f45490b1c96b4a8bbb2e556be3627) doesn't belong in release-0.8
branch, so pulling release-0.8
would have had the same result:
~/go/src/sigs.k8s.io/cluster-api-provider-openstack remotes/k8s/release-0.8
❯ git describe
v0.8.0-beta.0-11-gaf788a6b2
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.
Thanks.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: EmilienM, mandre 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 |
/hold cancel |
@EmilienM: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
Allow to use the new
AdditionalBlockDevices
in OpenShift machines.