apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T01:19:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-254-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-254.ec2.internal uid: e37ba3fd-22ca-4052-8d6c-d8ad38c9754c resourceVersion: "162056" uid: a100b7c2-7fdd-44ac-9dd8-0399c345d09f spec: sourcePod: network-check-source-6f78d59f99-rgvjv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T01:26:31Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.217213ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:22:31Z" - latency: 1.104669ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:21:31Z" - latency: 1.470974ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:20:31Z" - latency: 11.213854ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:19:31Z" - latency: 1.467569ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:18:31Z" - latency: 1.812739ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:17:31Z" - latency: 1.020251ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:16:31Z" - latency: 1.249164ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:15:31Z" - latency: 3.121499ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:14:31Z" - latency: 1.334724ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:13:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T01:19:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-254-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-254.ec2.internal uid: e37ba3fd-22ca-4052-8d6c-d8ad38c9754c resourceVersion: "155113" uid: 911f49f2-a905-48be-8a81-562390149738 spec: sourcePod: network-check-source-6f78d59f99-rgvjv targetEndpoint: ae48b1253dc954d3382a7b31facbef21-8f6068867c777ecd.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T01:25:31Z" message: 'load-balancer-api-external: tcp connection to ae48b1253dc954d3382a7b31facbef21-8f6068867c777ecd.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 30.490107ms message: 'load-balancer-api-external: tcp connection to ae48b1253dc954d3382a7b31facbef21-8f6068867c777ecd.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:19:31Z" - latency: 42.753683ms message: 'load-balancer-api-external: resolved host name ae48b1253dc954d3382a7b31facbef21-8f6068867c777ecd.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T02:19:31Z" - latency: 17.645822ms message: 'load-balancer-api-external: tcp connection to ae48b1253dc954d3382a7b31facbef21-8f6068867c777ecd.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:18:31Z" - latency: 15.787607ms message: 'load-balancer-api-external: resolved host name ae48b1253dc954d3382a7b31facbef21-8f6068867c777ecd.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T02:18:31Z" - latency: 16.807771ms message: 'load-balancer-api-external: tcp connection to ae48b1253dc954d3382a7b31facbef21-8f6068867c777ecd.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:17:31Z" - latency: 9.893093ms message: 'load-balancer-api-external: resolved host name ae48b1253dc954d3382a7b31facbef21-8f6068867c777ecd.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T02:17:31Z" - latency: 16.082688ms message: 'load-balancer-api-external: tcp connection to ae48b1253dc954d3382a7b31facbef21-8f6068867c777ecd.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:16:31Z" - latency: 8.156969ms message: 'load-balancer-api-external: resolved host name ae48b1253dc954d3382a7b31facbef21-8f6068867c777ecd.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T02:16:31Z" - latency: 17.369581ms message: 'load-balancer-api-external: tcp connection to ae48b1253dc954d3382a7b31facbef21-8f6068867c777ecd.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:15:31Z" - latency: 8.292216ms message: 'load-balancer-api-external: resolved host name ae48b1253dc954d3382a7b31facbef21-8f6068867c777ecd.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T02:15:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T01:19:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-254-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-254.ec2.internal uid: e37ba3fd-22ca-4052-8d6c-d8ad38c9754c resourceVersion: "155114" uid: 8bd8fe86-7972-4ee4-bc03-58db88008c83 spec: sourcePod: network-check-source-6f78d59f99-rgvjv targetEndpoint: ae48b1253dc954d3382a7b31facbef21-8f6068867c777ecd.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T01:25:31Z" message: 'load-balancer-api-internal: tcp connection to ae48b1253dc954d3382a7b31facbef21-8f6068867c777ecd.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 29.710188ms message: 'load-balancer-api-internal: tcp connection to ae48b1253dc954d3382a7b31facbef21-8f6068867c777ecd.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:19:31Z" - latency: 42.38792ms message: 'load-balancer-api-internal: resolved host name ae48b1253dc954d3382a7b31facbef21-8f6068867c777ecd.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T02:19:31Z" - latency: 18.434604ms message: 'load-balancer-api-internal: tcp connection to ae48b1253dc954d3382a7b31facbef21-8f6068867c777ecd.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:18:31Z" - latency: 15.867059ms message: 'load-balancer-api-internal: resolved host name ae48b1253dc954d3382a7b31facbef21-8f6068867c777ecd.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T02:18:31Z" - latency: 17.457974ms message: 'load-balancer-api-internal: tcp connection to ae48b1253dc954d3382a7b31facbef21-8f6068867c777ecd.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:17:31Z" - latency: 10.019698ms message: 'load-balancer-api-internal: resolved host name ae48b1253dc954d3382a7b31facbef21-8f6068867c777ecd.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T02:17:31Z" - latency: 14.999711ms message: 'load-balancer-api-internal: tcp connection to ae48b1253dc954d3382a7b31facbef21-8f6068867c777ecd.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:16:31Z" - latency: 8.13654ms message: 'load-balancer-api-internal: resolved host name ae48b1253dc954d3382a7b31facbef21-8f6068867c777ecd.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T02:16:31Z" - latency: 17.385498ms message: 'load-balancer-api-internal: tcp connection to ae48b1253dc954d3382a7b31facbef21-8f6068867c777ecd.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:15:31Z" - latency: 8.330658ms message: 'load-balancer-api-internal: resolved host name ae48b1253dc954d3382a7b31facbef21-8f6068867c777ecd.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T02:15:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T01:19:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-254-to-network-check-target-ip-10-0-134-254 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-254.ec2.internal uid: e37ba3fd-22ca-4052-8d6c-d8ad38c9754c resourceVersion: "162053" uid: 043c215d-69ec-46ed-a4ee-c4c0b65ff7ef spec: sourcePod: network-check-source-6f78d59f99-rgvjv targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T01:26:31Z" message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.233926ms message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:22:31Z" - latency: 1.098508ms message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:21:31Z" - latency: 1.001877ms message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:20:31Z" - latency: 11.341745ms message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:19:31Z" - latency: 1.71574ms message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:18:31Z" - latency: 1.208218ms message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:17:31Z" - latency: 1.205966ms message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:16:31Z" - latency: 1.623474ms message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:15:31Z" - latency: 1.444837ms message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:14:31Z" - latency: 1.213144ms message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:13:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T01:19:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-254-to-network-check-target-ip-10-0-135-65 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-254.ec2.internal uid: e37ba3fd-22ca-4052-8d6c-d8ad38c9754c resourceVersion: "162055" uid: 3cfaeb31-8adc-47c8-ba21-9e174e217ab6 spec: sourcePod: network-check-source-6f78d59f99-rgvjv targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T01:26:31Z" message: 'network-check-target-ip-10-0-135-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.749177ms message: 'network-check-target-ip-10-0-135-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:22:31Z" - latency: 2.20404ms message: 'network-check-target-ip-10-0-135-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:21:31Z" - latency: 2.57373ms message: 'network-check-target-ip-10-0-135-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:20:31Z" - latency: 15.635052ms message: 'network-check-target-ip-10-0-135-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:19:31Z" - latency: 2.689647ms message: 'network-check-target-ip-10-0-135-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:18:31Z" - latency: 3.281715ms message: 'network-check-target-ip-10-0-135-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:17:31Z" - latency: 2.222104ms message: 'network-check-target-ip-10-0-135-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:16:31Z" - latency: 3.0137ms message: 'network-check-target-ip-10-0-135-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:15:31Z" - latency: 3.588242ms message: 'network-check-target-ip-10-0-135-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:14:31Z" - latency: 2.817863ms message: 'network-check-target-ip-10-0-135-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:13:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T01:19:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-254-to-network-check-target-ip-10-0-138-223 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-254.ec2.internal uid: e37ba3fd-22ca-4052-8d6c-d8ad38c9754c resourceVersion: "162054" uid: 3940d025-9f19-48f7-937b-758b98b6a582 spec: sourcePod: network-check-source-6f78d59f99-rgvjv targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T01:26:31Z" message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.667145ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:22:31Z" - latency: 2.628204ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:21:31Z" - latency: 2.765949ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:20:31Z" - latency: 15.069968ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:19:31Z" - latency: 5.573834ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:18:31Z" - latency: 2.800104ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:17:31Z" - latency: 3.041723ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:16:31Z" - latency: 3.103449ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:15:31Z" - latency: 3.850168ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:14:31Z" - latency: 11.06686ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:13:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T01:19:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-254-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-254.ec2.internal uid: e37ba3fd-22ca-4052-8d6c-d8ad38c9754c resourceVersion: "155110" uid: 37583b6d-ceb0-42c8-9f46-b27c063558c7 spec: sourcePod: network-check-source-6f78d59f99-rgvjv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T01:25:31Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.673701ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:19:31Z" - latency: 12.719284ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T02:19:31Z" - latency: 4.267749ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:18:31Z" - latency: 2.641651ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T02:18:31Z" - latency: 1.715951ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:17:31Z" - latency: 3.293468ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T02:17:31Z" - latency: 1.08053ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:16:31Z" - latency: 2.428987ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T02:16:31Z" - latency: 1.71416ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T02:15:31Z" - latency: 2.354533ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T02:15:31Z" kind: List metadata: resourceVersion: ""