if chain != nil {
		sort.SliceStable(chain.Rules, func(i, j int) bool {
			return orderByCommentServiceName(chain.Rules[i], chain.Rules[j])
		})
	}
	chain, _ = dump.GetChain(utiliptables.TableNAT, kubeNodePortsChain)
	if chain != nil {
		sort.SliceStable(chain.Rules, func(i, j int) bool {
			return orderByCommentServiceName(chain.Rules[i], chain.Rules[j])
		})
	}

protected void before() throws Throwable; protected void after(); } org/junit/rules/Stopwatch$1.class package org.junit.rules; synchronized class Stopwatch$1 { } org/junit/rules/Timeout$1.class package org.junit.rules; synchronized class Timeout$1 extends org.junit.runners.model.Statement { void Timeout$1(Timeout, Exception); public void evaluate() throws Throwable; } org/junit/rules/TestName.class package org.junit.rules; public synchronized class TestName extends TestWatcher { private volatile String...

                  to what Ingress and Egress rules are present in the policy.  The
                  default is: \n - [ PolicyTypeIngress ], if there are no Egress rules
                  (including the case where there are   also no Ingress rules) \n
                  - [ PolicyTypeEgress ], if there are Egress rules but no Ingress
                  rules \n - [ PolicyTypeIngress, PolicyTypeEgress ], if there are

                        For example, foo/bar is given precedence over foo/baz. \n
                        All valid rules within a Route attached to this Listener should
                        be implemented. Invalid Route rules can be ignored (sometimes
                        that will mean the full Route). If a Route rule transitions

        "properties": {
          "excludeResourceRules": {
            "description": "ExcludeResourceRules describes what operations on what resources/subresources the ValidatingAdmissionPolicy should not care about. The exclude rules take precedence over include rules (if a resource matches both, it is excluded)",

<h3 id="Type_unification_rules">Type unification rules</h3>

<p>
The type unification rules describe if and how two types unify.
The precise details are relevant for Go implementations,
affect the specifics of error messages (such as whether
a compiler reports a type inference or other error),
and may explain why type inference fails in unusual code situations.
But by and large these rules can be ignored when writing Go code:

*   Azure NSG rules are now restricted so that external access is allowed only to the load balancer IP. ([#54177](https://github.com/kubernetes/kubernetes/pull/54177),[ @itowlson](https://github.com/itowlson))

            "type": "string"
          },
          "rules": {
            "description": "rules is a list of host rules used to configure the Ingress. If unspecified, or no rule matches, all traffic is sent to the default backend.",
            "items": {
              "allOf": [
                {

        "properties": {
          "rules": {

- In "large" clusters, kube-proxy in iptables mode will now sometimes
  leave unused rules in iptables for a while (up to `--iptables-sync-period`)
  before deleting them. This improves performance by not requiring it to
  check for stale rules on every sync. (In smaller clusters, it will still
  remove unused rules immediately once they are no longer used.)