apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T09:45:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-85-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-85.us-west-1.compute.internal
      uid: a2dc77a5-ad00-4f4c-a8f2-35174bb6a5c4
    resourceVersion: "9142"
    uid: 7fa56869-1fd3-49c6-8c1d-a8c3dc2da3ae
  spec:
    sourcePod: network-check-source-6f78d59f99-v22vc
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T09:45:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-85-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-85.us-west-1.compute.internal
      uid: a2dc77a5-ad00-4f4c-a8f2-35174bb6a5c4
    resourceVersion: "11492"
    uid: 28520794-ae18-4fb3-9701-f54cde36fd86
  spec:
    sourcePod: network-check-source-6f78d59f99-v22vc
    targetEndpoint: ae77c517c671543e1af94a948b03cada-515b92ea84ba2b73.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T09:51:22Z"
      message: 'load-balancer-api-external: tcp connection to ae77c517c671543e1af94a948b03cada-515b92ea84ba2b73.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 53.947199ms
      message: 'load-balancer-api-external: tcp connection to ae77c517c671543e1af94a948b03cada-515b92ea84ba2b73.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:51:21Z"
    - latency: 11.031159ms
      message: 'load-balancer-api-external: resolved host name ae77c517c671543e1af94a948b03cada-515b92ea84ba2b73.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:51:21Z"
    - latency: 53.561174ms
      message: 'load-balancer-api-external: tcp connection to ae77c517c671543e1af94a948b03cada-515b92ea84ba2b73.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:50:21Z"
    - latency: 7.510022ms
      message: 'load-balancer-api-external: resolved host name ae77c517c671543e1af94a948b03cada-515b92ea84ba2b73.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:50:21Z"
    - latency: 55.25213ms
      message: 'load-balancer-api-external: tcp connection to ae77c517c671543e1af94a948b03cada-515b92ea84ba2b73.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:49:21Z"
    - latency: 7.472648ms
      message: 'load-balancer-api-external: resolved host name ae77c517c671543e1af94a948b03cada-515b92ea84ba2b73.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:49:21Z"
    - latency: 53.647168ms
      message: 'load-balancer-api-external: tcp connection to ae77c517c671543e1af94a948b03cada-515b92ea84ba2b73.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:48:21Z"
    - latency: 8.235804ms
      message: 'load-balancer-api-external: resolved host name ae77c517c671543e1af94a948b03cada-515b92ea84ba2b73.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:48:21Z"
    - latency: 53.809625ms
      message: 'load-balancer-api-external: tcp connection to ae77c517c671543e1af94a948b03cada-515b92ea84ba2b73.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:47:21Z"
    - latency: 7.609211ms
      message: 'load-balancer-api-external: resolved host name ae77c517c671543e1af94a948b03cada-515b92ea84ba2b73.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:47:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T09:45:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-85-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-85.us-west-1.compute.internal
      uid: a2dc77a5-ad00-4f4c-a8f2-35174bb6a5c4
    resourceVersion: "11493"
    uid: c8dbc827-1915-45fa-91da-9868c30ab062
  spec:
    sourcePod: network-check-source-6f78d59f99-v22vc
    targetEndpoint: ae77c517c671543e1af94a948b03cada-515b92ea84ba2b73.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T09:51:22Z"
      message: 'load-balancer-api-internal: tcp connection to ae77c517c671543e1af94a948b03cada-515b92ea84ba2b73.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 53.967623ms
      message: 'load-balancer-api-internal: tcp connection to ae77c517c671543e1af94a948b03cada-515b92ea84ba2b73.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:51:21Z"
    - latency: 11.111254ms
      message: 'load-balancer-api-internal: resolved host name ae77c517c671543e1af94a948b03cada-515b92ea84ba2b73.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:51:21Z"
    - latency: 54.289555ms
      message: 'load-balancer-api-internal: tcp connection to ae77c517c671543e1af94a948b03cada-515b92ea84ba2b73.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:50:21Z"
    - latency: 7.559881ms
      message: 'load-balancer-api-internal: resolved host name ae77c517c671543e1af94a948b03cada-515b92ea84ba2b73.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:50:21Z"
    - latency: 55.271627ms
      message: 'load-balancer-api-internal: tcp connection to ae77c517c671543e1af94a948b03cada-515b92ea84ba2b73.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:49:21Z"
    - latency: 7.542965ms
      message: 'load-balancer-api-internal: resolved host name ae77c517c671543e1af94a948b03cada-515b92ea84ba2b73.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:49:21Z"
    - latency: 55.130211ms
      message: 'load-balancer-api-internal: tcp connection to ae77c517c671543e1af94a948b03cada-515b92ea84ba2b73.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:48:21Z"
    - latency: 8.169969ms
      message: 'load-balancer-api-internal: resolved host name ae77c517c671543e1af94a948b03cada-515b92ea84ba2b73.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:48:21Z"
    - latency: 53.770642ms
      message: 'load-balancer-api-internal: tcp connection to ae77c517c671543e1af94a948b03cada-515b92ea84ba2b73.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:47:21Z"
    - latency: 7.594336ms
      message: 'load-balancer-api-internal: resolved host name ae77c517c671543e1af94a948b03cada-515b92ea84ba2b73.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:47:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T09:45:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-85-to-network-check-target-ip-10-0-132-94
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-85.us-west-1.compute.internal
      uid: a2dc77a5-ad00-4f4c-a8f2-35174bb6a5c4
    resourceVersion: "9148"
    uid: 7c3464d9-18bd-44a0-ae32-ab03ddb59096
  spec:
    sourcePod: network-check-source-6f78d59f99-v22vc
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T09:45:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-85-to-network-check-target-ip-10-0-139-242
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-85.us-west-1.compute.internal
      uid: a2dc77a5-ad00-4f4c-a8f2-35174bb6a5c4
    resourceVersion: "9149"
    uid: 1e7e9b1d-1d84-4d1d-bb0a-d97b29939373
  spec:
    sourcePod: network-check-source-6f78d59f99-v22vc
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T09:45:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-85-to-network-check-target-ip-10-0-140-85
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-85.us-west-1.compute.internal
      uid: a2dc77a5-ad00-4f4c-a8f2-35174bb6a5c4
    resourceVersion: "9146"
    uid: 188e6c66-aec4-413a-b69c-9bc63ecdf3f6
  spec:
    sourcePod: network-check-source-6f78d59f99-v22vc
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T09:45:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-85-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-85.us-west-1.compute.internal
      uid: a2dc77a5-ad00-4f4c-a8f2-35174bb6a5c4
    resourceVersion: "11491"
    uid: 8ea679c0-670a-4c70-a387-fb8fc8ed9380
  spec:
    sourcePod: network-check-source-6f78d59f99-v22vc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T09:51:21Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.186716ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:51:21Z"
    - latency: 3.377717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:51:21Z"
    - latency: 1.025763ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:50:21Z"
    - latency: 1.705946ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:50:21Z"
    - latency: 1.332131ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:49:21Z"
    - latency: 1.770243ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:49:21Z"
    - latency: 726.073µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:48:21Z"
    - latency: 1.608778ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:48:21Z"
    - latency: 934.295µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:47:21Z"
    - latency: 1.864726ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:47:21Z"
kind: List
metadata:
  resourceVersion: ""