apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T17:00:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-118-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-118.ec2.internal
      uid: cf67ce39-3dec-4378-8c65-b1a39fafb7c6
    resourceVersion: "14587"
    uid: 7eff3aea-a428-4c98-b376-65ad1dc97e73
  spec:
    sourcePod: network-check-source-685456655f-4vfvs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T17:07:16Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 790.534µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:07:16Z"
    - latency: 1.104144ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:06:16Z"
    - latency: 1.17647ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:05:16Z"
    - latency: 946.043µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:04:16Z"
    - latency: 1.034119ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:03:16Z"
    - latency: 944.822µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:02:16Z"
    - latency: 1.123674ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:01:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T17:00:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-118-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-118.ec2.internal
      uid: cf67ce39-3dec-4378-8c65-b1a39fafb7c6
    resourceVersion: "14240"
    uid: dae7e25a-59a6-49a4-b4c2-8391a3681d74
  spec:
    sourcePod: network-check-source-685456655f-4vfvs
    targetEndpoint: af43f25341bbc4f6682987b06bbbd7ad-fee88d9788ad7868.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T17:06:16Z"
      message: 'load-balancer-api-external: tcp connection to af43f25341bbc4f6682987b06bbbd7ad-fee88d9788ad7868.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.782291ms
      message: 'load-balancer-api-external: tcp connection to af43f25341bbc4f6682987b06bbbd7ad-fee88d9788ad7868.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:06:16Z"
    - latency: 5.852249ms
      message: 'load-balancer-api-external: resolved host name af43f25341bbc4f6682987b06bbbd7ad-fee88d9788ad7868.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:06:16Z"
    - latency: 4.351449ms
      message: 'load-balancer-api-external: tcp connection to af43f25341bbc4f6682987b06bbbd7ad-fee88d9788ad7868.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:05:16Z"
    - latency: 7.258206ms
      message: 'load-balancer-api-external: resolved host name af43f25341bbc4f6682987b06bbbd7ad-fee88d9788ad7868.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:05:16Z"
    - latency: 3.273271ms
      message: 'load-balancer-api-external: tcp connection to af43f25341bbc4f6682987b06bbbd7ad-fee88d9788ad7868.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:04:16Z"
    - latency: 7.512564ms
      message: 'load-balancer-api-external: resolved host name af43f25341bbc4f6682987b06bbbd7ad-fee88d9788ad7868.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:04:16Z"
    - latency: 4.246621ms
      message: 'load-balancer-api-external: tcp connection to af43f25341bbc4f6682987b06bbbd7ad-fee88d9788ad7868.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:03:16Z"
    - latency: 7.013599ms
      message: 'load-balancer-api-external: resolved host name af43f25341bbc4f6682987b06bbbd7ad-fee88d9788ad7868.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:03:16Z"
    - latency: 4.747762ms
      message: 'load-balancer-api-external: tcp connection to af43f25341bbc4f6682987b06bbbd7ad-fee88d9788ad7868.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:02:16Z"
    - latency: 6.541926ms
      message: 'load-balancer-api-external: resolved host name af43f25341bbc4f6682987b06bbbd7ad-fee88d9788ad7868.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:02:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T17:00:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-118-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-118.ec2.internal
      uid: cf67ce39-3dec-4378-8c65-b1a39fafb7c6
    resourceVersion: "14239"
    uid: 48ed7275-f8bf-49be-b34c-2191aa5999e2
  spec:
    sourcePod: network-check-source-685456655f-4vfvs
    targetEndpoint: af43f25341bbc4f6682987b06bbbd7ad-fee88d9788ad7868.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T17:06:16Z"
      message: 'load-balancer-api-internal: tcp connection to af43f25341bbc4f6682987b06bbbd7ad-fee88d9788ad7868.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.793116ms
      message: 'load-balancer-api-internal: tcp connection to af43f25341bbc4f6682987b06bbbd7ad-fee88d9788ad7868.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:06:16Z"
    - latency: 5.807893ms
      message: 'load-balancer-api-internal: resolved host name af43f25341bbc4f6682987b06bbbd7ad-fee88d9788ad7868.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:06:16Z"
    - latency: 4.443789ms
      message: 'load-balancer-api-internal: tcp connection to af43f25341bbc4f6682987b06bbbd7ad-fee88d9788ad7868.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:05:16Z"
    - latency: 7.223932ms
      message: 'load-balancer-api-internal: resolved host name af43f25341bbc4f6682987b06bbbd7ad-fee88d9788ad7868.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:05:16Z"
    - latency: 4.332924ms
      message: 'load-balancer-api-internal: tcp connection to af43f25341bbc4f6682987b06bbbd7ad-fee88d9788ad7868.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:04:16Z"
    - latency: 7.404274ms
      message: 'load-balancer-api-internal: resolved host name af43f25341bbc4f6682987b06bbbd7ad-fee88d9788ad7868.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:04:16Z"
    - latency: 4.261676ms
      message: 'load-balancer-api-internal: tcp connection to af43f25341bbc4f6682987b06bbbd7ad-fee88d9788ad7868.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:03:16Z"
    - latency: 6.979735ms
      message: 'load-balancer-api-internal: resolved host name af43f25341bbc4f6682987b06bbbd7ad-fee88d9788ad7868.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:03:16Z"
    - latency: 6.76747ms
      message: 'load-balancer-api-internal: tcp connection to af43f25341bbc4f6682987b06bbbd7ad-fee88d9788ad7868.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:02:16Z"
    - latency: 6.489219ms
      message: 'load-balancer-api-internal: resolved host name af43f25341bbc4f6682987b06bbbd7ad-fee88d9788ad7868.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:02:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T17:00:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-118-to-network-check-target-ip-10-0-136-113
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-118.ec2.internal
      uid: cf67ce39-3dec-4378-8c65-b1a39fafb7c6
    resourceVersion: "14586"
    uid: 5e89df2a-69f1-4190-9365-9f7216f04ef5
  spec:
    sourcePod: network-check-source-685456655f-4vfvs
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T17:07:16Z"
      message: 'network-check-target-ip-10-0-136-113: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.131733ms
      message: 'network-check-target-ip-10-0-136-113: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:07:16Z"
    - latency: 2.320846ms
      message: 'network-check-target-ip-10-0-136-113: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:06:16Z"
    - latency: 1.951747ms
      message: 'network-check-target-ip-10-0-136-113: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:05:16Z"
    - latency: 2.877847ms
      message: 'network-check-target-ip-10-0-136-113: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:04:16Z"
    - latency: 1.877371ms
      message: 'network-check-target-ip-10-0-136-113: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:03:16Z"
    - latency: 2.1862ms
      message: 'network-check-target-ip-10-0-136-113: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:02:16Z"
    - latency: 2.277356ms
      message: 'network-check-target-ip-10-0-136-113: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:01:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T17:00:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-118-to-network-check-target-ip-10-0-141-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-118.ec2.internal
      uid: cf67ce39-3dec-4378-8c65-b1a39fafb7c6
    resourceVersion: "14584"
    uid: ffa02401-507a-4bf8-a226-cd3050fa3e1a
  spec:
    sourcePod: network-check-source-685456655f-4vfvs
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T17:07:16Z"
      message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 797.429µs
      message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:07:16Z"
    - latency: 833.706µs
      message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:06:16Z"
    - latency: 804.334µs
      message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:05:16Z"
    - latency: 1.547292ms
      message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:04:16Z"
    - latency: 824.079µs
      message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:03:16Z"
    - latency: 1.149277ms
      message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:02:16Z"
    - latency: 1.063432ms
      message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:01:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T17:00:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-118-to-network-check-target-ip-10-0-142-120
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-118.ec2.internal
      uid: cf67ce39-3dec-4378-8c65-b1a39fafb7c6
    resourceVersion: "14585"
    uid: c19b4192-c20d-4716-aceb-792b6d6ad362
  spec:
    sourcePod: network-check-source-685456655f-4vfvs
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T17:07:16Z"
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.078041ms
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:07:16Z"
    - latency: 1.81847ms
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:06:16Z"
    - latency: 1.594084ms
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:05:16Z"
    - latency: 2.472971ms
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:04:16Z"
    - latency: 1.944028ms
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:03:16Z"
    - latency: 2.129094ms
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:02:16Z"
    - latency: 2.117882ms
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:01:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T17:00:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-118-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-118.ec2.internal
      uid: cf67ce39-3dec-4378-8c65-b1a39fafb7c6
    resourceVersion: "14238"
    uid: a2724ed5-34fc-4316-a452-6881d2c40222
  spec:
    sourcePod: network-check-source-685456655f-4vfvs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T17:06:16Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 893.565µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:06:16Z"
    - latency: 1.637138ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:06:16Z"
    - latency: 1.078705ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:05:16Z"
    - latency: 1.757761ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:05:16Z"
    - latency: 828.63µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:04:16Z"
    - latency: 2.96446ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:04:16Z"
    - latency: 1.060147ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:03:16Z"
    - latency: 1.727175ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:03:16Z"
    - latency: 747.354µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:02:16Z"
    - latency: 1.881682ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:02:16Z"
kind: List
metadata:
  resourceVersion: ""