cluster-api-provider-openstack icon indicating copy to clipboard operation
cluster-api-provider-openstack copied to clipboard

Results 220 cluster-api-provider-openstack issues
Sort by recently updated
recently updated
newest added

/kind feature **Describe the solution you'd like** [A clear and concise description of what you want to happen.] we use calico by default now , e.g the security group is...

kind/feature

/kind bug **What steps did you take and what happened:** Unable to provision VM on INTERNAL network. On our openstack network are like this ``` (openstack) subnet list +--------------------------------------+-----------------------+--------------------------------------+------------------+ |...

kind/bug
lifecycle/stale

/kind feature **Describe the solution you'd like** Currently, CAPO machines require that a failure domain (availability zone) is specified. However there are a number of cases where this results in...

kind/feature

**What this PR does / why we need it**: **Which issue(s) this PR fixes** *(optional, in `fixes #(, fixes #, ...)` format, will close the issue(s) when PR gets merged)*:...

do-not-merge/hold
lifecycle/stale
cncf-cla: yes
approved
size/XS
lgtm

**What this PR does / why we need it**: This is to automatically bump versions through pull requests. **Which issue(s) this PR fixes** *(optional, in `fixes #(, fixes #, ...)`...

size/M
do-not-merge/hold
lifecycle/stale
cncf-cla: yes
approved
lgtm
ok-to-test

/kind feature **Describe the solution you'd like** Currently the OpenStack loadbalancer ***monitor*** for the API server created by CAPO has hardcoded settings, as seen in: https://github.com/kubernetes-sigs/cluster-api-provider-openstack/blob/944b2658fb11e8212aab43e5bbf112b15a8bb75a/pkg/cloud/services/loadbalancer/loadbalancer.go#L223-L230 In other words, `Delay:...

kind/feature
help wanted
good first issue
lifecycle/stale

/kind bug **What steps did you take and what happened:** [A clear and concise description of what the bug is.] I create a cluster with define subnet_id, network_id, external_network_id and...

kind/bug
lifecycle/stale

/kind feature Nowadays, CAPO will always choose the first subnet given the `OPENSTACK_EXTERNAL_NETWORK_ID` based on the current code [0]. Would be nice to have a new configuration option, something like...

kind/feature
lifecycle/stale

/kind bug **What steps did you take and what happened:** creating an ubuntu 20.04 compatible image for CAPO, kubelet doesn't start, with a weird message: `could not init cloud provider...

kind/bug

/kind bug **What steps did you take and what happened:** When I has experience with CAPI and CAPO, I created some clusters but it isn't smooth. Some usecases I got:...

kind/bug
lifecycle/rotten