apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:39:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-5-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-5.ec2.internal
      uid: 0db24675-4d8c-4e72-9573-ef402ed7e7cc
    resourceVersion: "16254"
    uid: 05197e85-ce45-41ad-81fe-ae2165407620
  spec:
    sourcePod: network-check-source-dbd9cf844-5c4v8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:46:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.3574ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:46:59Z"
    - latency: 1.023793ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:45:59Z"
    - latency: 816.77µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:44:59Z"
    - latency: 894.944µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:43:59Z"
    - latency: 867.415µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:42:59Z"
    - latency: 921.407µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:41:59Z"
    - latency: 1.023747ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:40:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:39:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-5-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-5.ec2.internal
      uid: 0db24675-4d8c-4e72-9573-ef402ed7e7cc
    resourceVersion: "15927"
    uid: 483b6dbc-bb94-4cc0-8ba9-e60d6efb39e6
  spec:
    sourcePod: network-check-source-dbd9cf844-5c4v8
    targetEndpoint: ada25544be6124113aa70557b49d1749-2ca62c14fb1e84b1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:45:59Z"
      message: 'load-balancer-api-external: tcp connection to ada25544be6124113aa70557b49d1749-2ca62c14fb1e84b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.140021ms
      message: 'load-balancer-api-external: tcp connection to ada25544be6124113aa70557b49d1749-2ca62c14fb1e84b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:45:59Z"
    - latency: 8.902677ms
      message: 'load-balancer-api-external: resolved host name ada25544be6124113aa70557b49d1749-2ca62c14fb1e84b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:45:59Z"
    - latency: 4.404181ms
      message: 'load-balancer-api-external: tcp connection to ada25544be6124113aa70557b49d1749-2ca62c14fb1e84b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:44:59Z"
    - latency: 9.163071ms
      message: 'load-balancer-api-external: resolved host name ada25544be6124113aa70557b49d1749-2ca62c14fb1e84b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:44:59Z"
    - latency: 4.664044ms
      message: 'load-balancer-api-external: tcp connection to ada25544be6124113aa70557b49d1749-2ca62c14fb1e84b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:43:59Z"
    - latency: 7.13028ms
      message: 'load-balancer-api-external: resolved host name ada25544be6124113aa70557b49d1749-2ca62c14fb1e84b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:43:59Z"
    - latency: 5.22983ms
      message: 'load-balancer-api-external: tcp connection to ada25544be6124113aa70557b49d1749-2ca62c14fb1e84b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:42:59Z"
    - latency: 9.185695ms
      message: 'load-balancer-api-external: resolved host name ada25544be6124113aa70557b49d1749-2ca62c14fb1e84b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:42:59Z"
    - latency: 5.051097ms
      message: 'load-balancer-api-external: tcp connection to ada25544be6124113aa70557b49d1749-2ca62c14fb1e84b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:41:59Z"
    - latency: 8.229086ms
      message: 'load-balancer-api-external: resolved host name ada25544be6124113aa70557b49d1749-2ca62c14fb1e84b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:41:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:39:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-5-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-5.ec2.internal
      uid: 0db24675-4d8c-4e72-9573-ef402ed7e7cc
    resourceVersion: "15926"
    uid: ead61a56-106c-4e85-93e4-b95551f7facb
  spec:
    sourcePod: network-check-source-dbd9cf844-5c4v8
    targetEndpoint: ada25544be6124113aa70557b49d1749-2ca62c14fb1e84b1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:45:59Z"
      message: 'load-balancer-api-internal: tcp connection to ada25544be6124113aa70557b49d1749-2ca62c14fb1e84b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.991914ms
      message: 'load-balancer-api-internal: tcp connection to ada25544be6124113aa70557b49d1749-2ca62c14fb1e84b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:45:59Z"
    - latency: 8.983227ms
      message: 'load-balancer-api-internal: resolved host name ada25544be6124113aa70557b49d1749-2ca62c14fb1e84b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:45:59Z"
    - latency: 4.333966ms
      message: 'load-balancer-api-internal: tcp connection to ada25544be6124113aa70557b49d1749-2ca62c14fb1e84b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:44:59Z"
    - latency: 9.201711ms
      message: 'load-balancer-api-internal: resolved host name ada25544be6124113aa70557b49d1749-2ca62c14fb1e84b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:44:59Z"
    - latency: 4.604673ms
      message: 'load-balancer-api-internal: tcp connection to ada25544be6124113aa70557b49d1749-2ca62c14fb1e84b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:43:59Z"
    - latency: 7.165223ms
      message: 'load-balancer-api-internal: resolved host name ada25544be6124113aa70557b49d1749-2ca62c14fb1e84b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:43:59Z"
    - latency: 5.181918ms
      message: 'load-balancer-api-internal: tcp connection to ada25544be6124113aa70557b49d1749-2ca62c14fb1e84b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:42:59Z"
    - latency: 9.216631ms
      message: 'load-balancer-api-internal: resolved host name ada25544be6124113aa70557b49d1749-2ca62c14fb1e84b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:42:59Z"
    - latency: 5.056998ms
      message: 'load-balancer-api-internal: tcp connection to ada25544be6124113aa70557b49d1749-2ca62c14fb1e84b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:41:59Z"
    - latency: 8.327162ms
      message: 'load-balancer-api-internal: resolved host name ada25544be6124113aa70557b49d1749-2ca62c14fb1e84b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:41:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:39:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-5-to-network-check-target-ip-10-0-130-127
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-5.ec2.internal
      uid: 0db24675-4d8c-4e72-9573-ef402ed7e7cc
    resourceVersion: "16253"
    uid: 77ef747d-1203-42bf-a392-3b8e4112796a
  spec:
    sourcePod: network-check-source-dbd9cf844-5c4v8
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:46:59Z"
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.47391ms
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:46:59Z"
    - latency: 2.282879ms
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:45:59Z"
    - latency: 2.238669ms
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:44:59Z"
    - latency: 2.065831ms
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:43:59Z"
    - latency: 2.255799ms
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:42:59Z"
    - latency: 2.198371ms
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:41:59Z"
    - latency: 2.736685ms
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:40:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:39:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-5-to-network-check-target-ip-10-0-131-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-5.ec2.internal
      uid: 0db24675-4d8c-4e72-9573-ef402ed7e7cc
    resourceVersion: "16251"
    uid: 712a0945-5732-4ebd-8606-9ed2557ab139
  spec:
    sourcePod: network-check-source-dbd9cf844-5c4v8
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:46:59Z"
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.814847ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:46:59Z"
    - latency: 1.827427ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:45:59Z"
    - latency: 689.931µs
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:44:59Z"
    - latency: 1.25939ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:43:59Z"
    - latency: 846.545µs
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:42:59Z"
    - latency: 891.417µs
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:41:59Z"
    - latency: 1.160859ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:40:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:39:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-5-to-network-check-target-ip-10-0-142-71
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-5.ec2.internal
      uid: 0db24675-4d8c-4e72-9573-ef402ed7e7cc
    resourceVersion: "16252"
    uid: 2fbad90b-0d92-41fd-9115-63f03b5ad651
  spec:
    sourcePod: network-check-source-dbd9cf844-5c4v8
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:46:59Z"
      message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.055185ms
      message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:46:59Z"
    - latency: 2.391561ms
      message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:45:59Z"
    - latency: 2.079811ms
      message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:44:59Z"
    - latency: 2.247141ms
      message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:43:59Z"
    - latency: 2.295211ms
      message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:42:59Z"
    - latency: 2.280423ms
      message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:41:59Z"
    - latency: 2.219043ms
      message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:40:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:39:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-5-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-5.ec2.internal
      uid: 0db24675-4d8c-4e72-9573-ef402ed7e7cc
    resourceVersion: "15925"
    uid: e92da9ca-c21c-47b7-a2ce-681d66e57030
  spec:
    sourcePod: network-check-source-dbd9cf844-5c4v8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:45:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 728.952µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:45:59Z"
    - latency: 2.570135ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:45:59Z"
    - latency: 721.984µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:44:59Z"
    - latency: 1.943923ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:44:59Z"
    - latency: 867.335µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:43:59Z"
    - latency: 1.610519ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:43:59Z"
    - latency: 863.285µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:42:59Z"
    - latency: 2.191126ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:42:59Z"
    - latency: 826.365µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:41:59Z"
    - latency: 1.67415ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:41:59Z"
kind: List
metadata:
  resourceVersion: ""