Incompatible with IBM/vpc-go-sdk v0.77.0+: removed constants and types

[bryan-cox]

Summary

cluster-api-provider-ibmcloud is incompatible with github.com/IBM/vpc-go-sdk v0.77.0 and later. The SDK underwent a major breaking change in IBM/vpc-go-sdk#141 (API spec version 2025-12-09), which removed and restructured constants and types used throughout this project.

Breaking changes in vpc-go-sdk v0.77.0+

Removed constant

• NetworkACLRuleProtocolAllConst ("all") was removed and replaced by NetworkACLRuleProtocolAnyConst ("any")

Removed struct types

The per-protocol SecurityGroupRule subtypes were removed and flattened into a single SecurityGroupRule struct:

• SecurityGroupRuleSecurityGroupRuleProtocolAll — removed
• SecurityGroupRulePrototypeSecurityGroupRuleProtocolAll — removed
• SecurityGroupRuleSecurityGroupRuleProtocolIcmp → still exists
• SecurityGroupRuleSecurityGroupRuleProtocolTcpudp → still exists

Affected files in cluster-api-provider-ibmcloud

Constant references (NetworkACLRuleProtocolAllConst)

• api/powervs/v1beta2/types.go:326
• api/powervs/v1beta3/types.go:326
• api/vpc/v1beta2/types.go:205

Type references (SecurityGroupRuleSecurityGroupRuleProtocolAll)

• api/powervs/v1beta2/types.go:289 (string type reference)
• api/powervs/v1beta3/types.go:289 (string type reference)
• api/vpc/v1beta2/types.go:168 (string type reference)
• cloud/scope/vpc/cluster_v2.go (lines 1463, 1531, 1710, 1757)
• cloud/scope/powervs/powervs_cluster.go (lines 1471-1472, 1618-1619)
• cloud/scope/powervs/powervs_cluster_test.go (many references)

Kubebuilder validation enums

The +kubebuilder:validation:Enum=all;icmp;tcp;udp annotation needs to change to any;icmp;tcp;udp in the three API types files.

Impact

Downstream consumers like openshift/hypershift cannot bump vpc-go-sdk past v0.76.2 because the vendored cluster-api-provider-ibmcloud fails to compile. See OCPBUGS-78712.

Current vpc-go-sdk version

cluster-api-provider-ibmcloud currently requires vpc-go-sdk v0.76.2 in go.mod. All tagged releases through v0.14.0-alpha.0 are affected.

[Karthik-K-N]

Thanks @bryan-cox , Its been worked on by @Pacho20

Here is the PR #2603

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale