Skip to content

Align max managed security priority behavior #9906

@nilo19

Description

@nilo19

What happened:

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

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:

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions