apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T14:38:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-222-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-222.ec2.internal uid: ac9ad3af-be76-4eb5-a38f-ed8264b19ce6 resourceVersion: "54590" uid: c94c069f-4c1c-484f-8a77-4eabcb2a7e42 spec: sourcePod: network-check-source-869dcfcdcd-8zw8c targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T14:45:11Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.935813ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:13:11Z" - latency: 982.466µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:12:11Z" - latency: 1.178992ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:11:11Z" - latency: 871.134µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:10:11Z" - latency: 1.748494ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:09:11Z" - latency: 854.243µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:08:11Z" - latency: 1.121395ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:07:11Z" - latency: 1.735168ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:06:11Z" - latency: 941.659µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:05:11Z" - latency: 986.366µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:04:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T14:38:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-222-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-222.ec2.internal uid: ac9ad3af-be76-4eb5-a38f-ed8264b19ce6 resourceVersion: "55624" uid: fc392d41-b45f-41ae-9823-0b264491483d spec: sourcePod: network-check-source-869dcfcdcd-8zw8c targetEndpoint: a46426fea288f4a3a9ca90346de0774f-bcfa66e3935eb25d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T14:44:11Z" message: 'load-balancer-api-external: tcp connection to a46426fea288f4a3a9ca90346de0774f-bcfa66e3935eb25d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.999998ms message: 'load-balancer-api-external: tcp connection to a46426fea288f4a3a9ca90346de0774f-bcfa66e3935eb25d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:14:11Z" - latency: 8.582409ms message: 'load-balancer-api-external: resolved host name a46426fea288f4a3a9ca90346de0774f-bcfa66e3935eb25d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T15:14:11Z" - latency: 7.854329ms message: 'load-balancer-api-external: tcp connection to a46426fea288f4a3a9ca90346de0774f-bcfa66e3935eb25d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:13:11Z" - latency: 7.580062ms message: 'load-balancer-api-external: resolved host name a46426fea288f4a3a9ca90346de0774f-bcfa66e3935eb25d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T15:13:11Z" - latency: 4.239039ms message: 'load-balancer-api-external: tcp connection to a46426fea288f4a3a9ca90346de0774f-bcfa66e3935eb25d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:12:11Z" - latency: 6.674305ms message: 'load-balancer-api-external: resolved host name a46426fea288f4a3a9ca90346de0774f-bcfa66e3935eb25d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T15:12:11Z" - latency: 4.354547ms message: 'load-balancer-api-external: tcp connection to a46426fea288f4a3a9ca90346de0774f-bcfa66e3935eb25d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:11:11Z" - latency: 8.043952ms message: 'load-balancer-api-external: resolved host name a46426fea288f4a3a9ca90346de0774f-bcfa66e3935eb25d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T15:11:11Z" - latency: 4.973659ms message: 'load-balancer-api-external: tcp connection to a46426fea288f4a3a9ca90346de0774f-bcfa66e3935eb25d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:10:11Z" - latency: 7.203232ms message: 'load-balancer-api-external: resolved host name a46426fea288f4a3a9ca90346de0774f-bcfa66e3935eb25d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T15:10:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T14:38:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-222-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-222.ec2.internal uid: ac9ad3af-be76-4eb5-a38f-ed8264b19ce6 resourceVersion: "55625" uid: 9b24866c-96d1-4daf-b1c8-dcd0cada6d41 spec: sourcePod: network-check-source-869dcfcdcd-8zw8c targetEndpoint: a46426fea288f4a3a9ca90346de0774f-bcfa66e3935eb25d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T14:44:11Z" message: 'load-balancer-api-internal: tcp connection to a46426fea288f4a3a9ca90346de0774f-bcfa66e3935eb25d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.67938ms message: 'load-balancer-api-internal: tcp connection to a46426fea288f4a3a9ca90346de0774f-bcfa66e3935eb25d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:14:11Z" - latency: 8.613645ms message: 'load-balancer-api-internal: resolved host name a46426fea288f4a3a9ca90346de0774f-bcfa66e3935eb25d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T15:14:11Z" - latency: 4.491855ms message: 'load-balancer-api-internal: tcp connection to a46426fea288f4a3a9ca90346de0774f-bcfa66e3935eb25d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:13:11Z" - latency: 7.307939ms message: 'load-balancer-api-internal: resolved host name a46426fea288f4a3a9ca90346de0774f-bcfa66e3935eb25d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T15:13:11Z" - latency: 3.733414ms message: 'load-balancer-api-internal: tcp connection to a46426fea288f4a3a9ca90346de0774f-bcfa66e3935eb25d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:12:11Z" - latency: 6.763162ms message: 'load-balancer-api-internal: resolved host name a46426fea288f4a3a9ca90346de0774f-bcfa66e3935eb25d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T15:12:11Z" - latency: 6.369376ms message: 'load-balancer-api-internal: tcp connection to a46426fea288f4a3a9ca90346de0774f-bcfa66e3935eb25d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:11:11Z" - latency: 8.217874ms message: 'load-balancer-api-internal: resolved host name a46426fea288f4a3a9ca90346de0774f-bcfa66e3935eb25d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T15:11:11Z" - latency: 4.544384ms message: 'load-balancer-api-internal: tcp connection to a46426fea288f4a3a9ca90346de0774f-bcfa66e3935eb25d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:10:11Z" - latency: 7.096121ms message: 'load-balancer-api-internal: resolved host name a46426fea288f4a3a9ca90346de0774f-bcfa66e3935eb25d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T15:10:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T14:38:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-222-to-network-check-target-ip-10-0-135-222 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-222.ec2.internal uid: ac9ad3af-be76-4eb5-a38f-ed8264b19ce6 resourceVersion: "54587" uid: b1589c74-67c9-4800-907b-13bea396a675 spec: sourcePod: network-check-source-869dcfcdcd-8zw8c targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T14:45:11Z" message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 914.97µs message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:13:11Z" - latency: 895.203µs message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:12:11Z" - latency: 790.58µs message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:11:11Z" - latency: 863.54µs message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:10:11Z" - latency: 1.314989ms message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:09:11Z" - latency: 820.009µs message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:08:11Z" - latency: 1.176025ms message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:07:11Z" - latency: 2.207114ms message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:06:11Z" - latency: 1.007416ms message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:05:11Z" - latency: 945.198µs message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:04:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T14:38:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-222-to-network-check-target-ip-10-0-136-210 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-222.ec2.internal uid: ac9ad3af-be76-4eb5-a38f-ed8264b19ce6 resourceVersion: "54588" uid: f029f09a-8c43-497f-ab05-d82d987adba0 spec: sourcePod: network-check-source-869dcfcdcd-8zw8c targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T14:45:11Z" message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.726382ms message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:13:11Z" - latency: 2.090989ms message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:12:11Z" - latency: 2.099221ms message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:11:11Z" - latency: 2.457472ms message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:10:11Z" - latency: 2.532658ms message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:09:11Z" - latency: 2.094233ms message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:08:11Z" - latency: 2.453782ms message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:07:11Z" - latency: 2.660824ms message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:06:11Z" - latency: 2.235082ms message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:05:11Z" - latency: 2.136329ms message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:04:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T14:38:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-222-to-network-check-target-ip-10-0-136-92 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-222.ec2.internal uid: ac9ad3af-be76-4eb5-a38f-ed8264b19ce6 resourceVersion: "54589" uid: 33f14ef7-66ad-4407-bcae-91ad33d29e1e spec: sourcePod: network-check-source-869dcfcdcd-8zw8c targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T14:45:11Z" message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.750041ms message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:13:11Z" - latency: 2.232515ms message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:12:11Z" - latency: 2.345449ms message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:11:11Z" - latency: 2.480568ms message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:10:11Z" - latency: 2.514439ms message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:09:11Z" - latency: 2.369238ms message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:08:11Z" - latency: 2.451206ms message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:07:11Z" - latency: 2.516703ms message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:06:11Z" - latency: 2.257125ms message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:05:11Z" - latency: 2.333876ms message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:04:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T14:38:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-222-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-222.ec2.internal uid: ac9ad3af-be76-4eb5-a38f-ed8264b19ce6 resourceVersion: "55622" uid: 3e09e006-c3f0-457a-8faa-06dd35084512 spec: sourcePod: network-check-source-869dcfcdcd-8zw8c targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T14:44:11Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.01818ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:14:11Z" - latency: 1.657721ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T15:14:11Z" - latency: 1.014526ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:13:11Z" - latency: 1.972834ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T15:13:11Z" - latency: 1.134533ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:12:11Z" - latency: 1.885604ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T15:12:11Z" - latency: 941.977µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:11:11Z" - latency: 1.792739ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T15:11:11Z" - latency: 950.213µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:10:11Z" - latency: 1.630664ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T15:10:11Z" kind: List metadata: resourceVersion: ""