apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T14:44:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-182-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-182.ec2.internal
      uid: 7384d63e-ce1f-4cc5-ab74-09b843c76211
    resourceVersion: "14519"
    uid: 5bc07d3c-48ab-4ca9-9e29-789051be70fe
  spec:
    sourcePod: network-check-source-685456655f-wsvm4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T14:51:41Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.149045ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:51:41Z"
    - latency: 990.37µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:50:41Z"
    - latency: 1.051971ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:49:41Z"
    - latency: 1.651208ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:48:41Z"
    - latency: 1.118564ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:47:41Z"
    - latency: 1.011989ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:46:41Z"
    - latency: 1.412814ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:45:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T14:44:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-182-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-182.ec2.internal
      uid: 7384d63e-ce1f-4cc5-ab74-09b843c76211
    resourceVersion: "14178"
    uid: 2524ec33-90c0-4389-9681-5e50e7e81e48
  spec:
    sourcePod: network-check-source-685456655f-wsvm4
    targetEndpoint: ab3515a6b27f54b3982b4837d687fd8a-6a56b1c542d07467.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T14:50:41Z"
      message: 'load-balancer-api-external: tcp connection to ab3515a6b27f54b3982b4837d687fd8a-6a56b1c542d07467.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.235754ms
      message: 'load-balancer-api-external: tcp connection to ab3515a6b27f54b3982b4837d687fd8a-6a56b1c542d07467.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:50:41Z"
    - latency: 6.842526ms
      message: 'load-balancer-api-external: resolved host name ab3515a6b27f54b3982b4837d687fd8a-6a56b1c542d07467.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:50:41Z"
    - latency: 4.722621ms
      message: 'load-balancer-api-external: tcp connection to ab3515a6b27f54b3982b4837d687fd8a-6a56b1c542d07467.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:49:41Z"
    - latency: 6.914879ms
      message: 'load-balancer-api-external: resolved host name ab3515a6b27f54b3982b4837d687fd8a-6a56b1c542d07467.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:49:41Z"
    - latency: 6.057752ms
      message: 'load-balancer-api-external: tcp connection to ab3515a6b27f54b3982b4837d687fd8a-6a56b1c542d07467.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:48:41Z"
    - latency: 7.416712ms
      message: 'load-balancer-api-external: resolved host name ab3515a6b27f54b3982b4837d687fd8a-6a56b1c542d07467.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:48:41Z"
    - latency: 3.659087ms
      message: 'load-balancer-api-external: tcp connection to ab3515a6b27f54b3982b4837d687fd8a-6a56b1c542d07467.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:47:41Z"
    - latency: 6.854851ms
      message: 'load-balancer-api-external: resolved host name ab3515a6b27f54b3982b4837d687fd8a-6a56b1c542d07467.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:47:41Z"
    - latency: 5.253059ms
      message: 'load-balancer-api-external: tcp connection to ab3515a6b27f54b3982b4837d687fd8a-6a56b1c542d07467.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:46:41Z"
    - latency: 8.94273ms
      message: 'load-balancer-api-external: resolved host name ab3515a6b27f54b3982b4837d687fd8a-6a56b1c542d07467.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:46:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T14:44:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-182-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-182.ec2.internal
      uid: 7384d63e-ce1f-4cc5-ab74-09b843c76211
    resourceVersion: "14179"
    uid: 016bc732-633c-4f3f-9f3d-0e1252db6507
  spec:
    sourcePod: network-check-source-685456655f-wsvm4
    targetEndpoint: ab3515a6b27f54b3982b4837d687fd8a-6a56b1c542d07467.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T14:50:41Z"
      message: 'load-balancer-api-internal: tcp connection to ab3515a6b27f54b3982b4837d687fd8a-6a56b1c542d07467.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.230932ms
      message: 'load-balancer-api-internal: tcp connection to ab3515a6b27f54b3982b4837d687fd8a-6a56b1c542d07467.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:50:41Z"
    - latency: 6.766499ms
      message: 'load-balancer-api-internal: resolved host name ab3515a6b27f54b3982b4837d687fd8a-6a56b1c542d07467.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:50:41Z"
    - latency: 4.773971ms
      message: 'load-balancer-api-internal: tcp connection to ab3515a6b27f54b3982b4837d687fd8a-6a56b1c542d07467.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:49:41Z"
    - latency: 6.817331ms
      message: 'load-balancer-api-internal: resolved host name ab3515a6b27f54b3982b4837d687fd8a-6a56b1c542d07467.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:49:41Z"
    - latency: 6.045771ms
      message: 'load-balancer-api-internal: tcp connection to ab3515a6b27f54b3982b4837d687fd8a-6a56b1c542d07467.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:48:41Z"
    - latency: 7.382326ms
      message: 'load-balancer-api-internal: resolved host name ab3515a6b27f54b3982b4837d687fd8a-6a56b1c542d07467.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:48:41Z"
    - latency: 4.403182ms
      message: 'load-balancer-api-internal: tcp connection to ab3515a6b27f54b3982b4837d687fd8a-6a56b1c542d07467.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:47:41Z"
    - latency: 6.754425ms
      message: 'load-balancer-api-internal: resolved host name ab3515a6b27f54b3982b4837d687fd8a-6a56b1c542d07467.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:47:41Z"
    - latency: 5.296003ms
      message: 'load-balancer-api-internal: tcp connection to ab3515a6b27f54b3982b4837d687fd8a-6a56b1c542d07467.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:46:41Z"
    - latency: 8.883327ms
      message: 'load-balancer-api-internal: resolved host name ab3515a6b27f54b3982b4837d687fd8a-6a56b1c542d07467.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:46:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T14:44:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-182-to-network-check-target-ip-10-0-128-182
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-182.ec2.internal
      uid: 7384d63e-ce1f-4cc5-ab74-09b843c76211
    resourceVersion: "14522"
    uid: 53db075d-bfd1-4dd1-9da8-43767e571130
  spec:
    sourcePod: network-check-source-685456655f-wsvm4
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T14:51:41Z"
      message: 'network-check-target-ip-10-0-128-182: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.196093ms
      message: 'network-check-target-ip-10-0-128-182: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:51:41Z"
    - latency: 1.002026ms
      message: 'network-check-target-ip-10-0-128-182: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:50:41Z"
    - latency: 997.401µs
      message: 'network-check-target-ip-10-0-128-182: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:49:41Z"
    - latency: 881.498µs
      message: 'network-check-target-ip-10-0-128-182: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:48:41Z"
    - latency: 945.003µs
      message: 'network-check-target-ip-10-0-128-182: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:47:41Z"
    - latency: 1.376548ms
      message: 'network-check-target-ip-10-0-128-182: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:46:41Z"
    - latency: 1.417615ms
      message: 'network-check-target-ip-10-0-128-182: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:45:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T14:44:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-182-to-network-check-target-ip-10-0-140-32
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-182.ec2.internal
      uid: 7384d63e-ce1f-4cc5-ab74-09b843c76211
    resourceVersion: "14521"
    uid: 80bf0358-b7c1-42b9-8afd-d256f02b741e
  spec:
    sourcePod: network-check-source-685456655f-wsvm4
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T14:51:41Z"
      message: 'network-check-target-ip-10-0-140-32: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.277288ms
      message: 'network-check-target-ip-10-0-140-32: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:51:41Z"
    - latency: 2.248829ms
      message: 'network-check-target-ip-10-0-140-32: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:50:41Z"
    - latency: 2.290974ms
      message: 'network-check-target-ip-10-0-140-32: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:49:41Z"
    - latency: 1.819726ms
      message: 'network-check-target-ip-10-0-140-32: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:48:41Z"
    - latency: 1.875726ms
      message: 'network-check-target-ip-10-0-140-32: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:47:41Z"
    - latency: 1.813836ms
      message: 'network-check-target-ip-10-0-140-32: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:46:41Z"
    - latency: 6.457576ms
      message: 'network-check-target-ip-10-0-140-32: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:45:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T14:44:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-182-to-network-check-target-ip-10-0-143-201
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-182.ec2.internal
      uid: 7384d63e-ce1f-4cc5-ab74-09b843c76211
    resourceVersion: "14520"
    uid: e2d17cfd-622f-4dd4-941e-2e6a810bd780
  spec:
    sourcePod: network-check-source-685456655f-wsvm4
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T14:51:41Z"
      message: 'network-check-target-ip-10-0-143-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.148069ms
      message: 'network-check-target-ip-10-0-143-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:51:41Z"
    - latency: 2.139939ms
      message: 'network-check-target-ip-10-0-143-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:50:41Z"
    - latency: 2.147163ms
      message: 'network-check-target-ip-10-0-143-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:49:41Z"
    - latency: 2.917449ms
      message: 'network-check-target-ip-10-0-143-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:48:41Z"
    - latency: 2.155587ms
      message: 'network-check-target-ip-10-0-143-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:47:41Z"
    - latency: 2.04958ms
      message: 'network-check-target-ip-10-0-143-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:46:41Z"
    - latency: 6.149989ms
      message: 'network-check-target-ip-10-0-143-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:45:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T14:44:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-182-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-182.ec2.internal
      uid: 7384d63e-ce1f-4cc5-ab74-09b843c76211
    resourceVersion: "14177"
    uid: 817f9613-fcfe-4683-a2b4-2cedc59d4637
  spec:
    sourcePod: network-check-source-685456655f-wsvm4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T14:50:41Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.086832ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:50:41Z"
    - latency: 1.852226ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:50:41Z"
    - latency: 1.01131ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:49:41Z"
    - latency: 1.818669ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:49:41Z"
    - latency: 913.324µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:48:41Z"
    - latency: 1.981921ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:48:41Z"
    - latency: 884.63µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:47:41Z"
    - latency: 1.909306ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:47:41Z"
    - latency: 887.675µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:46:41Z"
    - latency: 2.199547ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:46:41Z"
kind: List
metadata:
  resourceVersion: ""