Closed chrischdi closed 3 years ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
/remove-lifecycle stale
@ramineni would it make sense to add simple kustomization.yaml
files to each of the manifest directories?
e.g. for the cinder csi plugin:
resources:
- cinder-csi-controllerplugin-rbac.yaml
- cinder-csi-controllerplugin.yaml
- cinder-csi-nodeplugin-rbac.yaml
- cinder-csi-nodeplugin.yaml
- csi-cinder-driver.yaml
- csi-secret-cinderplugin.yaml
If so I would be happy to open a PR for that :-)
@chrischdi That would be great. Please go ahead
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten
/remove-lifecycle rotten
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
/remove-lifecycle stale
For anyone winding up here before a fix lands or who want to use an older version you can use something like:
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- https://github.com/kubernetes/cloud-provider-openstack/raw/release-1.17/manifests/cinder-csi-plugin/cinder-csi-controllerplugin-rbac.yaml
- https://github.com/kubernetes/cloud-provider-openstack/raw/release-1.17/manifests/cinder-csi-plugin/cinder-csi-controllerplugin.yaml
- https://github.com/kubernetes/cloud-provider-openstack/raw/release-1.17/manifests/cinder-csi-plugin/cinder-csi-nodeplugin-rbac.yaml
- https://github.com/kubernetes/cloud-provider-openstack/raw/release-1.17/manifests/cinder-csi-plugin/cinder-csi-nodeplugin.yaml
- https://github.com/kubernetes/cloud-provider-openstack/raw/release-1.17/manifests/cinder-csi-plugin/csi-cinder-driver.yaml
- https://github.com/kubernetes/cloud-provider-openstack/raw/release-1.17/manifests/cinder-csi-plugin/csi-secret-cinderplugin.yaml
just replace the release-1.17
with the appropriate tag.
@baylisscg Thanks!
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to sig-contributor-experience at kubernetes/community. /close
@fejta-bot: Closing this issue.
Is this a BUG REPORT or FEATURE REQUEST?:
The binaries affected:
What happened: I wanted to use the yaml files in:
and refer them directly in a local
kustomization.yaml
file. This does not work because thecloud-provider-openstack
repository does not contain any kustomization file.What you expected to happen: There is a kustomization file which I could refer to in my
kustomization.yaml
How to reproduce it:
Anything else we need to know?:
Would it be reasonable to add kustomization.yaml files? If yes I would be happy to contribute :-)
Environment: