Align max managed security priority behavior

What happened:

https://github.com/kubernetes-sigs/cloud-provider-azure/blob/master/pkg/provider/securitygroup/securityrule.go#L41

cloud-provider-azure/pkg/provider/securitygroup/securitygroup.go

Line 113 in 5909ab1

    
           func (helper *RuleHelper) nextRulePriority(prefer rulePriorityPrefer) (int32, error) {

We need to make the above behaviors the same. Max priority 4096 should/shoult not be counted in as the managed range.

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

Kubernetes version (use kubectl version):
Cloud provider or hardware configuration:
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Network plugin and version (if this is a network-related bug):
Others:

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

Navigation Menu

Repository navigation

Align max managed security priority behavior #9906

What happened:

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Align max managed security priority behavior #9906

Description

What happened:

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

Activity

k8s-triage-robot commented on May 5, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions