apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T18:14:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-42-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-42.ec2.internal
      uid: d1000360-a38c-417f-84b2-af08be2abf08
    resourceVersion: "24964"
    uid: e1b37e5a-a994-4227-af4d-1a6ced418ad3
  spec:
    sourcePod: network-check-source-dbd9cf844-xrqhl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T18:21:15Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 975.017µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:21:15Z"
    - latency: 1.197237ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:20:15Z"
    - latency: 1.778949ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:19:15Z"
    - latency: 1.5108ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:18:15Z"
    - latency: 843.964µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:17:15Z"
    - latency: 834.901µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:16:15Z"
    - latency: 1.113652ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:15:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T18:14:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-42-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-42.ec2.internal
      uid: d1000360-a38c-417f-84b2-af08be2abf08
    resourceVersion: "29166"
    uid: 03cafe55-0c0c-463d-bc56-c95ec3eb17ee
  spec:
    sourcePod: network-check-source-dbd9cf844-xrqhl
    targetEndpoint: a0013a701af114073a9f6287212f76a5-6abf1303afa66ce5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T18:20:15Z"
      message: 'load-balancer-api-external: tcp connection to a0013a701af114073a9f6287212f76a5-6abf1303afa66ce5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.419726ms
      message: 'load-balancer-api-external: tcp connection to a0013a701af114073a9f6287212f76a5-6abf1303afa66ce5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:26:15Z"
    - latency: 8.467729ms
      message: 'load-balancer-api-external: resolved host name a0013a701af114073a9f6287212f76a5-6abf1303afa66ce5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:26:15Z"
    - latency: 5.580445ms
      message: 'load-balancer-api-external: tcp connection to a0013a701af114073a9f6287212f76a5-6abf1303afa66ce5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:25:15Z"
    - latency: 7.385174ms
      message: 'load-balancer-api-external: resolved host name a0013a701af114073a9f6287212f76a5-6abf1303afa66ce5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:25:15Z"
    - latency: 6.140273ms
      message: 'load-balancer-api-external: tcp connection to a0013a701af114073a9f6287212f76a5-6abf1303afa66ce5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:24:15Z"
    - latency: 8.581017ms
      message: 'load-balancer-api-external: resolved host name a0013a701af114073a9f6287212f76a5-6abf1303afa66ce5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:24:15Z"
    - latency: 6.877411ms
      message: 'load-balancer-api-external: tcp connection to a0013a701af114073a9f6287212f76a5-6abf1303afa66ce5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:23:15Z"
    - latency: 8.109141ms
      message: 'load-balancer-api-external: resolved host name a0013a701af114073a9f6287212f76a5-6abf1303afa66ce5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:23:15Z"
    - latency: 5.066505ms
      message: 'load-balancer-api-external: tcp connection to a0013a701af114073a9f6287212f76a5-6abf1303afa66ce5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:22:15Z"
    - latency: 8.96964ms
      message: 'load-balancer-api-external: resolved host name a0013a701af114073a9f6287212f76a5-6abf1303afa66ce5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:22:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T18:14:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-42-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-42.ec2.internal
      uid: d1000360-a38c-417f-84b2-af08be2abf08
    resourceVersion: "29167"
    uid: 22f04c63-7c06-4c39-ba4a-7124c5503e28
  spec:
    sourcePod: network-check-source-dbd9cf844-xrqhl
    targetEndpoint: a0013a701af114073a9f6287212f76a5-6abf1303afa66ce5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T18:20:15Z"
      message: 'load-balancer-api-internal: tcp connection to a0013a701af114073a9f6287212f76a5-6abf1303afa66ce5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.403844ms
      message: 'load-balancer-api-internal: tcp connection to a0013a701af114073a9f6287212f76a5-6abf1303afa66ce5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:26:15Z"
    - latency: 8.541477ms
      message: 'load-balancer-api-internal: resolved host name a0013a701af114073a9f6287212f76a5-6abf1303afa66ce5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:26:15Z"
    - latency: 5.627744ms
      message: 'load-balancer-api-internal: tcp connection to a0013a701af114073a9f6287212f76a5-6abf1303afa66ce5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:25:15Z"
    - latency: 7.186034ms
      message: 'load-balancer-api-internal: resolved host name a0013a701af114073a9f6287212f76a5-6abf1303afa66ce5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:25:15Z"
    - latency: 6.172547ms
      message: 'load-balancer-api-internal: tcp connection to a0013a701af114073a9f6287212f76a5-6abf1303afa66ce5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:24:15Z"
    - latency: 8.488914ms
      message: 'load-balancer-api-internal: resolved host name a0013a701af114073a9f6287212f76a5-6abf1303afa66ce5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:24:15Z"
    - latency: 6.015926ms
      message: 'load-balancer-api-internal: tcp connection to a0013a701af114073a9f6287212f76a5-6abf1303afa66ce5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:23:15Z"
    - latency: 8.024444ms
      message: 'load-balancer-api-internal: resolved host name a0013a701af114073a9f6287212f76a5-6abf1303afa66ce5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:23:15Z"
    - latency: 4.915094ms
      message: 'load-balancer-api-internal: tcp connection to a0013a701af114073a9f6287212f76a5-6abf1303afa66ce5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:22:15Z"
    - latency: 8.909264ms
      message: 'load-balancer-api-internal: resolved host name a0013a701af114073a9f6287212f76a5-6abf1303afa66ce5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:22:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T18:14:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-42-to-network-check-target-ip-10-0-129-42
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-42.ec2.internal
      uid: d1000360-a38c-417f-84b2-af08be2abf08
    resourceVersion: "24961"
    uid: 6294973d-98d3-469f-bf75-965f1751eb2e
  spec:
    sourcePod: network-check-source-dbd9cf844-xrqhl
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T18:21:15Z"
      message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 909.319µs
      message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:21:15Z"
    - latency: 1.134566ms
      message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:20:15Z"
    - latency: 2.450027ms
      message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:19:15Z"
    - latency: 1.95468ms
      message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:18:15Z"
    - latency: 1.008301ms
      message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:17:15Z"
    - latency: 885.601µs
      message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:16:15Z"
    - latency: 1.671992ms
      message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:15:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T18:14:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-42-to-network-check-target-ip-10-0-140-216
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-42.ec2.internal
      uid: d1000360-a38c-417f-84b2-af08be2abf08
    resourceVersion: "24963"
    uid: 61da0438-bea7-4d3f-bdfa-32fdd0c79890
  spec:
    sourcePod: network-check-source-dbd9cf844-xrqhl
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T18:21:15Z"
      message: 'network-check-target-ip-10-0-140-216: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.749895ms
      message: 'network-check-target-ip-10-0-140-216: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:21:15Z"
    - latency: 2.418112ms
      message: 'network-check-target-ip-10-0-140-216: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:20:15Z"
    - latency: 2.951845ms
      message: 'network-check-target-ip-10-0-140-216: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:19:15Z"
    - latency: 2.949395ms
      message: 'network-check-target-ip-10-0-140-216: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:18:15Z"
    - latency: 2.171564ms
      message: 'network-check-target-ip-10-0-140-216: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:17:15Z"
    - latency: 1.869506ms
      message: 'network-check-target-ip-10-0-140-216: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:16:15Z"
    - latency: 2.318681ms
      message: 'network-check-target-ip-10-0-140-216: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:15:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T18:14:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-42-to-network-check-target-ip-10-0-143-75
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-42.ec2.internal
      uid: d1000360-a38c-417f-84b2-af08be2abf08
    resourceVersion: "24962"
    uid: fe4c0268-07cc-4c7f-8cab-c51949c41b8f
  spec:
    sourcePod: network-check-source-dbd9cf844-xrqhl
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T18:21:15Z"
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.397625ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:21:15Z"
    - latency: 2.879889ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:20:15Z"
    - latency: 3.385203ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:19:15Z"
    - latency: 2.640221ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:18:15Z"
    - latency: 2.237391ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:17:15Z"
    - latency: 1.839321ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:16:15Z"
    - latency: 2.430465ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:15:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T18:14:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-42-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-42.ec2.internal
      uid: d1000360-a38c-417f-84b2-af08be2abf08
    resourceVersion: "29165"
    uid: 76f9ecb9-9fd8-489f-87e6-7d7bb9625797
  spec:
    sourcePod: network-check-source-dbd9cf844-xrqhl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T18:20:15Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 938.158µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:26:15Z"
    - latency: 1.866969ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:26:15Z"
    - latency: 860.778µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:25:15Z"
    - latency: 1.759249ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:25:15Z"
    - latency: 733.452µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:24:15Z"
    - latency: 1.714837ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:24:15Z"
    - latency: 772.034µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:23:15Z"
    - latency: 1.67479ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:23:15Z"
    - latency: 1.093819ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:22:15Z"
    - latency: 1.826572ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:22:15Z"
kind: List
metadata:
  resourceVersion: ""