apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T15:05:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-149-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-149.ec2.internal
      uid: 6d4d5402-e889-42ec-90a9-bc131f5ba43e
    resourceVersion: "23820"
    uid: f0268b97-8e83-463d-84d5-209fd8a18a2f
  spec:
    sourcePod: network-check-source-dbd9cf844-mpt8q
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T15:12:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.012637ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:12:30Z"
    - latency: 1.218527ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:11:30Z"
    - latency: 1.362442ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:10:30Z"
    - latency: 1.08117ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:09:30Z"
    - latency: 1.348697ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:08:30Z"
    - latency: 1.199814ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:07:30Z"
    - latency: 1.256156ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:06:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T15:05:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-149-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-149.ec2.internal
      uid: 6d4d5402-e889-42ec-90a9-bc131f5ba43e
    resourceVersion: "28138"
    uid: fd6a1cf5-b7bd-4a22-93b2-865d68592320
  spec:
    sourcePod: network-check-source-dbd9cf844-mpt8q
    targetEndpoint: a339a40aeccce40448f6040e80fdab30-4748bb0f9352f111.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T15:11:30Z"
      message: 'load-balancer-api-external: tcp connection to a339a40aeccce40448f6040e80fdab30-4748bb0f9352f111.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.107446ms
      message: 'load-balancer-api-external: tcp connection to a339a40aeccce40448f6040e80fdab30-4748bb0f9352f111.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:17:30Z"
    - latency: 8.900634ms
      message: 'load-balancer-api-external: resolved host name a339a40aeccce40448f6040e80fdab30-4748bb0f9352f111.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:17:30Z"
    - latency: 6.963193ms
      message: 'load-balancer-api-external: tcp connection to a339a40aeccce40448f6040e80fdab30-4748bb0f9352f111.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:16:30Z"
    - latency: 7.886259ms
      message: 'load-balancer-api-external: resolved host name a339a40aeccce40448f6040e80fdab30-4748bb0f9352f111.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:16:30Z"
    - latency: 5.77941ms
      message: 'load-balancer-api-external: tcp connection to a339a40aeccce40448f6040e80fdab30-4748bb0f9352f111.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:15:30Z"
    - latency: 7.283017ms
      message: 'load-balancer-api-external: resolved host name a339a40aeccce40448f6040e80fdab30-4748bb0f9352f111.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:15:30Z"
    - latency: 5.181653ms
      message: 'load-balancer-api-external: tcp connection to a339a40aeccce40448f6040e80fdab30-4748bb0f9352f111.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:14:30Z"
    - latency: 8.410929ms
      message: 'load-balancer-api-external: resolved host name a339a40aeccce40448f6040e80fdab30-4748bb0f9352f111.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:14:30Z"
    - latency: 5.077096ms
      message: 'load-balancer-api-external: tcp connection to a339a40aeccce40448f6040e80fdab30-4748bb0f9352f111.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:13:30Z"
    - latency: 8.356491ms
      message: 'load-balancer-api-external: resolved host name a339a40aeccce40448f6040e80fdab30-4748bb0f9352f111.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:13:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T15:05:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-149-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-149.ec2.internal
      uid: 6d4d5402-e889-42ec-90a9-bc131f5ba43e
    resourceVersion: "28137"
    uid: c79b4db0-40b0-4f0d-8dbd-8c6fb8d37371
  spec:
    sourcePod: network-check-source-dbd9cf844-mpt8q
    targetEndpoint: a339a40aeccce40448f6040e80fdab30-4748bb0f9352f111.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T15:11:30Z"
      message: 'load-balancer-api-internal: tcp connection to a339a40aeccce40448f6040e80fdab30-4748bb0f9352f111.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.16661ms
      message: 'load-balancer-api-internal: tcp connection to a339a40aeccce40448f6040e80fdab30-4748bb0f9352f111.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:17:30Z"
    - latency: 8.812277ms
      message: 'load-balancer-api-internal: resolved host name a339a40aeccce40448f6040e80fdab30-4748bb0f9352f111.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:17:30Z"
    - latency: 5.392255ms
      message: 'load-balancer-api-internal: tcp connection to a339a40aeccce40448f6040e80fdab30-4748bb0f9352f111.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:16:30Z"
    - latency: 7.945796ms
      message: 'load-balancer-api-internal: resolved host name a339a40aeccce40448f6040e80fdab30-4748bb0f9352f111.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:16:30Z"
    - latency: 4.858558ms
      message: 'load-balancer-api-internal: tcp connection to a339a40aeccce40448f6040e80fdab30-4748bb0f9352f111.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:15:30Z"
    - latency: 7.251089ms
      message: 'load-balancer-api-internal: resolved host name a339a40aeccce40448f6040e80fdab30-4748bb0f9352f111.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:15:30Z"
    - latency: 5.147664ms
      message: 'load-balancer-api-internal: tcp connection to a339a40aeccce40448f6040e80fdab30-4748bb0f9352f111.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:14:30Z"
    - latency: 8.498271ms
      message: 'load-balancer-api-internal: resolved host name a339a40aeccce40448f6040e80fdab30-4748bb0f9352f111.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:14:30Z"
    - latency: 5.049864ms
      message: 'load-balancer-api-internal: tcp connection to a339a40aeccce40448f6040e80fdab30-4748bb0f9352f111.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:13:30Z"
    - latency: 8.336581ms
      message: 'load-balancer-api-internal: resolved host name a339a40aeccce40448f6040e80fdab30-4748bb0f9352f111.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:13:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T15:05:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-149-to-network-check-target-ip-10-0-128-147
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-149.ec2.internal
      uid: 6d4d5402-e889-42ec-90a9-bc131f5ba43e
    resourceVersion: "23823"
    uid: b69cb96c-fd1a-4309-8167-1c927debb122
  spec:
    sourcePod: network-check-source-dbd9cf844-mpt8q
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T15:12:31Z"
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.063715ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:12:31Z"
    - latency: 1.06953ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:11:31Z"
    - latency: 2.193804ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:10:31Z"
    - latency: 1.160629ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:09:31Z"
    - latency: 1.152467ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:08:31Z"
    - latency: 825.265µs
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:07:31Z"
    - latency: 2.510619ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:06:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T15:05:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-149-to-network-check-target-ip-10-0-130-149
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-149.ec2.internal
      uid: 6d4d5402-e889-42ec-90a9-bc131f5ba43e
    resourceVersion: "23819"
    uid: a975ee3e-a513-40b6-a2f8-6ebc15444472
  spec:
    sourcePod: network-check-source-dbd9cf844-mpt8q
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T15:12:30Z"
      message: 'network-check-target-ip-10-0-130-149: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 893.871µs
      message: 'network-check-target-ip-10-0-130-149: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:12:30Z"
    - latency: 1.575835ms
      message: 'network-check-target-ip-10-0-130-149: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:11:30Z"
    - latency: 1.535885ms
      message: 'network-check-target-ip-10-0-130-149: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:10:30Z"
    - latency: 924.654µs
      message: 'network-check-target-ip-10-0-130-149: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:09:30Z"
    - latency: 1.707141ms
      message: 'network-check-target-ip-10-0-130-149: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:08:30Z"
    - latency: 1.225333ms
      message: 'network-check-target-ip-10-0-130-149: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:07:30Z"
    - latency: 1.687675ms
      message: 'network-check-target-ip-10-0-130-149: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:06:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T15:06:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-149-to-network-check-target-ip-10-0-133-68
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-149.ec2.internal
      uid: 6d4d5402-e889-42ec-90a9-bc131f5ba43e
    resourceVersion: "24293"
    uid: 9c08e9ac-cc12-48c8-a31e-5735d37b5ce4
  spec:
    sourcePod: network-check-source-dbd9cf844-mpt8q
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T15:13:15Z"
      message: 'network-check-target-ip-10-0-133-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.488333ms
      message: 'network-check-target-ip-10-0-133-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:13:15Z"
    - latency: 2.210355ms
      message: 'network-check-target-ip-10-0-133-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:12:15Z"
    - latency: 2.925637ms
      message: 'network-check-target-ip-10-0-133-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:11:15Z"
    - latency: 2.343441ms
      message: 'network-check-target-ip-10-0-133-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:10:15Z"
    - latency: 2.092736ms
      message: 'network-check-target-ip-10-0-133-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:09:15Z"
    - latency: 2.37987ms
      message: 'network-check-target-ip-10-0-133-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:08:15Z"
    - latency: 2.072798ms
      message: 'network-check-target-ip-10-0-133-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:07:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T15:05:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-149-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-149.ec2.internal
      uid: 6d4d5402-e889-42ec-90a9-bc131f5ba43e
    resourceVersion: "28136"
    uid: 559bf6db-4422-4f1d-84bb-4e901a01a24f
  spec:
    sourcePod: network-check-source-dbd9cf844-mpt8q
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T15:11:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.042197ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:17:30Z"
    - latency: 1.907223ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:17:30Z"
    - latency: 2.256805ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:16:30Z"
    - latency: 1.867272ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:16:30Z"
    - latency: 791.019µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:15:30Z"
    - latency: 1.903082ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:15:30Z"
    - latency: 835.781µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:14:30Z"
    - latency: 1.952551ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:14:30Z"
    - latency: 757.013µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:13:30Z"
    - latency: 1.770469ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:13:30Z"
kind: List
metadata:
  resourceVersion: ""