apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T20:32:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-188-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-188.us-west-1.compute.internal uid: e1d90138-7d47-4668-8c66-5dd23f2de26c resourceVersion: "113406" uid: ee5317ec-9c65-40af-a53f-f0cfe090c2e2 spec: sourcePod: network-check-source-6f78d59f99-jm5qf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-01T20:39:32Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.181784ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:42:32Z" - latency: 1.007752ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:41:32Z" - latency: 974.013µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:40:32Z" - latency: 1.24055ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:39:32Z" - latency: 1.436588ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:38:32Z" - latency: 902.916µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:37:32Z" - latency: 1.00195ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:36:32Z" - latency: 1.295274ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:35:32Z" - latency: 1.617163ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:34:32Z" - latency: 1.141708ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:33:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T20:32:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-188-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-188.us-west-1.compute.internal uid: e1d90138-7d47-4668-8c66-5dd23f2de26c resourceVersion: "110192" uid: 8ff0da5b-aa0c-4bab-abaa-3c104b24d219 spec: sourcePod: network-check-source-6f78d59f99-jm5qf targetEndpoint: a9584bc60fd4645d0a6dd8d98805fda7-6263b06240bad7c4.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T20:38:32Z" message: 'load-balancer-api-external: tcp connection to a9584bc60fd4645d0a6dd8d98805fda7-6263b06240bad7c4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 52.224974ms message: 'load-balancer-api-external: tcp connection to a9584bc60fd4645d0a6dd8d98805fda7-6263b06240bad7c4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:38:32Z" - latency: 6.143675ms message: 'load-balancer-api-external: resolved host name a9584bc60fd4645d0a6dd8d98805fda7-6263b06240bad7c4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T21:38:32Z" - latency: 52.828226ms message: 'load-balancer-api-external: tcp connection to a9584bc60fd4645d0a6dd8d98805fda7-6263b06240bad7c4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:37:32Z" - latency: 7.888768ms message: 'load-balancer-api-external: resolved host name a9584bc60fd4645d0a6dd8d98805fda7-6263b06240bad7c4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T21:37:32Z" - latency: 53.758758ms message: 'load-balancer-api-external: tcp connection to a9584bc60fd4645d0a6dd8d98805fda7-6263b06240bad7c4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:36:32Z" - latency: 6.040324ms message: 'load-balancer-api-external: resolved host name a9584bc60fd4645d0a6dd8d98805fda7-6263b06240bad7c4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T21:36:32Z" - latency: 54.833991ms message: 'load-balancer-api-external: tcp connection to a9584bc60fd4645d0a6dd8d98805fda7-6263b06240bad7c4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:35:32Z" - latency: 6.629935ms message: 'load-balancer-api-external: resolved host name a9584bc60fd4645d0a6dd8d98805fda7-6263b06240bad7c4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T21:35:32Z" - latency: 53.953151ms message: 'load-balancer-api-external: tcp connection to a9584bc60fd4645d0a6dd8d98805fda7-6263b06240bad7c4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:34:32Z" - latency: 6.763163ms message: 'load-balancer-api-external: resolved host name a9584bc60fd4645d0a6dd8d98805fda7-6263b06240bad7c4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T21:34:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T20:32:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-188-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-188.us-west-1.compute.internal uid: e1d90138-7d47-4668-8c66-5dd23f2de26c resourceVersion: "110191" uid: 5082cc03-f40d-404d-986f-3c2cc41a3e2d spec: sourcePod: network-check-source-6f78d59f99-jm5qf targetEndpoint: a9584bc60fd4645d0a6dd8d98805fda7-6263b06240bad7c4.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T20:38:32Z" message: 'load-balancer-api-internal: tcp connection to a9584bc60fd4645d0a6dd8d98805fda7-6263b06240bad7c4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 52.6054ms message: 'load-balancer-api-internal: tcp connection to a9584bc60fd4645d0a6dd8d98805fda7-6263b06240bad7c4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:38:32Z" - latency: 6.221611ms message: 'load-balancer-api-internal: resolved host name a9584bc60fd4645d0a6dd8d98805fda7-6263b06240bad7c4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T21:38:32Z" - latency: 52.932353ms message: 'load-balancer-api-internal: tcp connection to a9584bc60fd4645d0a6dd8d98805fda7-6263b06240bad7c4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:37:32Z" - latency: 7.935925ms message: 'load-balancer-api-internal: resolved host name a9584bc60fd4645d0a6dd8d98805fda7-6263b06240bad7c4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T21:37:32Z" - latency: 54.752605ms message: 'load-balancer-api-internal: tcp connection to a9584bc60fd4645d0a6dd8d98805fda7-6263b06240bad7c4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:36:32Z" - latency: 6.017806ms message: 'load-balancer-api-internal: resolved host name a9584bc60fd4645d0a6dd8d98805fda7-6263b06240bad7c4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T21:36:32Z" - latency: 54.759855ms message: 'load-balancer-api-internal: tcp connection to a9584bc60fd4645d0a6dd8d98805fda7-6263b06240bad7c4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:35:32Z" - latency: 6.601565ms message: 'load-balancer-api-internal: resolved host name a9584bc60fd4645d0a6dd8d98805fda7-6263b06240bad7c4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T21:35:32Z" - latency: 54.131908ms message: 'load-balancer-api-internal: tcp connection to a9584bc60fd4645d0a6dd8d98805fda7-6263b06240bad7c4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:34:32Z" - latency: 6.81684ms message: 'load-balancer-api-internal: resolved host name a9584bc60fd4645d0a6dd8d98805fda7-6263b06240bad7c4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T21:34:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T20:32:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-188-to-network-check-target-ip-10-0-131-188 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-188.us-west-1.compute.internal uid: e1d90138-7d47-4668-8c66-5dd23f2de26c resourceVersion: "113403" uid: 34491307-0ed6-4bd5-94ed-95396f6fceb7 spec: sourcePod: network-check-source-6f78d59f99-jm5qf targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-01T20:39:32Z" message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.285545ms message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:42:32Z" - latency: 1.300019ms message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:41:32Z" - latency: 966.52µs message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:40:32Z" - latency: 1.243211ms message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:39:32Z" - latency: 1.11895ms message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:38:32Z" - latency: 1.493159ms message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:37:32Z" - latency: 860.532µs message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:36:32Z" - latency: 990.941µs message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:35:32Z" - latency: 1.010644ms message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:34:32Z" - latency: 1.61018ms message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:33:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T20:32:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-188-to-network-check-target-ip-10-0-133-242 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-188.us-west-1.compute.internal uid: e1d90138-7d47-4668-8c66-5dd23f2de26c resourceVersion: "113405" uid: 62aab1bd-e4f1-45dc-bbfa-d94232d2d5e3 spec: sourcePod: network-check-source-6f78d59f99-jm5qf targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-01T20:39:32Z" message: 'network-check-target-ip-10-0-133-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.510615ms message: 'network-check-target-ip-10-0-133-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:42:32Z" - latency: 2.075026ms message: 'network-check-target-ip-10-0-133-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:41:32Z" - latency: 1.849231ms message: 'network-check-target-ip-10-0-133-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:40:32Z" - latency: 2.236136ms message: 'network-check-target-ip-10-0-133-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:39:32Z" - latency: 2.253855ms message: 'network-check-target-ip-10-0-133-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:38:32Z" - latency: 2.356718ms message: 'network-check-target-ip-10-0-133-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:37:32Z" - latency: 2.107535ms message: 'network-check-target-ip-10-0-133-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:36:32Z" - latency: 2.460445ms message: 'network-check-target-ip-10-0-133-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:35:32Z" - latency: 2.406755ms message: 'network-check-target-ip-10-0-133-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:34:32Z" - latency: 2.364572ms message: 'network-check-target-ip-10-0-133-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:33:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T20:32:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-188-to-network-check-target-ip-10-0-141-35 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-188.us-west-1.compute.internal uid: e1d90138-7d47-4668-8c66-5dd23f2de26c resourceVersion: "113404" uid: ec533809-2795-4dd2-a174-d48ea3b838ba spec: sourcePod: network-check-source-6f78d59f99-jm5qf targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-01T20:39:32Z" message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.446118ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:42:32Z" - latency: 2.364895ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:41:32Z" - latency: 2.297954ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:40:32Z" - latency: 2.241793ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:39:32Z" - latency: 2.327958ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:38:32Z" - latency: 2.422391ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:37:32Z" - latency: 2.492544ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:36:32Z" - latency: 2.677178ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:35:32Z" - latency: 2.293705ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:34:32Z" - latency: 2.476067ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:33:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T20:32:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-188-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-188.us-west-1.compute.internal uid: e1d90138-7d47-4668-8c66-5dd23f2de26c resourceVersion: "110190" uid: 0d1d50a2-7f43-4b78-8f58-d8c2087ea6e8 spec: sourcePod: network-check-source-6f78d59f99-jm5qf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-01T20:38:32Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.012042ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:38:32Z" - latency: 1.678621ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T21:38:32Z" - latency: 1.021871ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:37:32Z" - latency: 1.885759ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T21:37:32Z" - latency: 1.029665ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:36:32Z" - latency: 1.891205ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T21:36:32Z" - latency: 1.158168ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:35:32Z" - latency: 2.090321ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T21:35:32Z" - latency: 1.027656ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T21:34:32Z" - latency: 1.952048ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T21:34:32Z" kind: List metadata: resourceVersion: ""