apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T19:41:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-230-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-230.ec2.internal
      uid: df4133ee-acb4-4b94-a054-aef5412df21e
    resourceVersion: "24919"
    uid: c9665463-8d08-4151-88e1-358b53538668
  spec:
    sourcePod: network-check-source-dbd9cf844-d76rp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T19:48:21Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.136645ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:48:21Z"
    - latency: 2.498405ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:47:21Z"
    - latency: 1.303026ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:46:21Z"
    - latency: 1.65264ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:45:21Z"
    - latency: 3.520986ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:44:21Z"
    - latency: 858.717µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:43:21Z"
    - latency: 1.697286ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:42:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T19:41:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-230-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-230.ec2.internal
      uid: df4133ee-acb4-4b94-a054-aef5412df21e
    resourceVersion: "23784"
    uid: 0a18f9d1-82ba-4925-89bb-56c8e137547f
  spec:
    sourcePod: network-check-source-dbd9cf844-d76rp
    targetEndpoint: a88cfce474b3d4b0186f029bcf2f6c06-1aec8ffa71a497b5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T19:47:21Z"
      message: 'load-balancer-api-external: tcp connection to a88cfce474b3d4b0186f029bcf2f6c06-1aec8ffa71a497b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.126851ms
      message: 'load-balancer-api-external: tcp connection to a88cfce474b3d4b0186f029bcf2f6c06-1aec8ffa71a497b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:47:21Z"
    - latency: 9.80663ms
      message: 'load-balancer-api-external: resolved host name a88cfce474b3d4b0186f029bcf2f6c06-1aec8ffa71a497b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T19:47:21Z"
    - latency: 4.316732ms
      message: 'load-balancer-api-external: tcp connection to a88cfce474b3d4b0186f029bcf2f6c06-1aec8ffa71a497b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:46:21Z"
    - latency: 9.841262ms
      message: 'load-balancer-api-external: resolved host name a88cfce474b3d4b0186f029bcf2f6c06-1aec8ffa71a497b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T19:46:21Z"
    - latency: 5.658157ms
      message: 'load-balancer-api-external: tcp connection to a88cfce474b3d4b0186f029bcf2f6c06-1aec8ffa71a497b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:45:21Z"
    - latency: 11.243566ms
      message: 'load-balancer-api-external: resolved host name a88cfce474b3d4b0186f029bcf2f6c06-1aec8ffa71a497b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T19:45:21Z"
    - latency: 5.001672ms
      message: 'load-balancer-api-external: tcp connection to a88cfce474b3d4b0186f029bcf2f6c06-1aec8ffa71a497b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:44:21Z"
    - latency: 18.052668ms
      message: 'load-balancer-api-external: resolved host name a88cfce474b3d4b0186f029bcf2f6c06-1aec8ffa71a497b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T19:44:21Z"
    - latency: 5.046918ms
      message: 'load-balancer-api-external: tcp connection to a88cfce474b3d4b0186f029bcf2f6c06-1aec8ffa71a497b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:43:21Z"
    - latency: 8.967249ms
      message: 'load-balancer-api-external: resolved host name a88cfce474b3d4b0186f029bcf2f6c06-1aec8ffa71a497b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T19:43:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T19:41:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-230-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-230.ec2.internal
      uid: df4133ee-acb4-4b94-a054-aef5412df21e
    resourceVersion: "23785"
    uid: a354236f-ab66-4dbe-8977-f0fb5f0db5c1
  spec:
    sourcePod: network-check-source-dbd9cf844-d76rp
    targetEndpoint: a88cfce474b3d4b0186f029bcf2f6c06-1aec8ffa71a497b5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T19:47:21Z"
      message: 'load-balancer-api-internal: tcp connection to a88cfce474b3d4b0186f029bcf2f6c06-1aec8ffa71a497b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.219243ms
      message: 'load-balancer-api-internal: tcp connection to a88cfce474b3d4b0186f029bcf2f6c06-1aec8ffa71a497b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:47:21Z"
    - latency: 10.898866ms
      message: 'load-balancer-api-internal: resolved host name a88cfce474b3d4b0186f029bcf2f6c06-1aec8ffa71a497b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T19:47:21Z"
    - latency: 4.303958ms
      message: 'load-balancer-api-internal: tcp connection to a88cfce474b3d4b0186f029bcf2f6c06-1aec8ffa71a497b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:46:21Z"
    - latency: 9.749501ms
      message: 'load-balancer-api-internal: resolved host name a88cfce474b3d4b0186f029bcf2f6c06-1aec8ffa71a497b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T19:46:21Z"
    - latency: 5.562959ms
      message: 'load-balancer-api-internal: tcp connection to a88cfce474b3d4b0186f029bcf2f6c06-1aec8ffa71a497b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:45:21Z"
    - latency: 11.539243ms
      message: 'load-balancer-api-internal: resolved host name a88cfce474b3d4b0186f029bcf2f6c06-1aec8ffa71a497b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T19:45:21Z"
    - latency: 5.018571ms
      message: 'load-balancer-api-internal: tcp connection to a88cfce474b3d4b0186f029bcf2f6c06-1aec8ffa71a497b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:44:21Z"
    - latency: 17.993745ms
      message: 'load-balancer-api-internal: resolved host name a88cfce474b3d4b0186f029bcf2f6c06-1aec8ffa71a497b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T19:44:21Z"
    - latency: 6.873199ms
      message: 'load-balancer-api-internal: tcp connection to a88cfce474b3d4b0186f029bcf2f6c06-1aec8ffa71a497b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:43:21Z"
    - latency: 8.993283ms
      message: 'load-balancer-api-internal: resolved host name a88cfce474b3d4b0186f029bcf2f6c06-1aec8ffa71a497b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T19:43:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T19:41:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-230-to-network-check-target-ip-10-0-131-230
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-230.ec2.internal
      uid: df4133ee-acb4-4b94-a054-aef5412df21e
    resourceVersion: "24916"
    uid: 1d18aaa0-20f7-4deb-8804-64d5eddbebee
  spec:
    sourcePod: network-check-source-dbd9cf844-d76rp
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T19:48:21Z"
      message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 804.624µs
      message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:48:21Z"
    - latency: 2.759276ms
      message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:47:21Z"
    - latency: 878.162µs
      message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:46:21Z"
    - latency: 3.886842ms
      message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:45:21Z"
    - latency: 11.058295ms
      message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:44:21Z"
    - latency: 835.207µs
      message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:43:21Z"
    - latency: 2.18254ms
      message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:42:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T19:41:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-230-to-network-check-target-ip-10-0-133-234
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-230.ec2.internal
      uid: df4133ee-acb4-4b94-a054-aef5412df21e
    resourceVersion: "24917"
    uid: 247800a9-0bb9-488f-ae8e-1d8718c1a071
  spec:
    sourcePod: network-check-source-dbd9cf844-d76rp
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T19:48:21Z"
      message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.790534ms
      message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:48:21Z"
    - latency: 2.842567ms
      message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:47:21Z"
    - latency: 1.803023ms
      message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:46:21Z"
    - latency: 2.304837ms
      message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:45:21Z"
    - latency: 1.931289ms
      message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:44:21Z"
    - latency: 1.931811ms
      message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:43:21Z"
    - latency: 2.266793ms
      message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:42:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T19:41:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-230-to-network-check-target-ip-10-0-134-56
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-230.ec2.internal
      uid: df4133ee-acb4-4b94-a054-aef5412df21e
    resourceVersion: "24918"
    uid: d9cae954-efe3-41d8-bd5c-ceaa4c834e85
  spec:
    sourcePod: network-check-source-dbd9cf844-d76rp
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T19:48:21Z"
      message: 'network-check-target-ip-10-0-134-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.756043ms
      message: 'network-check-target-ip-10-0-134-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:48:21Z"
    - latency: 2.694139ms
      message: 'network-check-target-ip-10-0-134-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:47:21Z"
    - latency: 2.209302ms
      message: 'network-check-target-ip-10-0-134-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:46:21Z"
    - latency: 2.779388ms
      message: 'network-check-target-ip-10-0-134-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:45:21Z"
    - latency: 4.450204ms
      message: 'network-check-target-ip-10-0-134-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:44:21Z"
    - latency: 2.107925ms
      message: 'network-check-target-ip-10-0-134-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:43:21Z"
    - latency: 2.163293ms
      message: 'network-check-target-ip-10-0-134-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:42:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T19:41:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-230-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-230.ec2.internal
      uid: df4133ee-acb4-4b94-a054-aef5412df21e
    resourceVersion: "23783"
    uid: 221c5a25-240a-4d97-9358-4c09f9e7badd
  spec:
    sourcePod: network-check-source-dbd9cf844-d76rp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T19:47:21Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.14979ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:47:21Z"
    - latency: 3.629657ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T19:47:21Z"
    - latency: 1.000522ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:46:21Z"
    - latency: 1.73107ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T19:46:21Z"
    - latency: 951.8µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:45:21Z"
    - latency: 3.862046ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T19:45:21Z"
    - latency: 810.804µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:44:21Z"
    - latency: 5.004487ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T19:44:21Z"
    - latency: 760.881µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T19:43:21Z"
    - latency: 2.057245ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T19:43:21Z"
kind: List
metadata:
  resourceVersion: ""