apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T12:42:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-139-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-139.ec2.internal
      uid: 167e9f21-ba92-4f5f-ae88-2a57e3cdd506
    resourceVersion: "14190"
    uid: f5b84b55-1571-4d95-9cf1-fba868968d5a
  spec:
    sourcePod: network-check-source-56d84b9f44-kzh6j
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T12:49:16Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 871.358µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:49:16Z"
    - latency: 968.978µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:48:16Z"
    - latency: 926.463µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:47:16Z"
    - latency: 966.84µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:46:16Z"
    - latency: 915.333µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:45:16Z"
    - latency: 809.62µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:44:16Z"
    - latency: 1.262151ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:43:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T12:42:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-139-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-139.ec2.internal
      uid: 167e9f21-ba92-4f5f-ae88-2a57e3cdd506
    resourceVersion: "13864"
    uid: 982a6b93-c376-4502-b401-3ab8a7289256
  spec:
    sourcePod: network-check-source-56d84b9f44-kzh6j
    targetEndpoint: a6f6414335e1546049158707b97289b7-ccf2e582013ca76a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T12:48:16Z"
      message: 'load-balancer-api-external: tcp connection to a6f6414335e1546049158707b97289b7-ccf2e582013ca76a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.669322ms
      message: 'load-balancer-api-external: tcp connection to a6f6414335e1546049158707b97289b7-ccf2e582013ca76a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:48:16Z"
    - latency: 8.222356ms
      message: 'load-balancer-api-external: resolved host name a6f6414335e1546049158707b97289b7-ccf2e582013ca76a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T12:48:16Z"
    - latency: 5.208097ms
      message: 'load-balancer-api-external: tcp connection to a6f6414335e1546049158707b97289b7-ccf2e582013ca76a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:47:16Z"
    - latency: 8.93601ms
      message: 'load-balancer-api-external: resolved host name a6f6414335e1546049158707b97289b7-ccf2e582013ca76a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T12:47:16Z"
    - latency: 5.335546ms
      message: 'load-balancer-api-external: tcp connection to a6f6414335e1546049158707b97289b7-ccf2e582013ca76a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:46:16Z"
    - latency: 6.065789ms
      message: 'load-balancer-api-external: resolved host name a6f6414335e1546049158707b97289b7-ccf2e582013ca76a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T12:46:16Z"
    - latency: 4.985863ms
      message: 'load-balancer-api-external: tcp connection to a6f6414335e1546049158707b97289b7-ccf2e582013ca76a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:45:16Z"
    - latency: 8.01609ms
      message: 'load-balancer-api-external: resolved host name a6f6414335e1546049158707b97289b7-ccf2e582013ca76a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T12:45:16Z"
    - latency: 4.812275ms
      message: 'load-balancer-api-external: tcp connection to a6f6414335e1546049158707b97289b7-ccf2e582013ca76a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:44:16Z"
    - latency: 7.608794ms
      message: 'load-balancer-api-external: resolved host name a6f6414335e1546049158707b97289b7-ccf2e582013ca76a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T12:44:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T12:42:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-139-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-139.ec2.internal
      uid: 167e9f21-ba92-4f5f-ae88-2a57e3cdd506
    resourceVersion: "13863"
    uid: 39180263-1672-442a-a907-15666e9ea9ad
  spec:
    sourcePod: network-check-source-56d84b9f44-kzh6j
    targetEndpoint: a6f6414335e1546049158707b97289b7-ccf2e582013ca76a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T12:48:16Z"
      message: 'load-balancer-api-internal: tcp connection to a6f6414335e1546049158707b97289b7-ccf2e582013ca76a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.707605ms
      message: 'load-balancer-api-internal: tcp connection to a6f6414335e1546049158707b97289b7-ccf2e582013ca76a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:48:16Z"
    - latency: 8.170395ms
      message: 'load-balancer-api-internal: resolved host name a6f6414335e1546049158707b97289b7-ccf2e582013ca76a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T12:48:16Z"
    - latency: 5.22934ms
      message: 'load-balancer-api-internal: tcp connection to a6f6414335e1546049158707b97289b7-ccf2e582013ca76a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:47:16Z"
    - latency: 9.002611ms
      message: 'load-balancer-api-internal: resolved host name a6f6414335e1546049158707b97289b7-ccf2e582013ca76a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T12:47:16Z"
    - latency: 5.359332ms
      message: 'load-balancer-api-internal: tcp connection to a6f6414335e1546049158707b97289b7-ccf2e582013ca76a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:46:16Z"
    - latency: 6.098062ms
      message: 'load-balancer-api-internal: resolved host name a6f6414335e1546049158707b97289b7-ccf2e582013ca76a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T12:46:16Z"
    - latency: 4.99673ms
      message: 'load-balancer-api-internal: tcp connection to a6f6414335e1546049158707b97289b7-ccf2e582013ca76a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:45:16Z"
    - latency: 7.964683ms
      message: 'load-balancer-api-internal: resolved host name a6f6414335e1546049158707b97289b7-ccf2e582013ca76a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T12:45:16Z"
    - latency: 4.902886ms
      message: 'load-balancer-api-internal: tcp connection to a6f6414335e1546049158707b97289b7-ccf2e582013ca76a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:44:16Z"
    - latency: 7.68911ms
      message: 'load-balancer-api-internal: resolved host name a6f6414335e1546049158707b97289b7-ccf2e582013ca76a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T12:44:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T12:42:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-139-to-network-check-target-ip-10-0-128-229
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-139.ec2.internal
      uid: 167e9f21-ba92-4f5f-ae88-2a57e3cdd506
    resourceVersion: "14188"
    uid: a53338a5-f8d6-4b4b-a31a-4635b2e3e44b
  spec:
    sourcePod: network-check-source-56d84b9f44-kzh6j
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T12:49:16Z"
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.302363ms
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:49:16Z"
    - latency: 2.22674ms
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:48:16Z"
    - latency: 2.481668ms
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:47:16Z"
    - latency: 1.975132ms
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:46:16Z"
    - latency: 2.043598ms
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:45:16Z"
    - latency: 2.234351ms
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:44:16Z"
    - latency: 2.359408ms
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:43:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T12:42:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-139-to-network-check-target-ip-10-0-137-239
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-139.ec2.internal
      uid: 167e9f21-ba92-4f5f-ae88-2a57e3cdd506
    resourceVersion: "14189"
    uid: 9e1e07f8-64cd-43c3-a4a9-a3656d70214e
  spec:
    sourcePod: network-check-source-56d84b9f44-kzh6j
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T12:49:16Z"
      message: 'network-check-target-ip-10-0-137-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.399091ms
      message: 'network-check-target-ip-10-0-137-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:49:16Z"
    - latency: 2.095185ms
      message: 'network-check-target-ip-10-0-137-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:48:16Z"
    - latency: 2.138683ms
      message: 'network-check-target-ip-10-0-137-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:47:16Z"
    - latency: 2.133434ms
      message: 'network-check-target-ip-10-0-137-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:46:16Z"
    - latency: 2.117077ms
      message: 'network-check-target-ip-10-0-137-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:45:16Z"
    - latency: 2.142674ms
      message: 'network-check-target-ip-10-0-137-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:44:16Z"
    - latency: 2.364755ms
      message: 'network-check-target-ip-10-0-137-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:43:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T12:42:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-139-to-network-check-target-ip-10-0-143-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-139.ec2.internal
      uid: 167e9f21-ba92-4f5f-ae88-2a57e3cdd506
    resourceVersion: "14187"
    uid: 147ac125-6e48-4f34-8496-f4617e57795a
  spec:
    sourcePod: network-check-source-56d84b9f44-kzh6j
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T12:49:16Z"
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 878.012µs
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:49:16Z"
    - latency: 901.463µs
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:48:16Z"
    - latency: 860.228µs
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:47:16Z"
    - latency: 948.777µs
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:46:16Z"
    - latency: 846.504µs
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:45:16Z"
    - latency: 823.862µs
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:44:16Z"
    - latency: 1.756046ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:43:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T12:42:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-139-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-139.ec2.internal
      uid: 167e9f21-ba92-4f5f-ae88-2a57e3cdd506
    resourceVersion: "13862"
    uid: 8f0196a6-0155-4a0b-91df-edd2a7780900
  spec:
    sourcePod: network-check-source-56d84b9f44-kzh6j
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T12:48:16Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 843.791µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:48:16Z"
    - latency: 1.749362ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T12:48:16Z"
    - latency: 970.358µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:47:16Z"
    - latency: 2.119005ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T12:47:16Z"
    - latency: 807.867µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:46:16Z"
    - latency: 1.710672ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T12:46:16Z"
    - latency: 825.421µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:45:16Z"
    - latency: 1.598416ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T12:45:16Z"
    - latency: 988.107µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T12:44:16Z"
    - latency: 1.542992ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T12:44:16Z"
kind: List
metadata:
  resourceVersion: ""