Skip to content

Conversation

@sbueringer
Copy link
Member

@sbueringer sbueringer commented Oct 6, 2019

Ups, deleted the old branch so the old PR was closed. So again:

Okay I tested my existing multi-node setup and I tested it with remove networks filter. Both worked

@jichenjc Can you test if you're now able to use loadbalancers by setting the network and subnet fields (filters) in the ClusterSpec?

Edit: Old PR was this one: #475

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 6, 2019
@k8s-ci-robot k8s-ci-robot requested review from dims and ncdc October 6, 2019 12:11
@k8s-ci-robot k8s-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Oct 6, 2019
@sbueringer
Copy link
Member Author

/assign @jichenjc
/assign @hidekazuna

@fejta-bot
Copy link

Unknown CLA label state. Rechecking for CLA labels.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/check-cla

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Oct 6, 2019
@ncdc
Copy link
Contributor

ncdc commented Oct 7, 2019

/uncc

@k8s-ci-robot k8s-ci-robot removed the request for review from ncdc October 7, 2019 19:11
}
} else {
if openStackCluster.Status.Network == nil {
return nil, fmt.Errorf("no network was found in OpenStackCluster.Status.Network")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe we need add some info that because the machine doesn't have network spec and cluster network is also nil
so we return error..

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree. Fixed

@sbueringer sbueringer mentioned this pull request Oct 9, 2019
6 tasks
@jichenjc
Copy link
Contributor

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 11, 2019
@k8s-ci-robot k8s-ci-robot merged commit 554994e into kubernetes-sigs:master Oct 11, 2019
@sbueringer sbueringer deleted the pr-use-existing-networks branch January 4, 2020 15:07
pierreprinetti pushed a commit to shiftstack/cluster-api-provider-openstack that referenced this pull request Apr 22, 2024
* use existing networks, fallback to network/subnet defined in cluster status

* linter fixes

* remove the network filters which are not required anymore

* regen code/crds

* review fixes

* fix tests, by fixing kustomize

* fix tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants