apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T14:43:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-102-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-102.ec2.internal
      uid: b3eb0a76-466b-4fbf-9211-b62a9df54e50
    resourceVersion: "14755"
    uid: c5051cd6-992a-4a1c-bb72-bd1e857fd25f
  spec:
    sourcePod: network-check-source-685456655f-sjhc8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T14:50:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 890.745µ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:20Z"
    - latency: 1.260317ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:49:20Z"
    - latency: 1.079838ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:48:20Z"
    - latency: 1.169024ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:47:20Z"
    - latency: 1.336925ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:46:20Z"
    - latency: 1.04671ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:45:20Z"
    - latency: 1.082142ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:44:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T14:43:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-102-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-102.ec2.internal
      uid: b3eb0a76-466b-4fbf-9211-b62a9df54e50
    resourceVersion: "14401"
    uid: 28d5f4a9-8b6f-42c4-8567-2fad42df761d
  spec:
    sourcePod: network-check-source-685456655f-sjhc8
    targetEndpoint: ab3fa825be2964f47b4f08cff05dc5c1-5635fd559dcd00d3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T14:49:20Z"
      message: 'load-balancer-api-external: tcp connection to ab3fa825be2964f47b4f08cff05dc5c1-5635fd559dcd00d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.923605ms
      message: 'load-balancer-api-external: tcp connection to ab3fa825be2964f47b4f08cff05dc5c1-5635fd559dcd00d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:49:20Z"
    - latency: 10.024493ms
      message: 'load-balancer-api-external: resolved host name ab3fa825be2964f47b4f08cff05dc5c1-5635fd559dcd00d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:49:20Z"
    - latency: 5.389831ms
      message: 'load-balancer-api-external: tcp connection to ab3fa825be2964f47b4f08cff05dc5c1-5635fd559dcd00d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:48:20Z"
    - latency: 10.622147ms
      message: 'load-balancer-api-external: resolved host name ab3fa825be2964f47b4f08cff05dc5c1-5635fd559dcd00d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:48:20Z"
    - latency: 4.168722ms
      message: 'load-balancer-api-external: tcp connection to ab3fa825be2964f47b4f08cff05dc5c1-5635fd559dcd00d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:47:20Z"
    - latency: 10.2539ms
      message: 'load-balancer-api-external: resolved host name ab3fa825be2964f47b4f08cff05dc5c1-5635fd559dcd00d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:47:20Z"
    - latency: 4.924789ms
      message: 'load-balancer-api-external: tcp connection to ab3fa825be2964f47b4f08cff05dc5c1-5635fd559dcd00d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:46:20Z"
    - latency: 10.852925ms
      message: 'load-balancer-api-external: resolved host name ab3fa825be2964f47b4f08cff05dc5c1-5635fd559dcd00d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:46:20Z"
    - latency: 6.786276ms
      message: 'load-balancer-api-external: tcp connection to ab3fa825be2964f47b4f08cff05dc5c1-5635fd559dcd00d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:45:20Z"
    - latency: 12.991376ms
      message: 'load-balancer-api-external: resolved host name ab3fa825be2964f47b4f08cff05dc5c1-5635fd559dcd00d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:45:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T14:43:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-102-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-102.ec2.internal
      uid: b3eb0a76-466b-4fbf-9211-b62a9df54e50
    resourceVersion: "14402"
    uid: 1f390e80-580e-4b53-ba2e-475bf8de2a70
  spec:
    sourcePod: network-check-source-685456655f-sjhc8
    targetEndpoint: ab3fa825be2964f47b4f08cff05dc5c1-5635fd559dcd00d3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T14:49:20Z"
      message: 'load-balancer-api-internal: tcp connection to ab3fa825be2964f47b4f08cff05dc5c1-5635fd559dcd00d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.980811ms
      message: 'load-balancer-api-internal: tcp connection to ab3fa825be2964f47b4f08cff05dc5c1-5635fd559dcd00d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:49:20Z"
    - latency: 10.0051ms
      message: 'load-balancer-api-internal: resolved host name ab3fa825be2964f47b4f08cff05dc5c1-5635fd559dcd00d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:49:20Z"
    - latency: 5.346083ms
      message: 'load-balancer-api-internal: tcp connection to ab3fa825be2964f47b4f08cff05dc5c1-5635fd559dcd00d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:48:20Z"
    - latency: 10.53857ms
      message: 'load-balancer-api-internal: resolved host name ab3fa825be2964f47b4f08cff05dc5c1-5635fd559dcd00d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:48:20Z"
    - latency: 4.883164ms
      message: 'load-balancer-api-internal: tcp connection to ab3fa825be2964f47b4f08cff05dc5c1-5635fd559dcd00d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:47:20Z"
    - latency: 10.224398ms
      message: 'load-balancer-api-internal: resolved host name ab3fa825be2964f47b4f08cff05dc5c1-5635fd559dcd00d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:47:20Z"
    - latency: 4.570009ms
      message: 'load-balancer-api-internal: tcp connection to ab3fa825be2964f47b4f08cff05dc5c1-5635fd559dcd00d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:46:20Z"
    - latency: 11.019449ms
      message: 'load-balancer-api-internal: resolved host name ab3fa825be2964f47b4f08cff05dc5c1-5635fd559dcd00d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:46:20Z"
    - latency: 6.784474ms
      message: 'load-balancer-api-internal: tcp connection to ab3fa825be2964f47b4f08cff05dc5c1-5635fd559dcd00d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:45:20Z"
    - latency: 12.96527ms
      message: 'load-balancer-api-internal: resolved host name ab3fa825be2964f47b4f08cff05dc5c1-5635fd559dcd00d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:45:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T14:43:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-102-to-network-check-target-ip-10-0-135-102
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-102.ec2.internal
      uid: b3eb0a76-466b-4fbf-9211-b62a9df54e50
    resourceVersion: "14752"
    uid: 1b53b0d2-9843-4398-ba22-4937f0c58086
  spec:
    sourcePod: network-check-source-685456655f-sjhc8
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T14:50:20Z"
      message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 783.049µs
      message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:50:20Z"
    - latency: 1.737694ms
      message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:49:20Z"
    - latency: 673.539µs
      message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:48:20Z"
    - latency: 1.424607ms
      message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:47:20Z"
    - latency: 1.513086ms
      message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:46:20Z"
    - latency: 932.349µs
      message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:45:20Z"
    - latency: 1.912119ms
      message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:44:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T14:43:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-102-to-network-check-target-ip-10-0-136-166
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-102.ec2.internal
      uid: b3eb0a76-466b-4fbf-9211-b62a9df54e50
    resourceVersion: "14753"
    uid: cdd78497-5ce5-4acd-bce0-45f68fcb3f19
  spec:
    sourcePod: network-check-source-685456655f-sjhc8
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T14:50:20Z"
      message: 'network-check-target-ip-10-0-136-166: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.113483ms
      message: 'network-check-target-ip-10-0-136-166: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:50:20Z"
    - latency: 2.666366ms
      message: 'network-check-target-ip-10-0-136-166: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:49:20Z"
    - latency: 1.879309ms
      message: 'network-check-target-ip-10-0-136-166: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:48:20Z"
    - latency: 2.449902ms
      message: 'network-check-target-ip-10-0-136-166: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:47:20Z"
    - latency: 2.265278ms
      message: 'network-check-target-ip-10-0-136-166: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:46:20Z"
    - latency: 2.366647ms
      message: 'network-check-target-ip-10-0-136-166: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:45:20Z"
    - latency: 7.162301ms
      message: 'network-check-target-ip-10-0-136-166: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:44:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T14:43:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-102-to-network-check-target-ip-10-0-137-47
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-102.ec2.internal
      uid: b3eb0a76-466b-4fbf-9211-b62a9df54e50
    resourceVersion: "14754"
    uid: e37ae840-292a-4380-b0ef-815cbbcd035b
  spec:
    sourcePod: network-check-source-685456655f-sjhc8
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T14:50:20Z"
      message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.327023ms
      message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:50:20Z"
    - latency: 2.333147ms
      message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:49:20Z"
    - latency: 2.324416ms
      message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:48:20Z"
    - latency: 2.409913ms
      message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:47:20Z"
    - latency: 2.345867ms
      message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:46:20Z"
    - latency: 2.575468ms
      message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:45:20Z"
    - latency: 3.170432ms
      message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:44:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T14:43:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-102-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-102.ec2.internal
      uid: b3eb0a76-466b-4fbf-9211-b62a9df54e50
    resourceVersion: "14400"
    uid: c445c121-bf35-44a6-85ef-3dbdee72b783
  spec:
    sourcePod: network-check-source-685456655f-sjhc8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T14:49:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 971.098µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:49:20Z"
    - latency: 1.845776ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:49:20Z"
    - latency: 988.505µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:48:20Z"
    - latency: 1.514479ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:48:20Z"
    - latency: 1.003395ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:47:20Z"
    - latency: 2.039839ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:47:20Z"
    - latency: 794.821µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:46:20Z"
    - latency: 1.776967ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:46:20Z"
    - latency: 824.908µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T14:45:20Z"
    - latency: 1.692306ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T14:45:20Z"
kind: List
metadata:
  resourceVersion: ""