apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T14:40:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-171-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-171.ec2.internal
      uid: 8d293e4d-1426-48f7-a2e6-d5e81028546b
    resourceVersion: "24349"
    uid: 74df7b8a-7508-44ee-9d22-45efa90aad30
  spec:
    sourcePod: network-check-source-8894fc9bd-rl7lx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T14:47:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.314088ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:47:04Z"
    - latency: 1.127733ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:46:04Z"
    - latency: 1.318783ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:45:04Z"
    - latency: 957.22µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:44:04Z"
    - latency: 918.5µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:43:04Z"
    - latency: 1.059459ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:42:04Z"
    - latency: 1.206875ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:41:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T14:40:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-171-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-171.ec2.internal
      uid: 8d293e4d-1426-48f7-a2e6-d5e81028546b
    resourceVersion: "23159"
    uid: 6ba6a1bf-5238-493a-b208-3e058c8317c6
  spec:
    sourcePod: network-check-source-8894fc9bd-rl7lx
    targetEndpoint: a126d8bebd8664501883e6b6ecb1c633-d7a34a0e3441c3ff.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T14:46:04Z"
      message: 'load-balancer-api-external: tcp connection to a126d8bebd8664501883e6b6ecb1c633-d7a34a0e3441c3ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.859519ms
      message: 'load-balancer-api-external: tcp connection to a126d8bebd8664501883e6b6ecb1c633-d7a34a0e3441c3ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:46:04Z"
    - latency: 9.072654ms
      message: 'load-balancer-api-external: resolved host name a126d8bebd8664501883e6b6ecb1c633-d7a34a0e3441c3ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:46:04Z"
    - latency: 4.336061ms
      message: 'load-balancer-api-external: tcp connection to a126d8bebd8664501883e6b6ecb1c633-d7a34a0e3441c3ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:45:04Z"
    - latency: 8.885027ms
      message: 'load-balancer-api-external: resolved host name a126d8bebd8664501883e6b6ecb1c633-d7a34a0e3441c3ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:45:04Z"
    - latency: 4.693283ms
      message: 'load-balancer-api-external: tcp connection to a126d8bebd8664501883e6b6ecb1c633-d7a34a0e3441c3ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:44:04Z"
    - latency: 7.51938ms
      message: 'load-balancer-api-external: resolved host name a126d8bebd8664501883e6b6ecb1c633-d7a34a0e3441c3ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:44:04Z"
    - latency: 5.276094ms
      message: 'load-balancer-api-external: tcp connection to a126d8bebd8664501883e6b6ecb1c633-d7a34a0e3441c3ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:43:04Z"
    - latency: 9.824148ms
      message: 'load-balancer-api-external: resolved host name a126d8bebd8664501883e6b6ecb1c633-d7a34a0e3441c3ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:43:04Z"
    - latency: 5.629207ms
      message: 'load-balancer-api-external: tcp connection to a126d8bebd8664501883e6b6ecb1c633-d7a34a0e3441c3ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:42:04Z"
    - latency: 8.405382ms
      message: 'load-balancer-api-external: resolved host name a126d8bebd8664501883e6b6ecb1c633-d7a34a0e3441c3ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:42:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T14:40:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-171-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-171.ec2.internal
      uid: 8d293e4d-1426-48f7-a2e6-d5e81028546b
    resourceVersion: "23158"
    uid: 23fa9971-6ad8-47c7-9894-74b69fd68d9b
  spec:
    sourcePod: network-check-source-8894fc9bd-rl7lx
    targetEndpoint: a126d8bebd8664501883e6b6ecb1c633-d7a34a0e3441c3ff.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T14:46:04Z"
      message: 'load-balancer-api-internal: tcp connection to a126d8bebd8664501883e6b6ecb1c633-d7a34a0e3441c3ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.864382ms
      message: 'load-balancer-api-internal: tcp connection to a126d8bebd8664501883e6b6ecb1c633-d7a34a0e3441c3ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:46:04Z"
    - latency: 9.055554ms
      message: 'load-balancer-api-internal: resolved host name a126d8bebd8664501883e6b6ecb1c633-d7a34a0e3441c3ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:46:04Z"
    - latency: 4.310564ms
      message: 'load-balancer-api-internal: tcp connection to a126d8bebd8664501883e6b6ecb1c633-d7a34a0e3441c3ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:45:04Z"
    - latency: 8.803262ms
      message: 'load-balancer-api-internal: resolved host name a126d8bebd8664501883e6b6ecb1c633-d7a34a0e3441c3ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:45:04Z"
    - latency: 4.722736ms
      message: 'load-balancer-api-internal: tcp connection to a126d8bebd8664501883e6b6ecb1c633-d7a34a0e3441c3ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:44:04Z"
    - latency: 7.584324ms
      message: 'load-balancer-api-internal: resolved host name a126d8bebd8664501883e6b6ecb1c633-d7a34a0e3441c3ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:44:04Z"
    - latency: 5.26579ms
      message: 'load-balancer-api-internal: tcp connection to a126d8bebd8664501883e6b6ecb1c633-d7a34a0e3441c3ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:43:04Z"
    - latency: 9.942571ms
      message: 'load-balancer-api-internal: resolved host name a126d8bebd8664501883e6b6ecb1c633-d7a34a0e3441c3ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:43:04Z"
    - latency: 5.720234ms
      message: 'load-balancer-api-internal: tcp connection to a126d8bebd8664501883e6b6ecb1c633-d7a34a0e3441c3ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:42:04Z"
    - latency: 8.477747ms
      message: 'load-balancer-api-internal: resolved host name a126d8bebd8664501883e6b6ecb1c633-d7a34a0e3441c3ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:42:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T14:40:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-171-to-network-check-target-ip-10-0-129-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-171.ec2.internal
      uid: 8d293e4d-1426-48f7-a2e6-d5e81028546b
    resourceVersion: "24347"
    uid: a2434b97-7e84-4ce7-a67c-bb0dc6ed6adb
  spec:
    sourcePod: network-check-source-8894fc9bd-rl7lx
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T14:47:04Z"
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.14795ms
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:47:04Z"
    - latency: 2.370743ms
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:46:04Z"
    - latency: 1.759807ms
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:45:04Z"
    - latency: 2.242602ms
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:44:04Z"
    - latency: 2.022109ms
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:43:04Z"
    - latency: 2.103714ms
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:42:04Z"
    - latency: 2.186031ms
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:41:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T14:40:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-171-to-network-check-target-ip-10-0-135-180
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-171.ec2.internal
      uid: 8d293e4d-1426-48f7-a2e6-d5e81028546b
    resourceVersion: "24348"
    uid: 73d951d0-7daa-47a6-a910-ddfef3e45605
  spec:
    sourcePod: network-check-source-8894fc9bd-rl7lx
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T14:47:04Z"
      message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.094605ms
      message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:47:04Z"
    - latency: 1.822759ms
      message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:46:04Z"
    - latency: 1.938476ms
      message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:45:04Z"
    - latency: 1.745206ms
      message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:44:04Z"
    - latency: 1.734017ms
      message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:43:04Z"
    - latency: 1.816811ms
      message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:42:04Z"
    - latency: 2.030865ms
      message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:41:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T14:40:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-171-to-network-check-target-ip-10-0-143-171
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-171.ec2.internal
      uid: 8d293e4d-1426-48f7-a2e6-d5e81028546b
    resourceVersion: "24346"
    uid: 5827a7b4-363a-4c04-b006-d9f91144ec38
  spec:
    sourcePod: network-check-source-8894fc9bd-rl7lx
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T14:47:04Z"
      message: 'network-check-target-ip-10-0-143-171: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 935.556µs
      message: 'network-check-target-ip-10-0-143-171: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:47:04Z"
    - latency: 1.749992ms
      message: 'network-check-target-ip-10-0-143-171: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:46:04Z"
    - latency: 1.531969ms
      message: 'network-check-target-ip-10-0-143-171: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:45:04Z"
    - latency: 928.598µs
      message: 'network-check-target-ip-10-0-143-171: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:44:04Z"
    - latency: 1.359318ms
      message: 'network-check-target-ip-10-0-143-171: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:43:04Z"
    - latency: 1.206364ms
      message: 'network-check-target-ip-10-0-143-171: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:42:04Z"
    - latency: 1.094689ms
      message: 'network-check-target-ip-10-0-143-171: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:41:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T14:40:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-171-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-171.ec2.internal
      uid: 8d293e4d-1426-48f7-a2e6-d5e81028546b
    resourceVersion: "23156"
    uid: e02f3418-5cac-4edd-82d0-d627263d3320
  spec:
    sourcePod: network-check-source-8894fc9bd-rl7lx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T14:46:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 822.794µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:46:04Z"
    - latency: 2.199412ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:46:04Z"
    - latency: 834.796µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:45:04Z"
    - latency: 1.896686ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:45:04Z"
    - latency: 910.39µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:44:04Z"
    - latency: 1.796567ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:44:04Z"
    - latency: 1.077514ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:43:04Z"
    - latency: 1.502998ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:43:04Z"
    - latency: 949.594µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:42:04Z"
    - latency: 1.809721ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:42:04Z"
kind: List
metadata:
  resourceVersion: ""