Openstack Load Balancer Octavia

[elgamal2020]

Environment:

• **Openstack

• OS (printf "$(uname -srm)\n$(cat /etc/os-release)\n"):

Linux 5.4.0-42-generic x86_64 NAME="Ubuntu" VERSION="20.04.1 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.1 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" VERSION_CODENAME=focal

• Version of Ansible (ansible --version):

• Version of Python (python --version):

Kubespray version (commit) (git rev-parse --short HEAD): 2de6a567

Network plugin used:

CALICO AND multus

cat inventory/octavia/group_vars/all/openstack.yml
## When OpenStack is used, Cinder version can be explicitly specified if autodetection fails (Fixed in 1.9: https://github.com/kubernetes/kubernetes/issues/50461)
# openstack_blockstorage_version: "v1/v2/auto (default)"
# openstack_blockstorage_ignore_volume_az: yes
## When OpenStack is used, if LBaaSv2 is available you can enable it with the following 2 variables.
# openstack_lbaas_enabled: True
# openstack_lbaas_subnet_id: "Neutron subnet ID (not network ID) to create LBaaS VIP"
## To enable automatic floating ip provisioning, specify a subnet.
# openstack_lbaas_floating_network_id: "Neutron network ID (not subnet ID) to get floating IP from, disabled by default"
## Override default LBaaS behavior
# openstack_lbaas_use_octavia: False
# openstack_lbaas_method: "ROUND_ROBIN"
# openstack_lbaas_provider: "haproxy"
# openstack_lbaas_create_monitor: "yes"
# openstack_lbaas_monitor_delay: "1m"
# openstack_lbaas_monitor_timeout: "30s"
# openstack_lbaas_monitor_max_retries: "3"

## Values for the external OpenStack Cloud Controller
external_openstack_lbaas_network_id: "1a550851-75b1-4d48-bafc-d873019c2800"
external_openstack_lbaas_subnet_id: "1832a495-ca91-4cbf-b01b-9505ab434e58"
external_openstack_lbaas_floating_network_id: "0c6dc85f-d0f7-4b22-96fe-3efa50608688"
external_openstack_lbaas_floating_subnet_id: "62b56e82-e0d5-4a88-9981-5117d1f4a4df"
external_openstack_lbaas_use_octavia: true
external_openstack_lbaas_method: "ROUND_ROBIN"
external_openstack_lbaas_create_monitor: false
external_openstack_lbaas_monitor_delay: "1m"
external_openstack_lbaas_monitor_timeout: "30s"
external_openstack_lbaas_monitor_max_retries: "3"
external_openstack_lbaas_manage_security_groups: false
external_openstack_lbaas_internal_lb: false
external_openstack_network_ipv6_disabled: false
external_openstack_network_internal_networks:
   - "Internal10.20.10"
     #external_openstack_network_public_networks:
     # - ""
external_openstack_metadata_search_order: "configDrive,metadataService"

## Application credentials to authenticate against Keystone API
## Those settings will take precedence over username and password that might be set your environment
## All of them are required
# external_openstack_application_credential_name:
# external_openstack_application_credential_id:
# external_openstack_application_credential_secret:

## The tag of the external OpenStack Cloud Controller image
external_openstack_cloud_controller_image_tag: "latest"

## To use Cinder CSI plugin to provision volumes set this value to true
## Make sure to source in the openstack credentials
cinder_csi_enabled: true
cinder_csi_controller_replicas: 1

I have applied the above configuration

and I dont get an ingress configured / octavia is not configured

Only the directory is created

$ ll /etc/kubernetes/octavia-ingress-controller
total 8
drwxr-xr-x 2 root root 4096 Sep 25 05:15 ./
drwxr-xr-x 5 kube root 4096 Oct  3 04:00 ../

[fejta-bot]

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

[fejta-bot]

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

[fejta-bot]

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

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/kubespray/issues/6789#issuecomment-788656843): >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](https://github.com/kubernetes/community). >/close 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.

[ayaseen]

What is the update on this issue, I am facing the same?!

[deba10106]

I'm also facing the same issue. Please let me know if anyone got any solution