apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:27:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-40-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-40.ec2.internal
      uid: a59bdddd-e39a-44cd-8489-8ac7e7ce2db6
    resourceVersion: "15718"
    uid: 16ce9f1a-25ec-44ea-88b7-c16b0db81ded
  spec:
    sourcePod: network-check-source-7cbc45fddc-w25zz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T08:35:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.055836ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:35:00Z"
    - latency: 1.035907ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:34:00Z"
    - latency: 900.822µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:33:00Z"
    - latency: 1.148007ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:32:00Z"
    - latency: 1.178686ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:31:00Z"
    - latency: 1.378825ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:30:00Z"
    - latency: 918.628µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:29:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:27:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-40-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-40.ec2.internal
      uid: a59bdddd-e39a-44cd-8489-8ac7e7ce2db6
    resourceVersion: "15217"
    uid: 5e1c7b9b-ba62-44c7-be79-b17117a3ba6e
  spec:
    sourcePod: network-check-source-7cbc45fddc-w25zz
    targetEndpoint: a836748e95291428aa6c7b543851553c-881c57cec811fec1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T08:34:00Z"
      message: 'load-balancer-api-external: tcp connection to a836748e95291428aa6c7b543851553c-881c57cec811fec1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.389284ms
      message: 'load-balancer-api-external: tcp connection to a836748e95291428aa6c7b543851553c-881c57cec811fec1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:34:00Z"
    - latency: 8.20875ms
      message: 'load-balancer-api-external: resolved host name a836748e95291428aa6c7b543851553c-881c57cec811fec1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:34:00Z"
    - latency: 6.328454ms
      message: 'load-balancer-api-external: tcp connection to a836748e95291428aa6c7b543851553c-881c57cec811fec1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:33:00Z"
    - latency: 11.229791ms
      message: 'load-balancer-api-external: resolved host name a836748e95291428aa6c7b543851553c-881c57cec811fec1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:33:00Z"
    - latency: 6.837746ms
      message: 'load-balancer-api-external: tcp connection to a836748e95291428aa6c7b543851553c-881c57cec811fec1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:32:00Z"
    - latency: 10.174725ms
      message: 'load-balancer-api-external: resolved host name a836748e95291428aa6c7b543851553c-881c57cec811fec1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:32:00Z"
    - latency: 5.631309ms
      message: 'load-balancer-api-external: tcp connection to a836748e95291428aa6c7b543851553c-881c57cec811fec1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:31:00Z"
    - latency: 9.249296ms
      message: 'load-balancer-api-external: resolved host name a836748e95291428aa6c7b543851553c-881c57cec811fec1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:31:00Z"
    - latency: 5.642364ms
      message: 'load-balancer-api-external: tcp connection to a836748e95291428aa6c7b543851553c-881c57cec811fec1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:30:00Z"
    - latency: 13.569804ms
      message: 'load-balancer-api-external: resolved host name a836748e95291428aa6c7b543851553c-881c57cec811fec1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:30:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:27:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-40-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-40.ec2.internal
      uid: a59bdddd-e39a-44cd-8489-8ac7e7ce2db6
    resourceVersion: "15218"
    uid: 90ead9fa-a05a-4f43-a413-225cd0271287
  spec:
    sourcePod: network-check-source-7cbc45fddc-w25zz
    targetEndpoint: a836748e95291428aa6c7b543851553c-881c57cec811fec1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T08:34:00Z"
      message: 'load-balancer-api-internal: tcp connection to a836748e95291428aa6c7b543851553c-881c57cec811fec1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.235884ms
      message: 'load-balancer-api-internal: tcp connection to a836748e95291428aa6c7b543851553c-881c57cec811fec1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:34:00Z"
    - latency: 8.134057ms
      message: 'load-balancer-api-internal: resolved host name a836748e95291428aa6c7b543851553c-881c57cec811fec1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:34:00Z"
    - latency: 6.36418ms
      message: 'load-balancer-api-internal: tcp connection to a836748e95291428aa6c7b543851553c-881c57cec811fec1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:33:00Z"
    - latency: 11.204ms
      message: 'load-balancer-api-internal: resolved host name a836748e95291428aa6c7b543851553c-881c57cec811fec1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:33:00Z"
    - latency: 6.82238ms
      message: 'load-balancer-api-internal: tcp connection to a836748e95291428aa6c7b543851553c-881c57cec811fec1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:32:00Z"
    - latency: 10.242532ms
      message: 'load-balancer-api-internal: resolved host name a836748e95291428aa6c7b543851553c-881c57cec811fec1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:32:00Z"
    - latency: 5.652713ms
      message: 'load-balancer-api-internal: tcp connection to a836748e95291428aa6c7b543851553c-881c57cec811fec1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:31:00Z"
    - latency: 9.312841ms
      message: 'load-balancer-api-internal: resolved host name a836748e95291428aa6c7b543851553c-881c57cec811fec1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:31:00Z"
    - latency: 5.638351ms
      message: 'load-balancer-api-internal: tcp connection to a836748e95291428aa6c7b543851553c-881c57cec811fec1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:30:00Z"
    - latency: 13.497746ms
      message: 'load-balancer-api-internal: resolved host name a836748e95291428aa6c7b543851553c-881c57cec811fec1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:30:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:27:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-40-to-network-check-target-ip-10-0-134-145
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-40.ec2.internal
      uid: a59bdddd-e39a-44cd-8489-8ac7e7ce2db6
    resourceVersion: "15716"
    uid: b28d1200-7f8a-46a8-9b0f-182cb2c72a5b
  spec:
    sourcePod: network-check-source-7cbc45fddc-w25zz
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T08:35:00Z"
      message: 'network-check-target-ip-10-0-134-145: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.365321ms
      message: 'network-check-target-ip-10-0-134-145: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:35:00Z"
    - latency: 2.295041ms
      message: 'network-check-target-ip-10-0-134-145: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:34:00Z"
    - latency: 2.154959ms
      message: 'network-check-target-ip-10-0-134-145: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:33:00Z"
    - latency: 2.689482ms
      message: 'network-check-target-ip-10-0-134-145: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:32:00Z"
    - latency: 5.034146ms
      message: 'network-check-target-ip-10-0-134-145: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:31:00Z"
    - latency: 2.753683ms
      message: 'network-check-target-ip-10-0-134-145: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:30:00Z"
    - latency: 2.561796ms
      message: 'network-check-target-ip-10-0-134-145: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:29:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:27:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-40-to-network-check-target-ip-10-0-135-107
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-40.ec2.internal
      uid: a59bdddd-e39a-44cd-8489-8ac7e7ce2db6
    resourceVersion: "15717"
    uid: 5dadce1b-2f17-4519-9a75-e32f098f4c2e
  spec:
    sourcePod: network-check-source-7cbc45fddc-w25zz
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T08:35:00Z"
      message: 'network-check-target-ip-10-0-135-107: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.4291ms
      message: 'network-check-target-ip-10-0-135-107: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:35:00Z"
    - latency: 1.83625ms
      message: 'network-check-target-ip-10-0-135-107: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:34:00Z"
    - latency: 2.101582ms
      message: 'network-check-target-ip-10-0-135-107: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:33:00Z"
    - latency: 2.422115ms
      message: 'network-check-target-ip-10-0-135-107: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:32:00Z"
    - latency: 2.107502ms
      message: 'network-check-target-ip-10-0-135-107: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:31:00Z"
    - latency: 2.815463ms
      message: 'network-check-target-ip-10-0-135-107: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:30:00Z"
    - latency: 2.07672ms
      message: 'network-check-target-ip-10-0-135-107: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:29:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:27:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-40-to-network-check-target-ip-10-0-137-40
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-40.ec2.internal
      uid: a59bdddd-e39a-44cd-8489-8ac7e7ce2db6
    resourceVersion: "15715"
    uid: edd27d02-c192-42ab-a127-e33c45da9859
  spec:
    sourcePod: network-check-source-7cbc45fddc-w25zz
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T08:35:00Z"
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.392345ms
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:35:00Z"
    - latency: 821.006µs
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:34:00Z"
    - latency: 1.133598ms
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:33:00Z"
    - latency: 1.879717ms
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:32:00Z"
    - latency: 1.728243ms
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:31:00Z"
    - latency: 904.112µs
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:30:00Z"
    - latency: 1.240795ms
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:29:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:27:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-40-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-40.ec2.internal
      uid: a59bdddd-e39a-44cd-8489-8ac7e7ce2db6
    resourceVersion: "15216"
    uid: 0dcc5bf2-8417-4376-9077-14285fd1b101
  spec:
    sourcePod: network-check-source-7cbc45fddc-w25zz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T08:34:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.145579ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:34:00Z"
    - latency: 1.895746ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:34:00Z"
    - latency: 775.708µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:33:00Z"
    - latency: 1.87306ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:33:00Z"
    - latency: 1.673795ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:32:00Z"
    - latency: 2.437537ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:32:00Z"
    - latency: 3.866068ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:31:00Z"
    - latency: 1.823962ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:31:00Z"
    - latency: 5.19142ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:30:00Z"
    - latency: 2.451871ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:30:00Z"
kind: List
metadata:
  resourceVersion: ""