Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Antrea-native policies stayed in realizing status in some cases #5097

Closed
tnqn opened this issue Jun 7, 2023 · 0 comments · Fixed by #5096
Closed

Antrea-native policies stayed in realizing status in some cases #5097

tnqn opened this issue Jun 7, 2023 · 0 comments · Fixed by #5096
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@tnqn
Copy link
Member

tnqn commented Jun 7, 2023

Describe the bug

When no-op changes are applied to Antrea-native policies, such as adding or removing a non-existing group, there will be no datapath change but the generation has changed.

status:
  currentNodesRealized: 1
  desiredNodesRealized: 2
  observedGeneration: 4
  phase: Realizing

To Reproduce

  1. Create the following policy:
apiVersion: crd.antrea.io/v1alpha1
kind: NetworkPolicy
metadata:
  name: allow-client-to-server
spec:
  priority: 1
  ingress:
    - action: Drop
      appliedTo:
      - podSelector: {}
      - group: abc # non-existing group
      name: abc
  1. Then apply the following one which removes the group from appliedTo:
apiVersion: crd.antrea.io/v1alpha1
kind: NetworkPolicy
metadata:
  name: allow-client-to-server
spec:
  priority: 1
  ingress:
    - action: Drop
      appliedTo:
      - podSelector: {}
      name: abc
  1. The policy will stay in "realizing"

Versions:

  • Antrea version (Docker image tag). ~v1.12.0
@tnqn tnqn added the kind/bug Categorizes issue or PR as related to a bug. label Jun 7, 2023
@tnqn tnqn closed this as completed in #5096 Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant