Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uni delta #191

Merged

Conversation

jirimacku
Copy link
Contributor

@jirimacku jirimacku commented Apr 22, 2024

This PR contains the necessary custom resources for deploying OpenStack Services on OpenShift. The CRs are for the proposed uni*delta deployed topology.

Copy link
Contributor

@abays abays Apr 22, 2024

Choose a reason for hiding this comment

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

Doing this sort of linking violates the default "load restriction" policy of Kustomize, because you are importing resources from outside of the dir. Is there some reason you can't just use lib/dataplane directly as a component in your dt/uni04delta/ceph/kustomization.yaml? You can still use all of the patches and the replacements that you have there.

automation/vars/uni04delta.yaml Show resolved Hide resolved
oc -n openstack wait osdpd
edpm-deployment
--for condition=Ready
--timeout=1200s
Copy link
Contributor

Choose a reason for hiding this comment

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

the timeout here was not sufficient it took me around 22 minutes, so better to move it to 1800 or 2400 for slow systems

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed

dt/uni04delta/kustomization.yaml Outdated Show resolved Hide resolved
lib/dataplane/kustomization.yaml Outdated Show resolved Hide resolved
examples/dt/uni04delta/edpm-pre-ceph/values.yaml Outdated Show resolved Hide resolved
examples/dt/uni04delta/edpm-pre-ceph/values.yaml Outdated Show resolved Hide resolved
examples/dt/uni04delta/values-wo-ceph-client.yaml Outdated Show resolved Hide resolved
enable_debug: false
gather_facts: false
image_tag: current-podified
neutron_physical_bridge_name: br-ex
Copy link
Contributor

Choose a reason for hiding this comment

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

neutron vars can be dropped from ceph nodeset

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I needed to put the neutron_physical_bridge_name: br-ex and
neutron_public_interface_name: eth0 back. The deployment is failing without them.

examples/dt/uni04delta/edpm-pre-ceph/values.yaml Outdated Show resolved Hide resolved
@fultonj
Copy link
Contributor

fultonj commented May 7, 2024

@jirimacku when you're ready for this to be reviewed further, please take it out of draft and rebase.

Comment on lines +20 to +22
- ../../lib/networking/metallb
- ../../lib/networking/netconfig
- ../../lib/networking/nad
Copy link
Contributor

Choose a reason for hiding this comment

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

Optional: this can be simplified to - ../../lib/networking, but it works as-is as well

@jirimacku jirimacku marked this pull request as ready for review May 10, 2024 12:35
@jirimacku
Copy link
Contributor Author

The deployment itself is passing - thanks to everybody!
Problems observed so far:
8 of 9 of those TestNetworkBasicOp are failing:

Details: Fault: {'code': 500, 'created': '2024-05-10T12:08:20Z', 'message': 'No valid host was found. '}. Request ID of server operation performed before checking the server status req-5bd3c1e0-b8d3-4d1d-bd7a-6c0439ddacc0.

On one of the compute nodes I realized there might be a problem with the certificates rabbitq is using:

c6fef89332bf  quay.io/podified-antelope-centos9/openstack-nova-compute@sha256:4c886d06a5411e07dae0f3985cea4d40bee717cf6c2acac115de2187efd388d1                kolla_start  50 minutes ago     Up 26 minutes                 nova_compute
[zuul@compute-0 ~]$ sudo podman logs --tail 5 c6fef89332bf
2024-05-10 12:48:37.714 2 ERROR oslo.messaging._drivers.impl_rabbit [None req-4fb9d29f-503a-4efd-b09c-a20967f17a39 - - - - - -] Connection failed: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1129) (retrying in 31.0 seconds): ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1129)
2024-05-10 12:49:08.774 2 ERROR oslo.messaging._drivers.impl_rabbit [None req-4fb9d29f-503a-4efd-b09c-a20967f17a39 - - - - - -] Connection failed: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1129) (retrying in 31.0 seconds): ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1129)
2024-05-10 12:49:39.820 2 ERROR oslo.messaging._drivers.impl_rabbit [None req-4fb9d29f-503a-4efd-b09c-a20967f17a39 - - - - - -] Connection failed: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1129) (retrying in 31.0 seconds): ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1129)
2024-05-10 12:50:10.895 2 ERROR oslo.messaging._drivers.impl_rabbit [None req-4fb9d29f-503a-4efd-b09c-a20967f17a39 - - - - - -] Connection failed: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1129) (retrying in 31.0 seconds): ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1129)
2024-05-10 12:50:41.951 2 ERROR oslo.messaging._drivers.impl_rabbit [None req-4fb9d29f-503a-4efd-b09c-a20967f17a39 - - - - - -] Connection failed: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1129) (retrying in 31.0 seconds): ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1129)

Any hint is appreciated.

@karelyatin
Copy link
Contributor

The deployment itself is passing - thanks to everybody! Problems observed so far: 8 of 9 of those TestNetworkBasicOp are failing:

Details: Fault: {'code': 500, 'created': '2024-05-10T12:08:20Z', 'message': 'No valid host was found. '}. Request ID of server operation performed before checking the server status req-5bd3c1e0-b8d3-4d1d-bd7a-6c0439ddacc0.

On one of the compute nodes I realized there might be a problem with the certificates rabbitq is using:

c6fef89332bf  quay.io/podified-antelope-centos9/openstack-nova-compute@sha256:4c886d06a5411e07dae0f3985cea4d40bee717cf6c2acac115de2187efd388d1                kolla_start  50 minutes ago     Up 26 minutes                 nova_compute
[zuul@compute-0 ~]$ sudo podman logs --tail 5 c6fef89332bf
2024-05-10 12:48:37.714 2 ERROR oslo.messaging._drivers.impl_rabbit [None req-4fb9d29f-503a-4efd-b09c-a20967f17a39 - - - - - -] Connection failed: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1129) (retrying in 31.0 seconds): ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1129)
2024-05-10 12:49:08.774 2 ERROR oslo.messaging._drivers.impl_rabbit [None req-4fb9d29f-503a-4efd-b09c-a20967f17a39 - - - - - -] Connection failed: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1129) (retrying in 31.0 seconds): ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1129)
2024-05-10 12:49:39.820 2 ERROR oslo.messaging._drivers.impl_rabbit [None req-4fb9d29f-503a-4efd-b09c-a20967f17a39 - - - - - -] Connection failed: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1129) (retrying in 31.0 seconds): ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1129)
2024-05-10 12:50:10.895 2 ERROR oslo.messaging._drivers.impl_rabbit [None req-4fb9d29f-503a-4efd-b09c-a20967f17a39 - - - - - -] Connection failed: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1129) (retrying in 31.0 seconds): ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1129)
2024-05-10 12:50:41.951 2 ERROR oslo.messaging._drivers.impl_rabbit [None req-4fb9d29f-503a-4efd-b09c-a20967f17a39 - - - - - -] Connection failed: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1129) (retrying in 31.0 seconds): ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1129)

Any hint is appreciated.

#191 (comment) should help

@leifmadsen leifmadsen added deployment-topology Deployment topology changes or implementations ↟ priority-high High priority item that needs to be reviewed and testing in short order labels May 13, 2024
@leifmadsen
Copy link
Contributor

Looks like this is getting close, but there are a few open comments that still need addressing.

  • split dataplane
  • missing ca-cert reference
  • missing input src_file
  • (optional) simplified call to networking lib vs multi-resource calls

- target:
kind: OpenStackDataPlaneDeployment
name: .*
patch: |-
Copy link
Contributor

Choose a reason for hiding this comment

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

isn't this patch duplicate of above replacements?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, I think so

Copy link
Contributor

Choose a reason for hiding this comment

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

@jirimacku can you check and clean.

Copy link
Contributor

Choose a reason for hiding this comment

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

It looks to be resolved now

Copy link
Contributor Author

Choose a reason for hiding this comment

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

cleaned and checked.

edpm_neutron_metadata_agent_image: '{{ registry_url }}/openstack-neutron-metadata-agent-ovn:{{ image_tag }}'
edpm_nodes_validation_validate_controllers_icmp: false
edpm_nodes_validation_validate_gateway_icmp: false
edpm_nova_compute_container_image: '{{ registry_url }}/openstack-nova-compute:{{ image_tag }}'
Copy link
Contributor

Choose a reason for hiding this comment

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

the images can be dropped. and also the references of registry_url and image_tag

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

- ceph_nfs
- ceph_rgw_frontend
- ceph_nfs_frontend
storage_mtu: 9000
Copy link
Contributor

Choose a reason for hiding this comment

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

these storage_* i think not needed here(as should be coming from dataplane-operator based on netconfig) but likely copied from vas, so can be checked and cleanedup later.

Copy link
Contributor

Choose a reason for hiding this comment

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

VA1 does the same because it overrides the default MTU of 1500 for the storage network and adds the storage management network. Both uniDelta and va1 deploy EDPM nodes which host Ceph.

The storage management network does not need to be created in IPAM on the controller node. It's only used by nodes hosting ceph for ceph to sync it's internal data. I don't think we need to block this over storage_mgmt_ network being here. If you have an more dataplane-operator-netconfig-like way to do this, then let me know and we can do a follow up patch on va1 and uniDelta.

https://github.com/openstack-k8s-operators/architecture/blob/main/examples/va/hci/edpm-pre-ceph/nodeset/values.yaml#L95-L99

Copy link
Contributor

Choose a reason for hiding this comment

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

yes was not blocking, just raised this so be checked later

kind: Kustomization

components:
# - ../../../va/hci/edpm-post-ceph/nodeset
Copy link
Contributor

Choose a reason for hiding this comment

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

comment part can be dropped

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

name: edpm-values
annotations:
config.kubernetes.io/local-config: "true"

Copy link
Contributor

Choose a reason for hiding this comment

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

why not using _src and _dst as same path? as with that it would be usable without relying on ci-framework generation logic.

timesync_ntp_servers:
- hostname: clock.redhat.com

edpm_iscsid_image: '{{ registry_url }}/openstack-iscsid:{{ image_tag }}'
Copy link
Contributor

Choose a reason for hiding this comment

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

same images and all references of registry_url and image_tag can be dropped

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed the -wo- files. Will also make the kustomization dry run passing in the gate.

examples/dt/uni04delta/values-wo-ceph-client.yaml Outdated Show resolved Hide resolved
nova_api_network: internalapi
nova_libvirt_network: internalapi

edpm_ceph_hci_pre_enabled_services:
Copy link
Contributor

Choose a reason for hiding this comment

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

this should be only needed in ceph nodesets

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed

examples/dt/uni04delta/values-wo-ceph-client.yaml Outdated Show resolved Hide resolved
Comment on lines 23 to 28
- name: network-values
build_output: control-plane.yaml
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed

@leifmadsen
Copy link
Contributor

@jirimacku I think it would be good to rebase this against main as well.

--timeout=600s
values:
- name: network-values
src: nncp/values.yaml
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
src: nncp/values.yaml
src_file: nncp/values.yaml

Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed

@jirimacku
Copy link
Contributor Author

Tested with test project. Deployment passed, tempest base test case passed.


# 4. Generate the Ceph nodeset deployment plan.

$ kustomize build --load-restrictor LoadRestrictionsNone > nodeset-pre-ceph.yaml
Copy link
Contributor

@fultonj fultonj May 17, 2024

Choose a reason for hiding this comment

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

Please remove --load-restrictor LoadRestrictionsNone. It's not necessary in order to build the nodeset-pre-ceph.yaml file.

[fultonj@runcible nodeset{uniDelta}]$ kustomize build > nodeset-pre-ceph-1.yaml 
[fultonj@runcible nodeset{uniDelta}]$ kustomize build --load-restrictor LoadRestrictionsNone > nodeset-pre-ceph-2.yaml 
[fultonj@runcible nodeset{uniDelta}]$ diff nodeset-pre-ceph-2.yaml nodeset-pre-ceph-1.yaml
[fultonj@runcible nodeset{uniDelta}]$ 

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done


# 8. Generate the Ceph data plane deployment plan.

$ kustomize build --load-restrictor LoadRestrictionsNone > deployment-pre-ceph.yaml
Copy link
Contributor

Choose a reason for hiding this comment

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

Please remove --load-restrictor LoadRestrictionsNone. I was able to build deployment-pre-ceph.yaml without it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

@fultonj
Copy link
Contributor

fultonj commented May 17, 2024

Overall this looks OK to me, but it needs to be rebased and have a few updates as I indicated in my comments.

Rebased

Thank you, yes the rebased version no longer removes barbican from VA1 so that's good.

Would you please squash this PR?

[fultonj@runcible edpm-pre-ceph{uniDelta}]$ git log | grep Author | head -46
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Pragadeeswaran Sathyanarayanan <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Jiri Macku <[email protected]>
Author: Pragadeeswaran Sathyanarayanan <[email protected]>
Author: Yatin Karel <[email protected]>
[fultonj@runcible edpm-pre-ceph{uniDelta}]$ 

@fultonj
Copy link
Contributor

fultonj commented May 17, 2024

Overall this PR looks good to me and provided it can be squashed and --load-restrictor LoadRestrictionsNone removed I'll be OK with merging.

metallb.universe.tf/loadBalancerIPs: 172.17.0.86

lbServiceType: LoadBalancer
storageClass: host-nfs-storageclass
Copy link
Contributor

Choose a reason for hiding this comment

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

We are not using host-nfs-storageclass but we can set it to local-storage. However, it would change with LVM operators are used.

Copy link
Contributor

Choose a reason for hiding this comment

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

I think should be changed to local-storage so it works like all of the other VAs/DTs.

The LVMS ci-framework PR will set the generated values.yaml to have the correct name depending on if cifmw_lvms is true or false.

openstack-k8s-operators/ci-framework#1707

Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think we should keep it as host-nfs-storageclass since it might make people think it needs some special storage.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

@jirimacku jirimacku force-pushed the uniDelta branch 3 times, most recently from 03a251e to 5e4a6ea Compare May 21, 2024 05:30
Copy link
Contributor

@karelyatin karelyatin left a comment

Choose a reason for hiding this comment

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

LGTM, just few minor fixes inline

- target:
kind: OpenStackDataPlaneDeployment
name: .*
patch: |-
Copy link
Contributor

Choose a reason for hiding this comment

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

@jirimacku can you check and clean.

[ovs]
igmp_snooping_enable = true
[ovn]
ovn_emit_need_to_frag = true
Copy link
Contributor

Choose a reason for hiding this comment

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

can disable this for now as per #228

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

- ceph_nfs
- ceph_rgw_frontend
- ceph_nfs_frontend
storage_mtu: 9000
Copy link
Contributor

Choose a reason for hiding this comment

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

yes was not blocking, just raised this so be checked later

automation/vars/uni04delta.yaml Show resolved Hide resolved
oc -n openstack wait osdpns
openstack-edpm
--for condition=SetupReady
--timeout=2400s
Copy link
Contributor

Choose a reason for hiding this comment

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

can lower the timeout here to for nodeset, as that doesn't need much time, likely leftover from dataplane split.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

Wait for nodeset deployment to finish

```bash
oc wait osdpns edpm-nodeset-values --for condition=SetupReady --timeout=1200s
Copy link
Contributor

Choose a reason for hiding this comment

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

s/edpm-nodeset-values/openstack-edpm

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

@arxcruz
Copy link
Contributor

arxcruz commented May 21, 2024

/lgtm
lgtm

@arxcruz
Copy link
Contributor

arxcruz commented May 21, 2024

/lgtm
lgtm

@openshift-ci openshift-ci bot added the lgtm label May 21, 2024
@arxcruz
Copy link
Contributor

arxcruz commented May 21, 2024

/lgtm
lgtm

@openshift-ci openshift-ci bot added the lgtm label May 21, 2024
@fultonj fultonj self-requested a review May 21, 2024 14:02
Copy link
Contributor

@fultonj fultonj left a comment

Choose a reason for hiding this comment

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

Thanks for making the most recent set of changes.

Copy link

openshift-ci bot commented May 21, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fultonj, jirimacku

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

Copy link
Contributor

Build succeeded (gate pipeline).
https://review.rdoproject.org/zuul/buildset/8f86378849d1477c80bbdb50cf13fe66

✔️ noop SUCCESS in 0s

@softwarefactory-project-zuul softwarefactory-project-zuul bot merged commit 68b1bbb into openstack-k8s-operators:main May 21, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved deployment-topology Deployment topology changes or implementations lgtm ↟ priority-high High priority item that needs to be reviewed and testing in short order
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants