search

kubernetes / kops

Kubernetes Operations (kOps) - Production Grade k8s Installation, Upgrades and Management
https://kops.sigs.k8s.io/
Apache License 2.0
15.94k stars 4.65k forks source link

Seemingly arbitrary zone and subnet correlation for openstack #11685

Closed wesselvdv closed 3 years ago

wesselvdv commented 3 years ago

I am trying to use a terraform provider for kOps with Openstack, and I am running into an issue with that’s caused by the code below:

https://github.com/kubernetes/kops/blob/466877c8d5105e8cf11dfaa8a4868924d316ec9d/upup/pkg/fi/cloudup/openstack/cloud.go#L555-L582

from my understanding there’s no such thing as a subnet in a specific availability zone for Openstack. This makes it damn near impossible to provide a network/subnet combination to said terraform provider I am using because I don’t know what kind of subnet/zone combination kOps is expecting. (the provider requires me to setup the network and subsequent subnets manually, and pass ‘m in)

I made an issue in said repo (here) , but I found out it’s due to the line of code I referenced to above.

I think it’s not doing anything useful, but I don’t know enough to say that removing it would have no ill effects.

johngmyers commented 3 years ago

/area provider/openstack

k8s-triage-robot commented 3 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 3 years ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 3 years ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

k8s-ci-robot commented 3 years ago

@k8s-triage-robot: Closing this issue.

In response to [this](https://github.com/kubernetes/kops/issues/11685#issuecomment-962429064): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues and PRs according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue or PR with `/reopen` >- Mark this issue or PR as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.