apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T16:13:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-101-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-101.ec2.internal
      uid: df4cf0b6-1b4d-466a-91d6-747f09cc584e
    resourceVersion: "23319"
    uid: 66a3f201-ab29-4e86-bc19-1d6067ca17e6
  spec:
    sourcePod: network-check-source-56499946bc-qrpgx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T16:20:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 981.91µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:20:27Z"
    - latency: 1.20709ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:19:27Z"
    - latency: 1.445074ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:18:27Z"
    - latency: 907.337µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:17:27Z"
    - latency: 1.032128ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:16:27Z"
    - latency: 1.164045ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:15:27Z"
    - latency: 873.145µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:14:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T16:13:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-101-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-101.ec2.internal
      uid: df4cf0b6-1b4d-466a-91d6-747f09cc584e
    resourceVersion: "22307"
    uid: 7a2a51b2-3e9b-4811-87cc-d077d2a1e279
  spec:
    sourcePod: network-check-source-56499946bc-qrpgx
    targetEndpoint: a32d3f6209d164d1fbe05e635a9724d9-d71158d9dd27778e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T16:19:27Z"
      message: 'load-balancer-api-external: tcp connection to a32d3f6209d164d1fbe05e635a9724d9-d71158d9dd27778e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.340701ms
      message: 'load-balancer-api-external: tcp connection to a32d3f6209d164d1fbe05e635a9724d9-d71158d9dd27778e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:19:27Z"
    - latency: 13.25052ms
      message: 'load-balancer-api-external: resolved host name a32d3f6209d164d1fbe05e635a9724d9-d71158d9dd27778e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:19:27Z"
    - latency: 4.573095ms
      message: 'load-balancer-api-external: tcp connection to a32d3f6209d164d1fbe05e635a9724d9-d71158d9dd27778e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:18:27Z"
    - latency: 13.582073ms
      message: 'load-balancer-api-external: resolved host name a32d3f6209d164d1fbe05e635a9724d9-d71158d9dd27778e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:18:27Z"
    - latency: 5.744784ms
      message: 'load-balancer-api-external: tcp connection to a32d3f6209d164d1fbe05e635a9724d9-d71158d9dd27778e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:17:27Z"
    - latency: 10.575416ms
      message: 'load-balancer-api-external: resolved host name a32d3f6209d164d1fbe05e635a9724d9-d71158d9dd27778e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:17:27Z"
    - latency: 5.696572ms
      message: 'load-balancer-api-external: tcp connection to a32d3f6209d164d1fbe05e635a9724d9-d71158d9dd27778e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:16:27Z"
    - latency: 10.710565ms
      message: 'load-balancer-api-external: resolved host name a32d3f6209d164d1fbe05e635a9724d9-d71158d9dd27778e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:16:27Z"
    - latency: 4.720314ms
      message: 'load-balancer-api-external: tcp connection to a32d3f6209d164d1fbe05e635a9724d9-d71158d9dd27778e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:15:27Z"
    - latency: 9.664224ms
      message: 'load-balancer-api-external: resolved host name a32d3f6209d164d1fbe05e635a9724d9-d71158d9dd27778e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:15:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T16:13:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-101-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-101.ec2.internal
      uid: df4cf0b6-1b4d-466a-91d6-747f09cc584e
    resourceVersion: "22308"
    uid: 2a5995fb-fba4-4bbd-868a-757dca87554f
  spec:
    sourcePod: network-check-source-56499946bc-qrpgx
    targetEndpoint: a32d3f6209d164d1fbe05e635a9724d9-d71158d9dd27778e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T16:19:27Z"
      message: 'load-balancer-api-internal: tcp connection to a32d3f6209d164d1fbe05e635a9724d9-d71158d9dd27778e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.750935ms
      message: 'load-balancer-api-internal: tcp connection to a32d3f6209d164d1fbe05e635a9724d9-d71158d9dd27778e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:19:27Z"
    - latency: 13.302703ms
      message: 'load-balancer-api-internal: resolved host name a32d3f6209d164d1fbe05e635a9724d9-d71158d9dd27778e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:19:27Z"
    - latency: 4.048769ms
      message: 'load-balancer-api-internal: tcp connection to a32d3f6209d164d1fbe05e635a9724d9-d71158d9dd27778e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:18:27Z"
    - latency: 13.506063ms
      message: 'load-balancer-api-internal: resolved host name a32d3f6209d164d1fbe05e635a9724d9-d71158d9dd27778e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:18:27Z"
    - latency: 6.072744ms
      message: 'load-balancer-api-internal: tcp connection to a32d3f6209d164d1fbe05e635a9724d9-d71158d9dd27778e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:17:27Z"
    - latency: 10.444397ms
      message: 'load-balancer-api-internal: resolved host name a32d3f6209d164d1fbe05e635a9724d9-d71158d9dd27778e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:17:27Z"
    - latency: 5.442525ms
      message: 'load-balancer-api-internal: tcp connection to a32d3f6209d164d1fbe05e635a9724d9-d71158d9dd27778e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:16:27Z"
    - latency: 10.637639ms
      message: 'load-balancer-api-internal: resolved host name a32d3f6209d164d1fbe05e635a9724d9-d71158d9dd27778e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:16:27Z"
    - latency: 10.529683ms
      message: 'load-balancer-api-internal: tcp connection to a32d3f6209d164d1fbe05e635a9724d9-d71158d9dd27778e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:15:27Z"
    - latency: 8.842823ms
      message: 'load-balancer-api-internal: resolved host name a32d3f6209d164d1fbe05e635a9724d9-d71158d9dd27778e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:15:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T16:13:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-101-to-network-check-target-ip-10-0-130-217
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-101.ec2.internal
      uid: df4cf0b6-1b4d-466a-91d6-747f09cc584e
    resourceVersion: "23317"
    uid: 25d5f760-c88e-42b4-a5df-d6806f4266ec
  spec:
    sourcePod: network-check-source-56499946bc-qrpgx
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T16:20:27Z"
      message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.092665ms
      message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:20:27Z"
    - latency: 2.175924ms
      message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:19:27Z"
    - latency: 2.427472ms
      message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:18:27Z"
    - latency: 2.107859ms
      message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:17:27Z"
    - latency: 2.517843ms
      message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:16:27Z"
    - latency: 2.635297ms
      message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:15:27Z"
    - latency: 2.604518ms
      message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:14:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T16:13:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-101-to-network-check-target-ip-10-0-136-120
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-101.ec2.internal
      uid: df4cf0b6-1b4d-466a-91d6-747f09cc584e
    resourceVersion: "23318"
    uid: 9e47697a-6c0d-44cb-84ac-34e819cc769f
  spec:
    sourcePod: network-check-source-56499946bc-qrpgx
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T16:20:27Z"
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.868433ms
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:20:27Z"
    - latency: 2.285948ms
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:19:27Z"
    - latency: 2.264505ms
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:18:27Z"
    - latency: 1.7297ms
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:17:27Z"
    - latency: 1.921027ms
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:16:27Z"
    - latency: 2.175475ms
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:15:27Z"
    - latency: 2.331356ms
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:14:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T16:13:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-101-to-network-check-target-ip-10-0-140-101
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-101.ec2.internal
      uid: df4cf0b6-1b4d-466a-91d6-747f09cc584e
    resourceVersion: "23316"
    uid: 9897f5f5-79ef-4688-91eb-638f4382346c
  spec:
    sourcePod: network-check-source-56499946bc-qrpgx
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T16:20:27Z"
      message: 'network-check-target-ip-10-0-140-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 911.806µs
      message: 'network-check-target-ip-10-0-140-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:20:27Z"
    - latency: 926.982µs
      message: 'network-check-target-ip-10-0-140-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:19:27Z"
    - latency: 1.015723ms
      message: 'network-check-target-ip-10-0-140-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:18:27Z"
    - latency: 915.959µs
      message: 'network-check-target-ip-10-0-140-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:17:27Z"
    - latency: 1.221313ms
      message: 'network-check-target-ip-10-0-140-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:16:27Z"
    - latency: 1.158761ms
      message: 'network-check-target-ip-10-0-140-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:15:27Z"
    - latency: 2.236528ms
      message: 'network-check-target-ip-10-0-140-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:14:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T16:13:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-101-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-101.ec2.internal
      uid: df4cf0b6-1b4d-466a-91d6-747f09cc584e
    resourceVersion: "22306"
    uid: a0ed089e-4f97-4a02-bd6f-5c110d00b977
  spec:
    sourcePod: network-check-source-56499946bc-qrpgx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T16:19:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.055595ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:19:27Z"
    - latency: 1.841703ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:19:27Z"
    - latency: 1.356704ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:18:27Z"
    - latency: 2.369401ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:18:27Z"
    - latency: 882.924µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:17:27Z"
    - latency: 1.624565ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:17:27Z"
    - latency: 1.276186ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:16:27Z"
    - latency: 2.315802ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:16:27Z"
    - latency: 994.336µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:15:27Z"
    - latency: 2.311008ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:15:27Z"
kind: List
metadata:
  resourceVersion: ""