apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T16:50:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-234-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-234.ec2.internal uid: bf2d6296-da7f-4a6a-bd97-1015c3e8b03a resourceVersion: "66399" uid: bbe52683-6dbf-46ac-ab2a-f7670dbbf784 spec: sourcePod: network-check-source-7d88cb55d8-4rmnz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T16:58: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.195068ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:33:00Z" - latency: 991.4µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:32:00Z" - latency: 1.329218ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:31:00Z" - latency: 902.272µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:30:00Z" - latency: 1.248748ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:29:00Z" - latency: 1.247917ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:28:00Z" - latency: 1.578448ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:27:00Z" - latency: 878.601µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:26:00Z" - latency: 1.517473ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:25:00Z" - latency: 1.065724ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:24:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T16:50:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-234-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-234.ec2.internal uid: bf2d6296-da7f-4a6a-bd97-1015c3e8b03a resourceVersion: "66400" uid: f183ca45-ef0c-4807-97f8-a25b17df13a7 spec: sourcePod: network-check-source-7d88cb55d8-4rmnz targetEndpoint: a7e9389c344dd473fa9079bf8cf68c6e-0a64242050249fad.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T16:57:00Z" message: 'load-balancer-api-external: tcp connection to a7e9389c344dd473fa9079bf8cf68c6e-0a64242050249fad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.954769ms message: 'load-balancer-api-external: tcp connection to a7e9389c344dd473fa9079bf8cf68c6e-0a64242050249fad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:33:00Z" - latency: 9.001548ms message: 'load-balancer-api-external: resolved host name a7e9389c344dd473fa9079bf8cf68c6e-0a64242050249fad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:33:00Z" - latency: 5.646063ms message: 'load-balancer-api-external: tcp connection to a7e9389c344dd473fa9079bf8cf68c6e-0a64242050249fad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:32:00Z" - latency: 8.666649ms message: 'load-balancer-api-external: resolved host name a7e9389c344dd473fa9079bf8cf68c6e-0a64242050249fad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:32:00Z" - latency: 3.926422ms message: 'load-balancer-api-external: tcp connection to a7e9389c344dd473fa9079bf8cf68c6e-0a64242050249fad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:31:00Z" - latency: 8.940175ms message: 'load-balancer-api-external: resolved host name a7e9389c344dd473fa9079bf8cf68c6e-0a64242050249fad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:31:00Z" - latency: 6.886246ms message: 'load-balancer-api-external: tcp connection to a7e9389c344dd473fa9079bf8cf68c6e-0a64242050249fad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:30:00Z" - latency: 9.282566ms message: 'load-balancer-api-external: resolved host name a7e9389c344dd473fa9079bf8cf68c6e-0a64242050249fad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:30:00Z" - latency: 6.265043ms message: 'load-balancer-api-external: tcp connection to a7e9389c344dd473fa9079bf8cf68c6e-0a64242050249fad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:29:00Z" - latency: 9.382544ms message: 'load-balancer-api-external: resolved host name a7e9389c344dd473fa9079bf8cf68c6e-0a64242050249fad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:29:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T16:50:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-234-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-234.ec2.internal uid: bf2d6296-da7f-4a6a-bd97-1015c3e8b03a resourceVersion: "66401" uid: f7ffffcf-ac8b-47bf-8dfc-97bd726ef9ec spec: sourcePod: network-check-source-7d88cb55d8-4rmnz targetEndpoint: a7e9389c344dd473fa9079bf8cf68c6e-0a64242050249fad.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T16:57:00Z" message: 'load-balancer-api-internal: tcp connection to a7e9389c344dd473fa9079bf8cf68c6e-0a64242050249fad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 13.316163ms message: 'load-balancer-api-internal: tcp connection to a7e9389c344dd473fa9079bf8cf68c6e-0a64242050249fad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:33:00Z" - latency: 9.069385ms message: 'load-balancer-api-internal: resolved host name a7e9389c344dd473fa9079bf8cf68c6e-0a64242050249fad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:33:00Z" - latency: 5.62249ms message: 'load-balancer-api-internal: tcp connection to a7e9389c344dd473fa9079bf8cf68c6e-0a64242050249fad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:32:00Z" - latency: 8.734899ms message: 'load-balancer-api-internal: resolved host name a7e9389c344dd473fa9079bf8cf68c6e-0a64242050249fad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:32:00Z" - latency: 3.839182ms message: 'load-balancer-api-internal: tcp connection to a7e9389c344dd473fa9079bf8cf68c6e-0a64242050249fad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:31:00Z" - latency: 9.00423ms message: 'load-balancer-api-internal: resolved host name a7e9389c344dd473fa9079bf8cf68c6e-0a64242050249fad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:31:00Z" - latency: 5.917189ms message: 'load-balancer-api-internal: tcp connection to a7e9389c344dd473fa9079bf8cf68c6e-0a64242050249fad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:30:00Z" - latency: 9.363962ms message: 'load-balancer-api-internal: resolved host name a7e9389c344dd473fa9079bf8cf68c6e-0a64242050249fad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:30:00Z" - latency: 4.023881ms message: 'load-balancer-api-internal: tcp connection to a7e9389c344dd473fa9079bf8cf68c6e-0a64242050249fad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:29:00Z" - latency: 9.286996ms message: 'load-balancer-api-internal: resolved host name a7e9389c344dd473fa9079bf8cf68c6e-0a64242050249fad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:29:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T16:50:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-234-to-network-check-target-ip-10-0-133-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-234.ec2.internal uid: bf2d6296-da7f-4a6a-bd97-1015c3e8b03a resourceVersion: "66395" uid: 4540c177-2fb1-4c31-9f0d-b7735f440565 spec: sourcePod: network-check-source-7d88cb55d8-4rmnz targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-24T16:58:00Z" message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 842.464µs message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:33:00Z" - latency: 1.294223ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:32:00Z" - latency: 1.08833ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:31:00Z" - latency: 853.032µs message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:30:00Z" - latency: 1.417673ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:29:00Z" - latency: 1.565475ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:28:00Z" - latency: 1.129446ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:27:00Z" - latency: 1.496262ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:26:00Z" - latency: 1.841509ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:25:00Z" - latency: 1.450265ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:24:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T16:50:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-234-to-network-check-target-ip-10-0-135-204 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-234.ec2.internal uid: bf2d6296-da7f-4a6a-bd97-1015c3e8b03a resourceVersion: "66396" uid: 8f92b295-4931-4604-8446-f4b2d9d66ad2 spec: sourcePod: network-check-source-7d88cb55d8-4rmnz targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-24T16:58:00Z" message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.096705ms message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:33:00Z" - latency: 2.316919ms message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:32:00Z" - latency: 2.122685ms message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:31:00Z" - latency: 2.222033ms message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:30:00Z" - latency: 2.291856ms message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:29:00Z" - latency: 2.433316ms message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:28:00Z" - latency: 2.280785ms message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:27:00Z" - latency: 2.316719ms message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:26:00Z" - latency: 2.449408ms message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:25:00Z" - latency: 2.363172ms message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:24:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T16:50:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-234-to-network-check-target-ip-10-0-140-49 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-234.ec2.internal uid: bf2d6296-da7f-4a6a-bd97-1015c3e8b03a resourceVersion: "66398" uid: 9bf1e3c7-2fd5-46e6-b0bc-e3187aae21fb spec: sourcePod: network-check-source-7d88cb55d8-4rmnz targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T16:58:00Z" message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.034054ms message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:33:00Z" - latency: 2.200734ms message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:32:00Z" - latency: 2.235132ms message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:31:00Z" - latency: 2.195166ms message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:30:00Z" - latency: 2.225829ms message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:29:00Z" - latency: 2.329251ms message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:28:00Z" - latency: 2.570193ms message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:27:00Z" - latency: 2.313454ms message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:26:00Z" - latency: 2.552219ms message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:25:00Z" - latency: 2.210369ms message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:24:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T16:50:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-234-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-234.ec2.internal uid: bf2d6296-da7f-4a6a-bd97-1015c3e8b03a resourceVersion: "66397" uid: 024dc2c6-ac4b-4351-8217-c4ba99057799 spec: sourcePod: network-check-source-7d88cb55d8-4rmnz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T16:57:00Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 864.971µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:33:00Z" - latency: 1.952327ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T17:33:00Z" - latency: 1.031615ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:32:00Z" - latency: 1.97422ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T17:32:00Z" - latency: 935.017µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:31:00Z" - latency: 2.323439ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T17:31:00Z" - latency: 1.094597ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:30:00Z" - latency: 2.390789ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T17:30:00Z" - latency: 1.059431ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:29:00Z" - latency: 1.773101ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T17:29:00Z" kind: List metadata: resourceVersion: ""