🌱 E2E: Install independent Metal3 IPAM after upgrade #2382

lentzi90 · 2025-03-07T13:25:40Z

What this PR does / why we need it:

The Metal3 IPAM was previously bundled with CAPM3. Now we deploy it
separately as a CAPI IPAM provider. In clusterctl upgrade tests going
from a version where IPAM is bundled, to a version where it is not, we
must install it after the upgrade.
This commit adds a post upgrade hook to the clusterctl upgrade tests
that installs the Metal3 IPAM.

NOTE: This also includes #2380 we can merge that first or we can close it. I just wanted to make sure I don't hit that issue when testing the upgrade.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

metal3-io-bot · 2025-03-07T13:25:45Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from lentzi90. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

lentzi90 · 2025-03-07T13:34:24Z

/test metal3-e2e-clusterctl-upgrade-test-main

peppi-lotta · 2025-03-10T07:43:01Z

You are using metal3 as provider name but currently it's actually metal3ipam and this is why the test is not passing probably.

I created a PR to change it to Metal3 because that is a better and more correct name.
PR is here: metal3-io/metal3-dev-env#1509

adilGhaffarDev · 2025-03-10T09:22:23Z

/test metal3-e2e-clusterctl-upgrade-test-main

adilGhaffarDev · 2025-03-10T09:25:24Z

let's change the provider name here too:

cluster-api-provider-metal3/test/e2e/pivoting.go

Line 39 in 6fef657

Metal3ipamProviderName = "metal3ipam"

lentzi90 · 2025-03-10T11:04:04Z

/test metal3-e2e-clusterctl-upgrade-test-main

tuminoid · 2025-03-10T17:13:32Z

/test metal3-e2e-clusterctl-upgrade-test-main

tuminoid · 2025-03-12T05:36:02Z

/test metal3-e2e-clusterctl-upgrade-test-main

lentzi90 · 2025-03-12T15:39:05Z

/test metal3-e2e-clusterctl-upgrade-test-main

tuminoid · 2025-03-13T06:43:32Z

It is still complaining about target provider components for IPAM, even with the new name. I don't see open PRs anymore in any repo related to this, besides this one. What are we missing?

lentzi90 · 2025-03-13T07:02:29Z

There is something wrong with the clusterctl-config. It doesn't have the Metal3 IPAM provider listed. 🤔

tuminoid · 2025-03-13T07:42:01Z

There is something wrong with the clusterctl-config. It doesn't have the Metal3 IPAM provider listed. 🤔

We added it here and adjusted that here ... hmm.

adilGhaffarDev · 2025-03-13T07:52:08Z

There is something wrong with the clusterctl-config. It doesn't have the Metal3 IPAM provider listed. 🤔

We can move the following code to ci-e2e.sh

https://github.com/metal3-io/metal3-dev-env/blob/d831cba0825498a685d3b116183ee79dad00e358/03_launch_mgmt_cluster.sh#L499C1-L505C4

and try again. But I am not sure why dev-env is not setting it.
It should be fine to move it there for the main branch.

lentzi90 · 2025-03-13T08:07:53Z

Dev-env is setting it but possibly not in the place that is used by this test. There could also be something with the overrides structure that need to be adjusted.

lentzi90 · 2025-03-13T08:12:43Z

This is from earlier in the test. Does it look correct? I'm getting very confused with all the overrides and provider=... 😵

 + clusterctl init --core cluster-api:v1.9.5 --bootstrap kubeadm:v1.9.5 --control-plane kubeadm:v1.9.5 --infrastructure=metal3:v1.10.99 -v5 --ipam=metal3:v1.10.99
 Using configuration file="/home/metal3ci/.config/cluster-api/clusterctl.yaml"
 Installing the clusterctl inventory CRD
 Creating CustomResourceDefinition="providers.clusterctl.cluster.x-k8s.io"
 Fetching providers
 Potential override file searchFile="/home/metal3ci/.config/cluster-api/overrides/cluster-api/v1.9.5/core-components.yaml" provider="cluster-api" version="v1.9.5"
 Fetching file="core-components.yaml" provider="cluster-api" type="CoreProvider" version="v1.9.5"
 Potential override file searchFile="/home/metal3ci/.config/cluster-api/overrides/bootstrap-kubeadm/v1.9.5/bootstrap-components.yaml" provider="bootstrap-kubeadm" version="v1.9.5"
 Fetching file="bootstrap-components.yaml" provider="kubeadm" type="BootstrapProvider" version="v1.9.5"
 Potential override file searchFile="/home/metal3ci/.config/cluster-api/overrides/control-plane-kubeadm/v1.9.5/control-plane-components.yaml" provider="control-plane-kubeadm" version="v1.9.5"
 Fetching file="control-plane-components.yaml" provider="kubeadm" type="ControlPlaneProvider" version="v1.9.5"
 Potential override file searchFile="/home/metal3ci/.config/cluster-api/overrides/infrastructure-metal3/v1.10.99/infrastructure-components.yaml" provider="infrastructure-metal3" version="v1.10.99"
 Using override="infrastructure-components.yaml" provider="infrastructure-metal3" version="v1.10.99"
 Potential override file searchFile="/home/metal3ci/.config/cluster-api/overrides/ipam-metal3/v1.10.99/ipam-components.yaml" provider="ipam-metal3" version="v1.10.99"
 Using override="ipam-components.yaml" provider="ipam-metal3" version="v1.10.99"
 Potential override file searchFile="/home/metal3ci/.config/cluster-api/overrides/cluster-api/v1.9.5/metadata.yaml" provider="cluster-api" version="v1.9.5"
 Fetching file="metadata.yaml" provider="cluster-api" type="CoreProvider" version="v1.9.5"
 Potential override file searchFile="/home/metal3ci/.config/cluster-api/overrides/bootstrap-kubeadm/v1.9.5/metadata.yaml" provider="bootstrap-kubeadm" version="v1.9.5"
 Fetching file="metadata.yaml" provider="kubeadm" type="BootstrapProvider" version="v1.9.5"
 Potential override file searchFile="/home/metal3ci/.config/cluster-api/overrides/control-plane-kubeadm/v1.9.5/metadata.yaml" provider="control-plane-kubeadm" version="v1.9.5"
 Fetching file="metadata.yaml" provider="kubeadm" type="ControlPlaneProvider" version="v1.9.5"
 Potential override file searchFile="/home/metal3ci/.config/cluster-api/overrides/infrastructure-metal3/v1.10.99/metadata.yaml" provider="infrastructure-metal3" version="v1.10.99"
 Using override="metadata.yaml" provider="infrastructure-metal3" version="v1.10.99"
 Potential override file searchFile="/home/metal3ci/.config/cluster-api/overrides/ipam-metal3/v1.10.99/metadata.yaml" provider="ipam-metal3" version="v1.10.99"
 Using override="metadata.yaml" provider="ipam-metal3" version="v1.10.99"

adilGhaffarDev · 2025-03-13T08:22:11Z

This is from earlier in the test. Does it look correct? I'm getting very confused with all the overrides and provider=... 😵

 + clusterctl init --core cluster-api:v1.9.5 --bootstrap kubeadm:v1.9.5 --control-plane kubeadm:v1.9.5 --infrastructure=metal3:v1.10.99 -v5 --ipam=metal3:v1.10.99
 Using configuration file="/home/metal3ci/.config/cluster-api/clusterctl.yaml"
 Installing the clusterctl inventory CRD
 Creating CustomResourceDefinition="providers.clusterctl.cluster.x-k8s.io"
 Fetching providers
 Potential override file searchFile="/home/metal3ci/.config/cluster-api/overrides/cluster-api/v1.9.5/core-components.yaml" provider="cluster-api" version="v1.9.5"
 Fetching file="core-components.yaml" provider="cluster-api" type="CoreProvider" version="v1.9.5"
 Potential override file searchFile="/home/metal3ci/.config/cluster-api/overrides/bootstrap-kubeadm/v1.9.5/bootstrap-components.yaml" provider="bootstrap-kubeadm" version="v1.9.5"
 Fetching file="bootstrap-components.yaml" provider="kubeadm" type="BootstrapProvider" version="v1.9.5"
 Potential override file searchFile="/home/metal3ci/.config/cluster-api/overrides/control-plane-kubeadm/v1.9.5/control-plane-components.yaml" provider="control-plane-kubeadm" version="v1.9.5"
 Fetching file="control-plane-components.yaml" provider="kubeadm" type="ControlPlaneProvider" version="v1.9.5"
 Potential override file searchFile="/home/metal3ci/.config/cluster-api/overrides/infrastructure-metal3/v1.10.99/infrastructure-components.yaml" provider="infrastructure-metal3" version="v1.10.99"
 Using override="infrastructure-components.yaml" provider="infrastructure-metal3" version="v1.10.99"
 Potential override file searchFile="/home/metal3ci/.config/cluster-api/overrides/ipam-metal3/v1.10.99/ipam-components.yaml" provider="ipam-metal3" version="v1.10.99"
 Using override="ipam-components.yaml" provider="ipam-metal3" version="v1.10.99"
 Potential override file searchFile="/home/metal3ci/.config/cluster-api/overrides/cluster-api/v1.9.5/metadata.yaml" provider="cluster-api" version="v1.9.5"
 Fetching file="metadata.yaml" provider="cluster-api" type="CoreProvider" version="v1.9.5"
 Potential override file searchFile="/home/metal3ci/.config/cluster-api/overrides/bootstrap-kubeadm/v1.9.5/metadata.yaml" provider="bootstrap-kubeadm" version="v1.9.5"
 Fetching file="metadata.yaml" provider="kubeadm" type="BootstrapProvider" version="v1.9.5"
 Potential override file searchFile="/home/metal3ci/.config/cluster-api/overrides/control-plane-kubeadm/v1.9.5/metadata.yaml" provider="control-plane-kubeadm" version="v1.9.5"
 Fetching file="metadata.yaml" provider="kubeadm" type="ControlPlaneProvider" version="v1.9.5"
 Potential override file searchFile="/home/metal3ci/.config/cluster-api/overrides/infrastructure-metal3/v1.10.99/metadata.yaml" provider="infrastructure-metal3" version="v1.10.99"
 Using override="metadata.yaml" provider="infrastructure-metal3" version="v1.10.99"
 Potential override file searchFile="/home/metal3ci/.config/cluster-api/overrides/ipam-metal3/v1.10.99/metadata.yaml" provider="ipam-metal3" version="v1.10.99"
 Using override="metadata.yaml" provider="ipam-metal3" version="v1.10.99"

this seems fine to me, here --ipam=metal3 is working fine. This is coming from dev-env, which is launching a management cluster. What seems wrong here?

lentzi90 · 2025-03-13T08:32:36Z

It is probably correct. I'm just getting confused by at all.
I found another thing to check now... do we need to add it in the e2e config? We have config for all the other things there (core, control-plane, bootstrap and infra).

adilGhaffarDev · 2025-03-13T08:36:10Z

I found another thing to check now... do we need to add it in the e2e config? We have config for all the other things there (core, control-plane, bootstrap and infra).

yes we need to add there, I forgot about that. For e2e it gets it from there.

lentzi90 · 2025-03-13T08:56:55Z

/test metal3-e2e-clusterctl-upgrade-test-main

lentzi90 · 2025-03-13T09:25:49Z

[2025-03-13T09:17:51.985Z]   [FAILED] Failed to resolve release markers in e2e test config file

[2025-03-13T09:17:51.985Z]   Expected success, but got an error:

[2025-03-13T09:17:51.985Z]       <*errors.withStack | 0xc000b80cc0>: 

[2025-03-13T09:17:51.985Z]       failed resolving release url "{go://github.com/metal3-io/[email protected]}": failed to find releases tagged with a valid semantic version number

[2025-03-13T09:17:51.985Z]       {

[2025-03-13T09:17:51.985Z]           error: <*errors.withMessage | 0xc000aafee0>{

[2025-03-13T09:17:51.985Z]               cause: <*errors.fundamental | 0xc000b80c90>{

[2025-03-13T09:17:51.985Z]                   msg: "failed to find releases tagged with a valid semantic version number",

[2025-03-13T09:17:51.985Z]                   stack: [0x3720925, 0x371ff1e, 0x371fc4b, 0x371f519, 0x39b3a75, 0x397d29c, 0x1735346, 0x1734459, 0x1b8568e, 0x1b959ee, 0x1b9921b, 0x16b1101],

[2025-03-13T09:17:51.985Z]               },

[2025-03-13T09:17:51.985Z]               msg: "failed resolving release url \"{go://github.com/metal3-io/[email protected]}\"",

[2025-03-13T09:17:51.985Z]           },

[2025-03-13T09:17:51.985Z]           stack: [0x371fdcb, 0x371f519, 0x39b3a75, 0x397d29c, 0x1735346, 0x1734459, 0x1b8568e, 0x1b959ee, 0x1b9921b, 0x16b1101],

[2025-03-13T09:17:51.985Z]       }

I don't get it. We have proper tags there. What is the issue? 🤔

tuminoid · 2025-03-13T09:31:59Z

[2025-03-13T09:17:51.985Z]   [FAILED] Failed to resolve release markers in e2e test config file

[2025-03-13T09:17:51.985Z]   Expected success, but got an error:

[2025-03-13T09:17:51.985Z]       <*errors.withStack | 0xc000b80cc0>: 

[2025-03-13T09:17:51.985Z]       failed resolving release url "{go://github.com/metal3-io/[email protected]}": failed to find releases tagged with a valid semantic version number

[2025-03-13T09:17:51.985Z]       {

[2025-03-13T09:17:51.985Z]           error: <*errors.withMessage | 0xc000aafee0>{

[2025-03-13T09:17:51.985Z]               cause: <*errors.fundamental | 0xc000b80c90>{

[2025-03-13T09:17:51.985Z]                   msg: "failed to find releases tagged with a valid semantic version number",

[2025-03-13T09:17:51.985Z]                   stack: [0x3720925, 0x371ff1e, 0x371fc4b, 0x371f519, 0x39b3a75, 0x397d29c, 0x1735346, 0x1734459, 0x1b8568e, 0x1b959ee, 0x1b9921b, 0x16b1101],

[2025-03-13T09:17:51.985Z]               },

[2025-03-13T09:17:51.985Z]               msg: "failed resolving release url \"{go://github.com/metal3-io/[email protected]}\"",

[2025-03-13T09:17:51.985Z]           },

[2025-03-13T09:17:51.985Z]           stack: [0x371fdcb, 0x371f519, 0x39b3a75, 0x397d29c, 0x1735346, 0x1734459, 0x1b8568e, 0x1b959ee, 0x1b9921b, 0x16b1101],

[2025-03-13T09:17:51.985Z]       }

I don't get it. We have proper tags there. What is the issue? 🤔

It is looking for exactly v1.9 which we don't have? We have v1.9.0

lentzi90 · 2025-03-13T09:34:59Z

I don't think so. We use this same syntax everywhere to get the latest patch version for that minor version.
Edit: With "everywhere" I mean in the e2e config

adilGhaffarDev · 2025-03-13T09:37:43Z

test/e2e/config/e2e_conf.yaml

+- name: metal3
+  type: IPAMProvider
+  versions:
+  - name: "{go://github.com/metal3-io/[email protected]}"


Here, IPAM is slightly different from other providers because we want to test the main branch rather than version 1.9.

However, I'm wondering how that would work. We can use v1.10.99 instead of {go://github.com/metal3-io/[email protected]}, but how will we obtain the YAML resources for the main branch? Should we push them somewhere during our image-building process? As far as I know, we only push images to quay.

Oh we have them in the overrides folder:

Potential override file searchFile="/home/metal3ci/.config/cluster-api/overrides/ipam-metal3/v1.10.99/metadata.yaml" provider="ipam-metal3" version="v1.10.99" Using override="metadata.yaml" provider="ipam-metal3" version="v1.10.99"

We used them in dev-env, we can use these ones.

adilGhaffarDev · 2025-03-13T09:40:01Z

test/e2e/upgrade_clusterctl_test.go

+		ClusterctlConfigPath: clusterctlConfigPath,
+		KubeconfigPath:       clusterProxy.GetKubeconfigPath(),
+		LogFolder:            ipamDeployLogFolder,
+		IPAMProviders:        []string{Metal3ipamProviderName},


Suggested change

IPAMProviders: []string{Metal3ipamProviderName},

IPAMProviders: []string{fmt.Sprintf(Metal3ipamProviderName, ipamRelease)},

We need to give the version here.

adilGhaffarDev · 2025-03-13T10:36:02Z

I don't get it. We have proper tags there. What is the issue? 🤔

[2025-03-13T09:17:51.985Z]   [FAILED] Failed to resolve release markers in e2e test config file

[2025-03-13T09:17:51.985Z]   Expected success, but got an error:

[2025-03-13T09:17:51.985Z]       <*errors.withStack | 0xc000b80cc0>: 

[2025-03-13T09:17:51.985Z]       failed resolving release url "{go://github.com/metal3-io/[email protected]}": failed to find releases tagged with a valid semantic version number

[2025-03-13T09:17:51.985Z]       {

[2025-03-13T09:17:51.985Z]           error: <*errors.withMessage | 0xc000aafee0>{

[2025-03-13T09:17:51.985Z]               cause: <*errors.fundamental | 0xc000b80c90>{

[2025-03-13T09:17:51.985Z]                   msg: "failed to find releases tagged with a valid semantic version number",

[2025-03-13T09:17:51.985Z]                   stack: [0x3720925, 0x371ff1e, 0x371fc4b, 0x371f519, 0x39b3a75, 0x397d29c, 0x1735346, 0x1734459, 0x1b8568e, 0x1b959ee, 0x1b9921b, 0x16b1101],

[2025-03-13T09:17:51.985Z]               },

[2025-03-13T09:17:51.985Z]               msg: "failed resolving release url \"{go://github.com/metal3-io/[email protected]}\"",

[2025-03-13T09:17:51.985Z]           },

[2025-03-13T09:17:51.985Z]           stack: [0x371fdcb, 0x371f519, 0x39b3a75, 0x397d29c, 0x1735346, 0x1734459, 0x1b8568e, 0x1b959ee, 0x1b9921b, 0x16b1101],

[2025-03-13T09:17:51.985Z]       }

I don't get it. We have proper tags there. What is the issue? 🤔

This is failing because it attempts to find the metadata.yaml file in the v1.9.4 release of IPAM, treating it as a CAPI provider. However, our IPAM was not a provider in v1.9, so the file does not exist in that release (see https://github.com/metal3-io/ip-address-manager/releases/tag/v1.9.4). Starting from v1.10, it will be available.

lentzi90 · 2025-03-13T10:46:11Z

This is failing because it attempts to find the metadata.yaml file in the v1.9.4 release of IPAM, treating it as a CAPI provider. However, our IPAM was not a provider in v1.9, so the file does not exist in that release (see https://github.com/metal3-io/ip-address-manager/releases/tag/v1.9.4). Starting from v1.10, it will be available.

Good catch! We will need to do it with an override then I guess?

adilGhaffarDev · 2025-03-13T11:01:51Z

This is failing because it attempts to find the metadata.yaml file in the v1.9.4 release of IPAM, treating it as a CAPI provider. However, our IPAM was not a provider in v1.9, so the file does not exist in that release (see https://github.com/metal3-io/ip-address-manager/releases/tag/v1.9.4). Starting from v1.10, it will be available.

Good catch! We will need to do it with an override then I guess?

yes

lentzi90 · 2025-03-14T07:22:35Z

I wonder how much difference there really is in the manifests. Going to do a test run with just added metadata and see how it goes.
/test metal3-e2e-clusterctl-upgrade-test-main

lentzi90 · 2025-03-14T07:56:06Z

/test metal3-e2e-clusterctl-upgrade-test-main

adilGhaffarDev · 2025-03-14T08:00:54Z

this is probably still going to fail because the code that is resolving these markers: {go://github.com/metal3-io/[email protected]} does not check sourcePath. It checks metadata in the actual release, and this is to make sure a valid release is available.

lentzi90 · 2025-03-14T09:20:12Z

/test metal3-e2e-clusterctl-upgrade-test-main

lentzi90 · 2025-03-14T09:51:40Z

/test metal3-e2e-clusterctl-upgrade-test-main

lentzi90 · 2025-03-14T12:01:24Z

/test metal3-e2e-clusterctl-upgrade-test-main

The Metal3 IPAM was previously bundled with CAPM3. Now we deploy it separately as a CAPI IPAM provider. In clusterctl upgrade tests going from a version where IPAM is bundled, to a version where it is not, we must install it after the upgrade. This commit adds a post upgrade hook to the clusterctl upgrade tests that installs the Metal3 IPAM. Signed-off-by: Lennart Jern <[email protected]>

lentzi90 · 2025-03-14T12:34:01Z

/test metal3-e2e-clusterctl-upgrade-test-main

metal3-io-bot · 2025-03-14T14:38:32Z

@lentzi90: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
metal3-e2e-clusterctl-upgrade-test-main	`d97c33f`	link	false	`/test metal3-e2e-clusterctl-upgrade-test-main`

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

metal3-io-bot · 2025-03-14T14:38:32Z

@lentzi90: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
metal3-e2e-clusterctl-upgrade-test-main	`d97c33f`	link	false	`/test metal3-e2e-clusterctl-upgrade-test-main`

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

metal3-io-bot requested review from adilGhaffarDev and mquhuy March 7, 2025 13:25

metal3-io-bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Mar 7, 2025

lentzi90 force-pushed the lentzi90/clusterctl-upgrade-ipam branch from f25f534 to ef7f5cc Compare March 7, 2025 13:30

lentzi90 mentioned this pull request Mar 10, 2025

🌱 E2E: Ensure cert-manager webhook is available #2380

Merged

lentzi90 force-pushed the lentzi90/clusterctl-upgrade-ipam branch from ef7f5cc to 03dd3e7 Compare March 10, 2025 10:59

lentzi90 force-pushed the lentzi90/clusterctl-upgrade-ipam branch from 03dd3e7 to 3612a78 Compare March 12, 2025 13:52

metal3-io-bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Mar 12, 2025

lentzi90 closed this Mar 13, 2025

lentzi90 force-pushed the lentzi90/clusterctl-upgrade-ipam branch from 3612a78 to 5dd8f6e Compare March 13, 2025 08:55

metal3-io-bot removed the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Mar 13, 2025

metal3-io-bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Mar 13, 2025

lentzi90 reopened this Mar 13, 2025

adilGhaffarDev reviewed Mar 13, 2025

View reviewed changes

lentzi90 force-pushed the lentzi90/clusterctl-upgrade-ipam branch from 5dd8f6e to 30f2e5f Compare March 13, 2025 10:44

lentzi90 force-pushed the lentzi90/clusterctl-upgrade-ipam branch from 30f2e5f to 70bd8c9 Compare March 13, 2025 10:52

lentzi90 force-pushed the lentzi90/clusterctl-upgrade-ipam branch from 70bd8c9 to 13885d1 Compare March 14, 2025 07:55

lentzi90 force-pushed the lentzi90/clusterctl-upgrade-ipam branch from 13885d1 to 09ad410 Compare March 14, 2025 08:56

lentzi90 force-pushed the lentzi90/clusterctl-upgrade-ipam branch from 09ad410 to f62fdf8 Compare March 14, 2025 09:51

lentzi90 force-pushed the lentzi90/clusterctl-upgrade-ipam branch from f62fdf8 to 3b3c78b Compare March 14, 2025 12:01

lentzi90 force-pushed the lentzi90/clusterctl-upgrade-ipam branch from 3b3c78b to d97c33f Compare March 14, 2025 12:32

	IPAMProviders: []string{Metal3ipamProviderName},
	IPAMProviders: []string{fmt.Sprintf(Metal3ipamProviderName, ipamRelease)},

🌱 E2E: Install independent Metal3 IPAM after upgrade #2382

Are you sure you want to change the base?

🌱 E2E: Install independent Metal3 IPAM after upgrade #2382

Conversation

lentzi90 commented Mar 7, 2025

metal3-io-bot commented Mar 7, 2025

lentzi90 commented Mar 7, 2025

peppi-lotta commented Mar 10, 2025 • edited Loading

adilGhaffarDev commented Mar 10, 2025

adilGhaffarDev commented Mar 10, 2025

lentzi90 commented Mar 10, 2025

tuminoid commented Mar 10, 2025

tuminoid commented Mar 12, 2025

lentzi90 commented Mar 12, 2025

tuminoid commented Mar 13, 2025

lentzi90 commented Mar 13, 2025

tuminoid commented Mar 13, 2025

adilGhaffarDev commented Mar 13, 2025

lentzi90 commented Mar 13, 2025

lentzi90 commented Mar 13, 2025

adilGhaffarDev commented Mar 13, 2025

lentzi90 commented Mar 13, 2025

adilGhaffarDev commented Mar 13, 2025

lentzi90 commented Mar 13, 2025

lentzi90 commented Mar 13, 2025

tuminoid commented Mar 13, 2025

lentzi90 commented Mar 13, 2025 • edited Loading

adilGhaffarDev Mar 13, 2025

Choose a reason for hiding this comment

adilGhaffarDev Mar 13, 2025

Choose a reason for hiding this comment

adilGhaffarDev Mar 13, 2025

Choose a reason for hiding this comment

adilGhaffarDev commented Mar 13, 2025

lentzi90 commented Mar 13, 2025

adilGhaffarDev commented Mar 13, 2025

lentzi90 commented Mar 14, 2025

lentzi90 commented Mar 14, 2025

adilGhaffarDev commented Mar 14, 2025

lentzi90 commented Mar 14, 2025

lentzi90 commented Mar 14, 2025

lentzi90 commented Mar 14, 2025

lentzi90 commented Mar 14, 2025

metal3-io-bot commented Mar 14, 2025

metal3-io-bot commented Mar 14, 2025

peppi-lotta commented Mar 10, 2025 •

edited

Loading

lentzi90 commented Mar 13, 2025 •

edited

Loading