apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T17:24:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-235-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-235.ec2.internal uid: 21146584-ccb7-4303-8dd3-f0b4ef2f34de resourceVersion: "46887" uid: ed1b81d8-faaf-4225-bb3d-8f64ebb9b446 spec: sourcePod: network-check-source-685456655f-rxfld targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-09T17:31:36Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.070291ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:45:36Z" - latency: 771.668µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:44:36Z" - latency: 975.367µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:43:36Z" - latency: 1.401718ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:42:36Z" - latency: 1.189952ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:41:36Z" - latency: 1.251866ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:40:36Z" - latency: 1.003601ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:39:36Z" - latency: 1.780624ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:38:36Z" - latency: 1.175682ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:37:36Z" - latency: 1.290057ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:36:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T17:24:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-235-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-235.ec2.internal uid: 21146584-ccb7-4303-8dd3-f0b4ef2f34de resourceVersion: "49544" uid: 61ac66d9-6231-468b-8ce5-3f7ab643cfad spec: sourcePod: network-check-source-685456655f-rxfld targetEndpoint: af21dd79a115f44319cf4f3b3b184a22-a0c2bfd44cd790df.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T17:30:36Z" message: 'load-balancer-api-external: tcp connection to af21dd79a115f44319cf4f3b3b184a22-a0c2bfd44cd790df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.789267ms message: 'load-balancer-api-external: tcp connection to af21dd79a115f44319cf4f3b3b184a22-a0c2bfd44cd790df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:48:36Z" - latency: 11.700908ms message: 'load-balancer-api-external: resolved host name af21dd79a115f44319cf4f3b3b184a22-a0c2bfd44cd790df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T17:48:36Z" - latency: 4.185963ms message: 'load-balancer-api-external: tcp connection to af21dd79a115f44319cf4f3b3b184a22-a0c2bfd44cd790df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:47:36Z" - latency: 6.203375ms message: 'load-balancer-api-external: resolved host name af21dd79a115f44319cf4f3b3b184a22-a0c2bfd44cd790df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T17:47:36Z" - latency: 5.045504ms message: 'load-balancer-api-external: tcp connection to af21dd79a115f44319cf4f3b3b184a22-a0c2bfd44cd790df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:46:36Z" - latency: 6.646624ms message: 'load-balancer-api-external: resolved host name af21dd79a115f44319cf4f3b3b184a22-a0c2bfd44cd790df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T17:46:36Z" - latency: 3.785158ms message: 'load-balancer-api-external: tcp connection to af21dd79a115f44319cf4f3b3b184a22-a0c2bfd44cd790df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:45:36Z" - latency: 6.854747ms message: 'load-balancer-api-external: resolved host name af21dd79a115f44319cf4f3b3b184a22-a0c2bfd44cd790df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T17:45:36Z" - latency: 3.317006ms message: 'load-balancer-api-external: tcp connection to af21dd79a115f44319cf4f3b3b184a22-a0c2bfd44cd790df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:44:36Z" - latency: 7.056462ms message: 'load-balancer-api-external: resolved host name af21dd79a115f44319cf4f3b3b184a22-a0c2bfd44cd790df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T17:44:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T17:24:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-235-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-235.ec2.internal uid: 21146584-ccb7-4303-8dd3-f0b4ef2f34de resourceVersion: "49543" uid: 096cce70-c14e-43d2-ae21-3b8d613d232f spec: sourcePod: network-check-source-685456655f-rxfld targetEndpoint: af21dd79a115f44319cf4f3b3b184a22-a0c2bfd44cd790df.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T17:30:36Z" message: 'load-balancer-api-internal: tcp connection to af21dd79a115f44319cf4f3b3b184a22-a0c2bfd44cd790df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.950567ms message: 'load-balancer-api-internal: tcp connection to af21dd79a115f44319cf4f3b3b184a22-a0c2bfd44cd790df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:48:36Z" - latency: 11.716015ms message: 'load-balancer-api-internal: resolved host name af21dd79a115f44319cf4f3b3b184a22-a0c2bfd44cd790df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T17:48:36Z" - latency: 4.155859ms message: 'load-balancer-api-internal: tcp connection to af21dd79a115f44319cf4f3b3b184a22-a0c2bfd44cd790df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:47:36Z" - latency: 6.311071ms message: 'load-balancer-api-internal: resolved host name af21dd79a115f44319cf4f3b3b184a22-a0c2bfd44cd790df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T17:47:36Z" - latency: 4.98849ms message: 'load-balancer-api-internal: tcp connection to af21dd79a115f44319cf4f3b3b184a22-a0c2bfd44cd790df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:46:36Z" - latency: 6.679809ms message: 'load-balancer-api-internal: resolved host name af21dd79a115f44319cf4f3b3b184a22-a0c2bfd44cd790df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T17:46:36Z" - latency: 3.959698ms message: 'load-balancer-api-internal: tcp connection to af21dd79a115f44319cf4f3b3b184a22-a0c2bfd44cd790df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:45:36Z" - latency: 6.945673ms message: 'load-balancer-api-internal: resolved host name af21dd79a115f44319cf4f3b3b184a22-a0c2bfd44cd790df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T17:45:36Z" - latency: 3.317555ms message: 'load-balancer-api-internal: tcp connection to af21dd79a115f44319cf4f3b3b184a22-a0c2bfd44cd790df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:44:36Z" - latency: 7.105122ms message: 'load-balancer-api-internal: resolved host name af21dd79a115f44319cf4f3b3b184a22-a0c2bfd44cd790df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T17:44:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T17:24:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-235-to-network-check-target-ip-10-0-128-235 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-235.ec2.internal uid: 21146584-ccb7-4303-8dd3-f0b4ef2f34de resourceVersion: "46883" uid: d4d4a483-8818-4c14-a7d0-444086b7e205 spec: sourcePod: network-check-source-685456655f-rxfld targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-09T17:31:36Z" message: 'network-check-target-ip-10-0-128-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.38264ms message: 'network-check-target-ip-10-0-128-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:45:36Z" - latency: 1.144818ms message: 'network-check-target-ip-10-0-128-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:44:36Z" - latency: 1.1046ms message: 'network-check-target-ip-10-0-128-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:43:36Z" - latency: 756.291µs message: 'network-check-target-ip-10-0-128-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:42:36Z" - latency: 781.766µs message: 'network-check-target-ip-10-0-128-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:41:36Z" - latency: 906.432µs message: 'network-check-target-ip-10-0-128-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:40:36Z" - latency: 946.503µs message: 'network-check-target-ip-10-0-128-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:39:36Z" - latency: 1.415501ms message: 'network-check-target-ip-10-0-128-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:38:36Z" - latency: 1.272888ms message: 'network-check-target-ip-10-0-128-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:37:36Z" - latency: 749.588µs message: 'network-check-target-ip-10-0-128-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:36:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T17:24:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-235-to-network-check-target-ip-10-0-130-60 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-235.ec2.internal uid: 21146584-ccb7-4303-8dd3-f0b4ef2f34de resourceVersion: "46884" uid: 5df90575-405f-436c-ad1e-3971ed53a689 spec: sourcePod: network-check-source-685456655f-rxfld targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-09T17:31:36Z" message: 'network-check-target-ip-10-0-130-60: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.966961ms message: 'network-check-target-ip-10-0-130-60: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:45:36Z" - latency: 1.641641ms message: 'network-check-target-ip-10-0-130-60: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:44:36Z" - latency: 2.064245ms message: 'network-check-target-ip-10-0-130-60: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:43:36Z" - latency: 1.833479ms message: 'network-check-target-ip-10-0-130-60: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:42:36Z" - latency: 1.76558ms message: 'network-check-target-ip-10-0-130-60: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:41:36Z" - latency: 1.68085ms message: 'network-check-target-ip-10-0-130-60: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:40:36Z" - latency: 1.694898ms message: 'network-check-target-ip-10-0-130-60: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:39:36Z" - latency: 1.923946ms message: 'network-check-target-ip-10-0-130-60: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:38:36Z" - latency: 1.910393ms message: 'network-check-target-ip-10-0-130-60: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:37:36Z" - latency: 1.88589ms message: 'network-check-target-ip-10-0-130-60: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:36:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T17:24:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-235-to-network-check-target-ip-10-0-139-100 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-235.ec2.internal uid: 21146584-ccb7-4303-8dd3-f0b4ef2f34de resourceVersion: "46886" uid: 6edfa525-3440-43db-afb5-58bb3df6cc46 spec: sourcePod: network-check-source-685456655f-rxfld targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-09T17:31:36Z" message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.469108ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:45:36Z" - latency: 1.773262ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:44:36Z" - latency: 2.035787ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:43:36Z" - latency: 2.084059ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:42:36Z" - latency: 2.232072ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:41:36Z" - latency: 2.17078ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:40:36Z" - latency: 2.163593ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:39:36Z" - latency: 2.883488ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:38:36Z" - latency: 2.424798ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:37:36Z" - latency: 2.274009ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:36:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T17:24:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-235-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-235.ec2.internal uid: 21146584-ccb7-4303-8dd3-f0b4ef2f34de resourceVersion: "49542" uid: 1b8ba919-2c01-47bc-a278-bf02eed863a4 spec: sourcePod: network-check-source-685456655f-rxfld targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-09T17:30:36Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.158841ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:48:36Z" - latency: 2.311127ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T17:48:36Z" - latency: 968.893µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:47:36Z" - latency: 1.546571ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T17:47:36Z" - latency: 947.532µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:46:36Z" - latency: 1.761089ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T17:46:36Z" - latency: 926.397µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:45:36Z" - latency: 2.281765ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T17:45:36Z" - latency: 736.937µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T17:44:36Z" - latency: 1.790261ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T17:44:36Z" kind: List metadata: resourceVersion: ""