apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:21:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-167-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-167.ec2.internal
      uid: 74c69651-2f43-4f45-938a-fd6198ce0d6b
    resourceVersion: "24249"
    uid: 4346ad27-34b1-4f6f-ae54-4d690584bb62
  spec:
    sourcePod: network-check-source-685456655f-7ghfc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:28:02Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 859.637µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:28:02Z"
    - latency: 941.915µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:27:02Z"
    - latency: 1.076821ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:26:02Z"
    - latency: 1.125879ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:25:02Z"
    - latency: 949.663µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:24:02Z"
    - latency: 1.52171ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:23:02Z"
    - latency: 924.45µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:22:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:21:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-167-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-167.ec2.internal
      uid: 74c69651-2f43-4f45-938a-fd6198ce0d6b
    resourceVersion: "23061"
    uid: 3cef5128-1ca3-4e3f-b820-e48fa6eb175b
  spec:
    sourcePod: network-check-source-685456655f-7ghfc
    targetEndpoint: a8292c9e047a345618b2fbd9d72b3914-7b0888a99a227633.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:27:02Z"
      message: 'load-balancer-api-external: tcp connection to a8292c9e047a345618b2fbd9d72b3914-7b0888a99a227633.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.366952ms
      message: 'load-balancer-api-external: tcp connection to a8292c9e047a345618b2fbd9d72b3914-7b0888a99a227633.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:27:02Z"
    - latency: 6.595497ms
      message: 'load-balancer-api-external: resolved host name a8292c9e047a345618b2fbd9d72b3914-7b0888a99a227633.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:27:02Z"
    - latency: 4.015518ms
      message: 'load-balancer-api-external: tcp connection to a8292c9e047a345618b2fbd9d72b3914-7b0888a99a227633.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:26:02Z"
    - latency: 8.295886ms
      message: 'load-balancer-api-external: resolved host name a8292c9e047a345618b2fbd9d72b3914-7b0888a99a227633.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:26:02Z"
    - latency: 6.120222ms
      message: 'load-balancer-api-external: tcp connection to a8292c9e047a345618b2fbd9d72b3914-7b0888a99a227633.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:25:02Z"
    - latency: 8.126434ms
      message: 'load-balancer-api-external: resolved host name a8292c9e047a345618b2fbd9d72b3914-7b0888a99a227633.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:25:02Z"
    - latency: 5.806007ms
      message: 'load-balancer-api-external: tcp connection to a8292c9e047a345618b2fbd9d72b3914-7b0888a99a227633.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:24:02Z"
    - latency: 7.359236ms
      message: 'load-balancer-api-external: resolved host name a8292c9e047a345618b2fbd9d72b3914-7b0888a99a227633.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:24:02Z"
    - latency: 4.955886ms
      message: 'load-balancer-api-external: tcp connection to a8292c9e047a345618b2fbd9d72b3914-7b0888a99a227633.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:23:02Z"
    - latency: 6.88268ms
      message: 'load-balancer-api-external: resolved host name a8292c9e047a345618b2fbd9d72b3914-7b0888a99a227633.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:23:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:21:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-167-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-167.ec2.internal
      uid: 74c69651-2f43-4f45-938a-fd6198ce0d6b
    resourceVersion: "23060"
    uid: df4e3a78-cb1e-4108-b93d-b24b03bde7f4
  spec:
    sourcePod: network-check-source-685456655f-7ghfc
    targetEndpoint: a8292c9e047a345618b2fbd9d72b3914-7b0888a99a227633.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:27:02Z"
      message: 'load-balancer-api-internal: tcp connection to a8292c9e047a345618b2fbd9d72b3914-7b0888a99a227633.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.350971ms
      message: 'load-balancer-api-internal: tcp connection to a8292c9e047a345618b2fbd9d72b3914-7b0888a99a227633.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:27:02Z"
    - latency: 6.527951ms
      message: 'load-balancer-api-internal: resolved host name a8292c9e047a345618b2fbd9d72b3914-7b0888a99a227633.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:27:02Z"
    - latency: 4.053757ms
      message: 'load-balancer-api-internal: tcp connection to a8292c9e047a345618b2fbd9d72b3914-7b0888a99a227633.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:26:02Z"
    - latency: 8.178957ms
      message: 'load-balancer-api-internal: resolved host name a8292c9e047a345618b2fbd9d72b3914-7b0888a99a227633.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:26:02Z"
    - latency: 6.052986ms
      message: 'load-balancer-api-internal: tcp connection to a8292c9e047a345618b2fbd9d72b3914-7b0888a99a227633.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:25:02Z"
    - latency: 8.151586ms
      message: 'load-balancer-api-internal: resolved host name a8292c9e047a345618b2fbd9d72b3914-7b0888a99a227633.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:25:02Z"
    - latency: 5.856832ms
      message: 'load-balancer-api-internal: tcp connection to a8292c9e047a345618b2fbd9d72b3914-7b0888a99a227633.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:24:02Z"
    - latency: 7.3031ms
      message: 'load-balancer-api-internal: resolved host name a8292c9e047a345618b2fbd9d72b3914-7b0888a99a227633.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:24:02Z"
    - latency: 4.971982ms
      message: 'load-balancer-api-internal: tcp connection to a8292c9e047a345618b2fbd9d72b3914-7b0888a99a227633.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:23:02Z"
    - latency: 6.816462ms
      message: 'load-balancer-api-internal: resolved host name a8292c9e047a345618b2fbd9d72b3914-7b0888a99a227633.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:23:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:21:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-167-to-network-check-target-ip-10-0-130-161
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-167.ec2.internal
      uid: 74c69651-2f43-4f45-938a-fd6198ce0d6b
    resourceVersion: "24247"
    uid: 5c19a34b-1e22-4d79-ae0e-6ed6facda17f
  spec:
    sourcePod: network-check-source-685456655f-7ghfc
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:28:02Z"
      message: 'network-check-target-ip-10-0-130-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.189833ms
      message: 'network-check-target-ip-10-0-130-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:28:02Z"
    - latency: 2.164257ms
      message: 'network-check-target-ip-10-0-130-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:27:02Z"
    - latency: 1.908862ms
      message: 'network-check-target-ip-10-0-130-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:26:02Z"
    - latency: 2.201077ms
      message: 'network-check-target-ip-10-0-130-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:25:02Z"
    - latency: 1.89449ms
      message: 'network-check-target-ip-10-0-130-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:24:02Z"
    - latency: 2.374115ms
      message: 'network-check-target-ip-10-0-130-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:23:02Z"
    - latency: 2.331996ms
      message: 'network-check-target-ip-10-0-130-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:22:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:21:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-167-to-network-check-target-ip-10-0-130-56
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-167.ec2.internal
      uid: 74c69651-2f43-4f45-938a-fd6198ce0d6b
    resourceVersion: "24248"
    uid: 39eb6940-0eca-450e-8059-a9921fb30fc3
  spec:
    sourcePod: network-check-source-685456655f-7ghfc
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:28:02Z"
      message: 'network-check-target-ip-10-0-130-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.459915ms
      message: 'network-check-target-ip-10-0-130-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:28:02Z"
    - latency: 2.542777ms
      message: 'network-check-target-ip-10-0-130-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:27:02Z"
    - latency: 2.313894ms
      message: 'network-check-target-ip-10-0-130-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:26:02Z"
    - latency: 2.606619ms
      message: 'network-check-target-ip-10-0-130-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:25:02Z"
    - latency: 2.160433ms
      message: 'network-check-target-ip-10-0-130-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:24:02Z"
    - latency: 2.98052ms
      message: 'network-check-target-ip-10-0-130-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:23:02Z"
    - latency: 2.258217ms
      message: 'network-check-target-ip-10-0-130-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:22:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:21:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-167-to-network-check-target-ip-10-0-142-167
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-167.ec2.internal
      uid: 74c69651-2f43-4f45-938a-fd6198ce0d6b
    resourceVersion: "24246"
    uid: 16eb3dc9-a560-417a-9548-0cea3c54977d
  spec:
    sourcePod: network-check-source-685456655f-7ghfc
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:28:02Z"
      message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 932.132µs
      message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:28:02Z"
    - latency: 1.589132ms
      message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:27:02Z"
    - latency: 987.462µs
      message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:26:02Z"
    - latency: 1.700894ms
      message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:25:02Z"
    - latency: 939.512µs
      message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:24:02Z"
    - latency: 1.499172ms
      message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:23:02Z"
    - latency: 1.555435ms
      message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:22:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:21:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-167-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-167.ec2.internal
      uid: 74c69651-2f43-4f45-938a-fd6198ce0d6b
    resourceVersion: "23059"
    uid: c776b499-6186-405d-ad62-0c86663f71ca
  spec:
    sourcePod: network-check-source-685456655f-7ghfc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:27:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 839.933µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:27:02Z"
    - latency: 1.660871ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:27:02Z"
    - latency: 786.695µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:26:02Z"
    - latency: 1.783575ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:26:02Z"
    - latency: 874.595µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:25:02Z"
    - latency: 2.052007ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:25:02Z"
    - latency: 1.030043ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:24:02Z"
    - latency: 1.9515ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:24:02Z"
    - latency: 1.136517ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:23:02Z"
    - latency: 2.446932ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:23:02Z"
kind: List
metadata:
  resourceVersion: ""