apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T13:52:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-92-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-92.ec2.internal
      uid: 86110797-5905-4f92-9230-c2eee26ac223
    resourceVersion: "22826"
    uid: a42f8898-10b3-4caa-8d27-3643f624e13a
  spec:
    sourcePod: network-check-source-989f8b8dc-shl9d
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T13:59:53Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.502317ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:59:53Z"
    - latency: 1.321775ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:58:53Z"
    - latency: 2.103909ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:57:53Z"
    - latency: 1.062429ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:56:53Z"
    - latency: 1.230527ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:55:53Z"
    - latency: 993.086µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:54:53Z"
    - latency: 2.336182ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:53:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T13:52:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-92-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-92.ec2.internal
      uid: 86110797-5905-4f92-9230-c2eee26ac223
    resourceVersion: "22211"
    uid: 800d0a72-906d-4be2-b1b9-aa595c140f11
  spec:
    sourcePod: network-check-source-989f8b8dc-shl9d
    targetEndpoint: ab704a38507724e04b09d20b0c59fd27-d1cef354c8a6b270.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T13:58:53Z"
      message: 'load-balancer-api-external: tcp connection to ab704a38507724e04b09d20b0c59fd27-d1cef354c8a6b270.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.58086ms
      message: 'load-balancer-api-external: tcp connection to ab704a38507724e04b09d20b0c59fd27-d1cef354c8a6b270.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:58:53Z"
    - latency: 7.059157ms
      message: 'load-balancer-api-external: resolved host name ab704a38507724e04b09d20b0c59fd27-d1cef354c8a6b270.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:58:53Z"
    - latency: 5.529234ms
      message: 'load-balancer-api-external: tcp connection to ab704a38507724e04b09d20b0c59fd27-d1cef354c8a6b270.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:57:53Z"
    - latency: 8.417932ms
      message: 'load-balancer-api-external: resolved host name ab704a38507724e04b09d20b0c59fd27-d1cef354c8a6b270.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:57:53Z"
    - latency: 5.053623ms
      message: 'load-balancer-api-external: tcp connection to ab704a38507724e04b09d20b0c59fd27-d1cef354c8a6b270.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:56:53Z"
    - latency: 10.499569ms
      message: 'load-balancer-api-external: resolved host name ab704a38507724e04b09d20b0c59fd27-d1cef354c8a6b270.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:56:53Z"
    - latency: 5.648994ms
      message: 'load-balancer-api-external: tcp connection to ab704a38507724e04b09d20b0c59fd27-d1cef354c8a6b270.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:55:53Z"
    - latency: 8.139343ms
      message: 'load-balancer-api-external: resolved host name ab704a38507724e04b09d20b0c59fd27-d1cef354c8a6b270.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:55:53Z"
    - latency: 4.625898ms
      message: 'load-balancer-api-external: tcp connection to ab704a38507724e04b09d20b0c59fd27-d1cef354c8a6b270.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:54:53Z"
    - latency: 8.472594ms
      message: 'load-balancer-api-external: resolved host name ab704a38507724e04b09d20b0c59fd27-d1cef354c8a6b270.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:54:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T13:52:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-92-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-92.ec2.internal
      uid: 86110797-5905-4f92-9230-c2eee26ac223
    resourceVersion: "22210"
    uid: 086bb40f-4355-4818-ba80-df6a3e33cc5d
  spec:
    sourcePod: network-check-source-989f8b8dc-shl9d
    targetEndpoint: ab704a38507724e04b09d20b0c59fd27-d1cef354c8a6b270.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T13:58:53Z"
      message: 'load-balancer-api-internal: tcp connection to ab704a38507724e04b09d20b0c59fd27-d1cef354c8a6b270.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.59547ms
      message: 'load-balancer-api-internal: tcp connection to ab704a38507724e04b09d20b0c59fd27-d1cef354c8a6b270.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:58:53Z"
    - latency: 7.045607ms
      message: 'load-balancer-api-internal: resolved host name ab704a38507724e04b09d20b0c59fd27-d1cef354c8a6b270.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:58:53Z"
    - latency: 6.063865ms
      message: 'load-balancer-api-internal: tcp connection to ab704a38507724e04b09d20b0c59fd27-d1cef354c8a6b270.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:57:53Z"
    - latency: 8.31398ms
      message: 'load-balancer-api-internal: resolved host name ab704a38507724e04b09d20b0c59fd27-d1cef354c8a6b270.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:57:53Z"
    - latency: 4.938085ms
      message: 'load-balancer-api-internal: tcp connection to ab704a38507724e04b09d20b0c59fd27-d1cef354c8a6b270.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:56:53Z"
    - latency: 10.458478ms
      message: 'load-balancer-api-internal: resolved host name ab704a38507724e04b09d20b0c59fd27-d1cef354c8a6b270.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:56:53Z"
    - latency: 10.789879ms
      message: 'load-balancer-api-internal: tcp connection to ab704a38507724e04b09d20b0c59fd27-d1cef354c8a6b270.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:55:53Z"
    - latency: 7.944534ms
      message: 'load-balancer-api-internal: resolved host name ab704a38507724e04b09d20b0c59fd27-d1cef354c8a6b270.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:55:53Z"
    - latency: 4.826783ms
      message: 'load-balancer-api-internal: tcp connection to ab704a38507724e04b09d20b0c59fd27-d1cef354c8a6b270.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:54:53Z"
    - latency: 8.448836ms
      message: 'load-balancer-api-internal: resolved host name ab704a38507724e04b09d20b0c59fd27-d1cef354c8a6b270.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:54:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T13:52:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-92-to-network-check-target-ip-10-0-139-219
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-92.ec2.internal
      uid: 86110797-5905-4f92-9230-c2eee26ac223
    resourceVersion: "22824"
    uid: fa7b5fdb-2914-48bc-bea2-21133aef6890
  spec:
    sourcePod: network-check-source-989f8b8dc-shl9d
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T13:59:53Z"
      message: 'network-check-target-ip-10-0-139-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.873925ms
      message: 'network-check-target-ip-10-0-139-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:59:53Z"
    - latency: 1.837716ms
      message: 'network-check-target-ip-10-0-139-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:58:53Z"
    - latency: 2.29092ms
      message: 'network-check-target-ip-10-0-139-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:57:53Z"
    - latency: 2.183392ms
      message: 'network-check-target-ip-10-0-139-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:56:53Z"
    - latency: 2.054298ms
      message: 'network-check-target-ip-10-0-139-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:55:53Z"
    - latency: 1.874266ms
      message: 'network-check-target-ip-10-0-139-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:54:53Z"
    - latency: 2.287676ms
      message: 'network-check-target-ip-10-0-139-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:53:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T13:52:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-92-to-network-check-target-ip-10-0-141-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-92.ec2.internal
      uid: 86110797-5905-4f92-9230-c2eee26ac223
    resourceVersion: "22825"
    uid: a9df4527-ccb0-4551-8614-c4d318fb7bb1
  spec:
    sourcePod: network-check-source-989f8b8dc-shl9d
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T13:59:53Z"
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.301447ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:59:53Z"
    - latency: 2.185401ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:58:53Z"
    - latency: 2.625204ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:57:53Z"
    - latency: 2.164552ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:56:53Z"
    - latency: 2.241977ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:55:53Z"
    - latency: 2.339803ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:54:53Z"
    - latency: 2.658435ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:53:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T13:52:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-92-to-network-check-target-ip-10-0-143-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-92.ec2.internal
      uid: 86110797-5905-4f92-9230-c2eee26ac223
    resourceVersion: "22823"
    uid: ddd99846-7676-4d97-989b-151d48bdf368
  spec:
    sourcePod: network-check-source-989f8b8dc-shl9d
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T13:59:53Z"
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 970.589µs
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:59:53Z"
    - latency: 1.310975ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:58:53Z"
    - latency: 1.410714ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:57:53Z"
    - latency: 1.580003ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:56:53Z"
    - latency: 1.364385ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:55:53Z"
    - latency: 789.978µs
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:54:53Z"
    - latency: 2.408018ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:53:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T13:52:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-92-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-92.ec2.internal
      uid: 86110797-5905-4f92-9230-c2eee26ac223
    resourceVersion: "22209"
    uid: a74bd2c7-ab74-4412-8abf-150957cd1bb5
  spec:
    sourcePod: network-check-source-989f8b8dc-shl9d
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T13:58:53Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 996.622µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:58:53Z"
    - latency: 1.905274ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:58:53Z"
    - latency: 1.344027ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:57:53Z"
    - latency: 2.899995ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:57:53Z"
    - latency: 1.007023ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:56:53Z"
    - latency: 2.162525ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:56:53Z"
    - latency: 686.592µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:55:53Z"
    - latency: 1.69247ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:55:53Z"
    - latency: 985.048µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:54:53Z"
    - latency: 1.768737ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:54:53Z"
kind: List
metadata:
  resourceVersion: ""