apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T19:53:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-154-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-154.ec2.internal
      uid: f9485f9a-17c0-49fc-9cae-67b4cc08de1d
    resourceVersion: "23984"
    uid: e8995f2d-674b-4d1e-b603-0a5f706d703c
  spec:
    sourcePod: network-check-source-dbd9cf844-clmwm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T20:00:17Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.534103ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T20:00:17Z"
    - latency: 1.140036ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:59:17Z"
    - latency: 853.539µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:58:17Z"
    - latency: 1.394109ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:57:17Z"
    - latency: 2.173534ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:56:17Z"
    - latency: 1.530344ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:55:17Z"
    - latency: 1.37245ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:54:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T19:53:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-154-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-154.ec2.internal
      uid: f9485f9a-17c0-49fc-9cae-67b4cc08de1d
    resourceVersion: "22701"
    uid: 390e9849-4bad-488e-8ea2-fd2811a78a1e
  spec:
    sourcePod: network-check-source-dbd9cf844-clmwm
    targetEndpoint: a43db342d08944bc69ee6ad176a61ef4-de5ddeef3e83b760.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T19:59:17Z"
      message: 'load-balancer-api-external: tcp connection to a43db342d08944bc69ee6ad176a61ef4-de5ddeef3e83b760.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.104975ms
      message: 'load-balancer-api-external: tcp connection to a43db342d08944bc69ee6ad176a61ef4-de5ddeef3e83b760.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:59:17Z"
    - latency: 9.756705ms
      message: 'load-balancer-api-external: resolved host name a43db342d08944bc69ee6ad176a61ef4-de5ddeef3e83b760.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:59:17Z"
    - latency: 4.902171ms
      message: 'load-balancer-api-external: tcp connection to a43db342d08944bc69ee6ad176a61ef4-de5ddeef3e83b760.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:58:17Z"
    - latency: 7.53873ms
      message: 'load-balancer-api-external: resolved host name a43db342d08944bc69ee6ad176a61ef4-de5ddeef3e83b760.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:58:17Z"
    - latency: 4.602237ms
      message: 'load-balancer-api-external: tcp connection to a43db342d08944bc69ee6ad176a61ef4-de5ddeef3e83b760.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:57:17Z"
    - latency: 9.657523ms
      message: 'load-balancer-api-external: resolved host name a43db342d08944bc69ee6ad176a61ef4-de5ddeef3e83b760.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:57:17Z"
    - latency: 4.43892ms
      message: 'load-balancer-api-external: tcp connection to a43db342d08944bc69ee6ad176a61ef4-de5ddeef3e83b760.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:56:17Z"
    - latency: 12.037716ms
      message: 'load-balancer-api-external: resolved host name a43db342d08944bc69ee6ad176a61ef4-de5ddeef3e83b760.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:56:17Z"
    - latency: 3.635609ms
      message: 'load-balancer-api-external: tcp connection to a43db342d08944bc69ee6ad176a61ef4-de5ddeef3e83b760.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:55:17Z"
    - latency: 11.34359ms
      message: 'load-balancer-api-external: resolved host name a43db342d08944bc69ee6ad176a61ef4-de5ddeef3e83b760.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:55:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T19:53:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-154-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-154.ec2.internal
      uid: f9485f9a-17c0-49fc-9cae-67b4cc08de1d
    resourceVersion: "22700"
    uid: c4805172-5e58-44c6-b8c8-712cb991a76c
  spec:
    sourcePod: network-check-source-dbd9cf844-clmwm
    targetEndpoint: a43db342d08944bc69ee6ad176a61ef4-de5ddeef3e83b760.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T19:59:17Z"
      message: 'load-balancer-api-internal: tcp connection to a43db342d08944bc69ee6ad176a61ef4-de5ddeef3e83b760.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.106064ms
      message: 'load-balancer-api-internal: tcp connection to a43db342d08944bc69ee6ad176a61ef4-de5ddeef3e83b760.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:59:17Z"
    - latency: 9.705814ms
      message: 'load-balancer-api-internal: resolved host name a43db342d08944bc69ee6ad176a61ef4-de5ddeef3e83b760.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:59:17Z"
    - latency: 4.886088ms
      message: 'load-balancer-api-internal: tcp connection to a43db342d08944bc69ee6ad176a61ef4-de5ddeef3e83b760.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:58:17Z"
    - latency: 7.496219ms
      message: 'load-balancer-api-internal: resolved host name a43db342d08944bc69ee6ad176a61ef4-de5ddeef3e83b760.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:58:17Z"
    - latency: 3.98836ms
      message: 'load-balancer-api-internal: tcp connection to a43db342d08944bc69ee6ad176a61ef4-de5ddeef3e83b760.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:57:17Z"
    - latency: 9.646649ms
      message: 'load-balancer-api-internal: resolved host name a43db342d08944bc69ee6ad176a61ef4-de5ddeef3e83b760.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:57:17Z"
    - latency: 5.54328ms
      message: 'load-balancer-api-internal: tcp connection to a43db342d08944bc69ee6ad176a61ef4-de5ddeef3e83b760.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:56:17Z"
    - latency: 11.960076ms
      message: 'load-balancer-api-internal: resolved host name a43db342d08944bc69ee6ad176a61ef4-de5ddeef3e83b760.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:56:17Z"
    - latency: 6.400143ms
      message: 'load-balancer-api-internal: tcp connection to a43db342d08944bc69ee6ad176a61ef4-de5ddeef3e83b760.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:55:17Z"
    - latency: 11.333559ms
      message: 'load-balancer-api-internal: resolved host name a43db342d08944bc69ee6ad176a61ef4-de5ddeef3e83b760.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:55:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T19:53:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-154-to-network-check-target-ip-10-0-129-154
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-154.ec2.internal
      uid: f9485f9a-17c0-49fc-9cae-67b4cc08de1d
    resourceVersion: "23983"
    uid: 67607f59-1645-4e87-bb35-99cb66473c47
  spec:
    sourcePod: network-check-source-dbd9cf844-clmwm
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T20:00:17Z"
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.58751ms
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T20:00:17Z"
    - latency: 842.366µs
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:59:17Z"
    - latency: 864.842µs
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:58:17Z"
    - latency: 1.356679ms
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:57:17Z"
    - latency: 953.323µs
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:56:17Z"
    - latency: 1.580725ms
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:55:17Z"
    - latency: 1.882948ms
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:54:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T19:53:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-154-to-network-check-target-ip-10-0-132-2
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-154.ec2.internal
      uid: f9485f9a-17c0-49fc-9cae-67b4cc08de1d
    resourceVersion: "23982"
    uid: f42fc1d0-9468-479e-938f-114faa9acea6
  spec:
    sourcePod: network-check-source-dbd9cf844-clmwm
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T20:00:17Z"
      message: 'network-check-target-ip-10-0-132-2: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.83974ms
      message: 'network-check-target-ip-10-0-132-2: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T20:00:17Z"
    - latency: 2.233312ms
      message: 'network-check-target-ip-10-0-132-2: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:59:17Z"
    - latency: 2.242319ms
      message: 'network-check-target-ip-10-0-132-2: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:58:17Z"
    - latency: 2.50147ms
      message: 'network-check-target-ip-10-0-132-2: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:57:17Z"
    - latency: 2.31605ms
      message: 'network-check-target-ip-10-0-132-2: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:56:17Z"
    - latency: 2.256286ms
      message: 'network-check-target-ip-10-0-132-2: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:55:17Z"
    - latency: 2.375286ms
      message: 'network-check-target-ip-10-0-132-2: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:54:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T19:53:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-154-to-network-check-target-ip-10-0-138-254
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-154.ec2.internal
      uid: f9485f9a-17c0-49fc-9cae-67b4cc08de1d
    resourceVersion: "23981"
    uid: e1164ada-76af-46a5-bf40-6ae825cde97a
  spec:
    sourcePod: network-check-source-dbd9cf844-clmwm
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T20:00:17Z"
      message: 'network-check-target-ip-10-0-138-254: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.121002ms
      message: 'network-check-target-ip-10-0-138-254: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T20:00:17Z"
    - latency: 2.040536ms
      message: 'network-check-target-ip-10-0-138-254: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:59:17Z"
    - latency: 1.806071ms
      message: 'network-check-target-ip-10-0-138-254: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:58:17Z"
    - latency: 1.923229ms
      message: 'network-check-target-ip-10-0-138-254: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:57:17Z"
    - latency: 1.975845ms
      message: 'network-check-target-ip-10-0-138-254: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:56:17Z"
    - latency: 5.52016ms
      message: 'network-check-target-ip-10-0-138-254: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:55:17Z"
    - latency: 2.04332ms
      message: 'network-check-target-ip-10-0-138-254: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:54:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T19:53:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-154-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-154.ec2.internal
      uid: f9485f9a-17c0-49fc-9cae-67b4cc08de1d
    resourceVersion: "22699"
    uid: daf04cc4-780e-48b7-90da-370942091173
  spec:
    sourcePod: network-check-source-dbd9cf844-clmwm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T19:59:17Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.153006ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:59:17Z"
    - latency: 1.856513ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:59:17Z"
    - latency: 804.623µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:58:17Z"
    - latency: 1.789869ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:58:17Z"
    - latency: 1.102041ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:57:17Z"
    - latency: 2.079941ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:57:17Z"
    - latency: 1.189967ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:56:17Z"
    - latency: 3.172215ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:56:17Z"
    - latency: 4.18286ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:55:17Z"
    - latency: 2.050357ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:55:17Z"
kind: List
metadata:
  resourceVersion: ""