apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T21:42:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-61-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-61.ec2.internal
      uid: a8e616be-3cbc-4068-9c44-710598b3b3d7
    resourceVersion: "22937"
    uid: 2430f9d2-95a2-449f-bb9f-96f656356c43
  spec:
    sourcePod: network-check-source-56d84b9f44-k7m6k
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T21:50:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.196277ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:50:00Z"
    - latency: 2.383367ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:49:00Z"
    - latency: 1.36051ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:48:00Z"
    - latency: 1.082377ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:47:00Z"
    - latency: 1.022299ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:46:00Z"
    - latency: 1.087441ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:45:00Z"
    - latency: 957.107µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:44:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T21:42:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-61-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-61.ec2.internal
      uid: a8e616be-3cbc-4068-9c44-710598b3b3d7
    resourceVersion: "28217"
    uid: 217317b3-f142-46e9-8137-eea046c7266b
  spec:
    sourcePod: network-check-source-56d84b9f44-k7m6k
    targetEndpoint: ae7b30179235449378614702fc1f7766-3a700961480ca053.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T21:49:00Z"
      message: 'load-balancer-api-external: tcp connection to ae7b30179235449378614702fc1f7766-3a700961480ca053.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.598581ms
      message: 'load-balancer-api-external: tcp connection to ae7b30179235449378614702fc1f7766-3a700961480ca053.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:55:00Z"
    - latency: 7.321433ms
      message: 'load-balancer-api-external: resolved host name ae7b30179235449378614702fc1f7766-3a700961480ca053.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T21:55:00Z"
    - latency: 5.047324ms
      message: 'load-balancer-api-external: tcp connection to ae7b30179235449378614702fc1f7766-3a700961480ca053.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:54:00Z"
    - latency: 8.636429ms
      message: 'load-balancer-api-external: resolved host name ae7b30179235449378614702fc1f7766-3a700961480ca053.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T21:54:00Z"
    - latency: 4.390201ms
      message: 'load-balancer-api-external: tcp connection to ae7b30179235449378614702fc1f7766-3a700961480ca053.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:53:00Z"
    - latency: 8.132937ms
      message: 'load-balancer-api-external: resolved host name ae7b30179235449378614702fc1f7766-3a700961480ca053.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T21:53:00Z"
    - latency: 4.768587ms
      message: 'load-balancer-api-external: tcp connection to ae7b30179235449378614702fc1f7766-3a700961480ca053.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:52:00Z"
    - latency: 7.765244ms
      message: 'load-balancer-api-external: resolved host name ae7b30179235449378614702fc1f7766-3a700961480ca053.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T21:52:00Z"
    - latency: 3.461022ms
      message: 'load-balancer-api-external: tcp connection to ae7b30179235449378614702fc1f7766-3a700961480ca053.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:51:00Z"
    - latency: 9.821027ms
      message: 'load-balancer-api-external: resolved host name ae7b30179235449378614702fc1f7766-3a700961480ca053.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T21:51:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T21:42:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-61-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-61.ec2.internal
      uid: a8e616be-3cbc-4068-9c44-710598b3b3d7
    resourceVersion: "28218"
    uid: fc8408b8-3eaa-4714-bbf9-184ca88340d0
  spec:
    sourcePod: network-check-source-56d84b9f44-k7m6k
    targetEndpoint: ae7b30179235449378614702fc1f7766-3a700961480ca053.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T21:49:00Z"
      message: 'load-balancer-api-internal: tcp connection to ae7b30179235449378614702fc1f7766-3a700961480ca053.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.453623ms
      message: 'load-balancer-api-internal: tcp connection to ae7b30179235449378614702fc1f7766-3a700961480ca053.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:55:00Z"
    - latency: 7.34763ms
      message: 'load-balancer-api-internal: resolved host name ae7b30179235449378614702fc1f7766-3a700961480ca053.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T21:55:00Z"
    - latency: 5.019375ms
      message: 'load-balancer-api-internal: tcp connection to ae7b30179235449378614702fc1f7766-3a700961480ca053.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:54:00Z"
    - latency: 8.70183ms
      message: 'load-balancer-api-internal: resolved host name ae7b30179235449378614702fc1f7766-3a700961480ca053.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T21:54:00Z"
    - latency: 3.835888ms
      message: 'load-balancer-api-internal: tcp connection to ae7b30179235449378614702fc1f7766-3a700961480ca053.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:53:00Z"
    - latency: 8.175169ms
      message: 'load-balancer-api-internal: resolved host name ae7b30179235449378614702fc1f7766-3a700961480ca053.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T21:53:00Z"
    - latency: 4.31981ms
      message: 'load-balancer-api-internal: tcp connection to ae7b30179235449378614702fc1f7766-3a700961480ca053.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:52:00Z"
    - latency: 7.780676ms
      message: 'load-balancer-api-internal: resolved host name ae7b30179235449378614702fc1f7766-3a700961480ca053.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T21:52:00Z"
    - latency: 3.479307ms
      message: 'load-balancer-api-internal: tcp connection to ae7b30179235449378614702fc1f7766-3a700961480ca053.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:51:00Z"
    - latency: 9.870792ms
      message: 'load-balancer-api-internal: resolved host name ae7b30179235449378614702fc1f7766-3a700961480ca053.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T21:51:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T21:42:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-61-to-network-check-target-ip-10-0-131-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-61.ec2.internal
      uid: a8e616be-3cbc-4068-9c44-710598b3b3d7
    resourceVersion: "22935"
    uid: 94f84e28-6e26-4a72-94b0-398aaa6fedf8
  spec:
    sourcePod: network-check-source-56d84b9f44-k7m6k
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T21:50:00Z"
      message: 'network-check-target-ip-10-0-131-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.785891ms
      message: 'network-check-target-ip-10-0-131-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:50:00Z"
    - latency: 2.170329ms
      message: 'network-check-target-ip-10-0-131-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:49:00Z"
    - latency: 1.899266ms
      message: 'network-check-target-ip-10-0-131-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:48:00Z"
    - latency: 1.950303ms
      message: 'network-check-target-ip-10-0-131-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:47:00Z"
    - latency: 1.732603ms
      message: 'network-check-target-ip-10-0-131-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:46:00Z"
    - latency: 1.731182ms
      message: 'network-check-target-ip-10-0-131-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:45:00Z"
    - latency: 1.880225ms
      message: 'network-check-target-ip-10-0-131-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:44:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T21:42:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-61-to-network-check-target-ip-10-0-135-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-61.ec2.internal
      uid: a8e616be-3cbc-4068-9c44-710598b3b3d7
    resourceVersion: "22936"
    uid: 45e4be74-5b03-48e1-a885-74cba990f5d5
  spec:
    sourcePod: network-check-source-56d84b9f44-k7m6k
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T21:50:00Z"
      message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.184964ms
      message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:50:00Z"
    - latency: 3.092755ms
      message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:49:00Z"
    - latency: 2.029108ms
      message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:48:00Z"
    - latency: 2.254162ms
      message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:47:00Z"
    - latency: 2.037753ms
      message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:46:00Z"
    - latency: 2.061463ms
      message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:45:00Z"
    - latency: 3.090932ms
      message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:44:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T21:42:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-61-to-network-check-target-ip-10-0-143-61
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-61.ec2.internal
      uid: a8e616be-3cbc-4068-9c44-710598b3b3d7
    resourceVersion: "22934"
    uid: aff03603-3b04-452b-886a-56d2436e2508
  spec:
    sourcePod: network-check-source-56d84b9f44-k7m6k
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T21:50:00Z"
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.309817ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:50:00Z"
    - latency: 3.753573ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:49:00Z"
    - latency: 1.78118ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:48:00Z"
    - latency: 1.787814ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:47:00Z"
    - latency: 1.441264ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:46:00Z"
    - latency: 1.372073ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:45:00Z"
    - latency: 1.136415ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:44:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T21:42:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-61-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-61.ec2.internal
      uid: a8e616be-3cbc-4068-9c44-710598b3b3d7
    resourceVersion: "28216"
    uid: cb787831-7684-495f-8ead-d998298c9b02
  spec:
    sourcePod: network-check-source-56d84b9f44-k7m6k
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T21:49:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 834.003µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:55:00Z"
    - latency: 1.81394ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T21:55:00Z"
    - latency: 960.649µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:54:00Z"
    - latency: 1.88848ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T21:54:00Z"
    - latency: 1.182391ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:53:00Z"
    - latency: 1.886835ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T21:53:00Z"
    - latency: 906.495µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:52:00Z"
    - latency: 2.020706ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T21:52:00Z"
    - latency: 1.274975ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T21:51:00Z"
    - latency: 1.919801ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T21:51:00Z"
kind: List
metadata:
  resourceVersion: ""