apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T22:15:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-31-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-31.ec2.internal uid: 4c17c7d0-b0ac-493a-ae18-321f6096c61b resourceVersion: "148114" uid: 6dca15bf-ae85-41fc-a22a-2919e0f2e24b spec: sourcePod: network-check-source-6f78d59f99-j4c22 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-29T22:22:58Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.10147ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:18:57Z" - latency: 1.713847ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:17:57Z" - latency: 2.999914ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:16:57Z" - latency: 1.432759ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:15:57Z" - latency: 1.299454ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:14:57Z" - latency: 945.56µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:13:57Z" - latency: 1.176138ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:12:57Z" - latency: 849.961µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:11:57Z" - latency: 970.51µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:10:57Z" - latency: 1.029952ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:09:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T22:15:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-31-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-31.ec2.internal uid: 4c17c7d0-b0ac-493a-ae18-321f6096c61b resourceVersion: "145965" uid: ba35b382-758d-460d-b43c-3799421cc780 spec: sourcePod: network-check-source-6f78d59f99-j4c22 targetEndpoint: aa6d8ba7453c241c58124f3fb1cbbb1f-fec9f82c39afadc4.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-29T22:21:58Z" message: 'load-balancer-api-external: tcp connection to aa6d8ba7453c241c58124f3fb1cbbb1f-fec9f82c39afadc4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.366863ms message: 'load-balancer-api-external: tcp connection to aa6d8ba7453c241c58124f3fb1cbbb1f-fec9f82c39afadc4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:15:57Z" - latency: 8.762406ms message: 'load-balancer-api-external: resolved host name aa6d8ba7453c241c58124f3fb1cbbb1f-fec9f82c39afadc4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:15:57Z" - latency: 19.051417ms message: 'load-balancer-api-external: tcp connection to aa6d8ba7453c241c58124f3fb1cbbb1f-fec9f82c39afadc4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:14:57Z" - latency: 6.738891ms message: 'load-balancer-api-external: resolved host name aa6d8ba7453c241c58124f3fb1cbbb1f-fec9f82c39afadc4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:14:57Z" - latency: 15.204989ms message: 'load-balancer-api-external: tcp connection to aa6d8ba7453c241c58124f3fb1cbbb1f-fec9f82c39afadc4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:13:57Z" - latency: 6.5177ms message: 'load-balancer-api-external: resolved host name aa6d8ba7453c241c58124f3fb1cbbb1f-fec9f82c39afadc4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:13:57Z" - latency: 25.51743ms message: 'load-balancer-api-external: tcp connection to aa6d8ba7453c241c58124f3fb1cbbb1f-fec9f82c39afadc4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:12:57Z" - latency: 6.768553ms message: 'load-balancer-api-external: resolved host name aa6d8ba7453c241c58124f3fb1cbbb1f-fec9f82c39afadc4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:12:57Z" - latency: 17.855619ms message: 'load-balancer-api-external: tcp connection to aa6d8ba7453c241c58124f3fb1cbbb1f-fec9f82c39afadc4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:11:57Z" - latency: 7.056541ms message: 'load-balancer-api-external: resolved host name aa6d8ba7453c241c58124f3fb1cbbb1f-fec9f82c39afadc4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:11:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T22:15:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-31-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-31.ec2.internal uid: 4c17c7d0-b0ac-493a-ae18-321f6096c61b resourceVersion: "145966" uid: 8ca0238e-53e1-4d66-ae43-73b3bb157d5d spec: sourcePod: network-check-source-6f78d59f99-j4c22 targetEndpoint: aa6d8ba7453c241c58124f3fb1cbbb1f-fec9f82c39afadc4.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-29T22:21:58Z" message: 'load-balancer-api-internal: tcp connection to aa6d8ba7453c241c58124f3fb1cbbb1f-fec9f82c39afadc4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 18.328001ms message: 'load-balancer-api-internal: tcp connection to aa6d8ba7453c241c58124f3fb1cbbb1f-fec9f82c39afadc4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:15:57Z" - latency: 8.706095ms message: 'load-balancer-api-internal: resolved host name aa6d8ba7453c241c58124f3fb1cbbb1f-fec9f82c39afadc4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:15:57Z" - latency: 18.967311ms message: 'load-balancer-api-internal: tcp connection to aa6d8ba7453c241c58124f3fb1cbbb1f-fec9f82c39afadc4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:14:57Z" - latency: 6.789945ms message: 'load-balancer-api-internal: resolved host name aa6d8ba7453c241c58124f3fb1cbbb1f-fec9f82c39afadc4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:14:57Z" - latency: 18.381338ms message: 'load-balancer-api-internal: tcp connection to aa6d8ba7453c241c58124f3fb1cbbb1f-fec9f82c39afadc4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:13:57Z" - latency: 6.453789ms message: 'load-balancer-api-internal: resolved host name aa6d8ba7453c241c58124f3fb1cbbb1f-fec9f82c39afadc4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:13:57Z" - latency: 19.201746ms message: 'load-balancer-api-internal: tcp connection to aa6d8ba7453c241c58124f3fb1cbbb1f-fec9f82c39afadc4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:12:57Z" - latency: 6.841473ms message: 'load-balancer-api-internal: resolved host name aa6d8ba7453c241c58124f3fb1cbbb1f-fec9f82c39afadc4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:12:57Z" - latency: 17.790211ms message: 'load-balancer-api-internal: tcp connection to aa6d8ba7453c241c58124f3fb1cbbb1f-fec9f82c39afadc4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:11:57Z" - latency: 6.991902ms message: 'load-balancer-api-internal: resolved host name aa6d8ba7453c241c58124f3fb1cbbb1f-fec9f82c39afadc4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:11:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T22:15:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-31-to-network-check-target-ip-10-0-128-31 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-31.ec2.internal uid: 4c17c7d0-b0ac-493a-ae18-321f6096c61b resourceVersion: "148111" uid: 1f6f5d14-8d49-4e2f-a7e4-6d2d4c46c139 spec: sourcePod: network-check-source-6f78d59f99-j4c22 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-29T22:22:57Z" message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 801.62µs message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:18:57Z" - latency: 922.105µs message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:17:57Z" - latency: 3.141483ms message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:16:57Z" - latency: 1.373457ms message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:15:57Z" - latency: 1.137734ms message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:14:57Z" - latency: 1.590749ms message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:13:57Z" - latency: 1.006042ms message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:12:57Z" - latency: 902.966µs message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:11:57Z" - latency: 1.096012ms message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:10:57Z" - latency: 1.119423ms message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:09:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T22:15:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-31-to-network-check-target-ip-10-0-138-2 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-31.ec2.internal uid: 4c17c7d0-b0ac-493a-ae18-321f6096c61b resourceVersion: "148112" uid: a5206131-9e9f-48d6-9df8-e9dbd374346d spec: sourcePod: network-check-source-6f78d59f99-j4c22 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-29T22:22:57Z" message: 'network-check-target-ip-10-0-138-2: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.028888ms message: 'network-check-target-ip-10-0-138-2: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:18:57Z" - latency: 2.254596ms message: 'network-check-target-ip-10-0-138-2: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:17:57Z" - latency: 8.905561ms message: 'network-check-target-ip-10-0-138-2: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:16:57Z" - latency: 2.71298ms message: 'network-check-target-ip-10-0-138-2: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:15:57Z" - latency: 2.40246ms message: 'network-check-target-ip-10-0-138-2: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:14:57Z" - latency: 2.199826ms message: 'network-check-target-ip-10-0-138-2: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:13:57Z" - latency: 2.506533ms message: 'network-check-target-ip-10-0-138-2: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:12:57Z" - latency: 2.075124ms message: 'network-check-target-ip-10-0-138-2: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:11:57Z" - latency: 2.313616ms message: 'network-check-target-ip-10-0-138-2: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:10:57Z" - latency: 2.37892ms message: 'network-check-target-ip-10-0-138-2: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:09:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T22:15:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-31-to-network-check-target-ip-10-0-143-15 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-31.ec2.internal uid: 4c17c7d0-b0ac-493a-ae18-321f6096c61b resourceVersion: "148113" uid: eeb3f8a3-1fbd-48dd-87b0-e4577252c64a spec: sourcePod: network-check-source-6f78d59f99-j4c22 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-29T22:22:57Z" message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.352149ms message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:18:57Z" - latency: 2.166877ms message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:17:57Z" - latency: 3.495404ms message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:16:57Z" - latency: 2.625015ms message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:15:57Z" - latency: 2.34028ms message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:14:57Z" - latency: 2.43147ms message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:13:57Z" - latency: 2.269869ms message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:12:57Z" - latency: 2.344056ms message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:11:57Z" - latency: 2.429471ms message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:10:57Z" - latency: 2.286545ms message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:09:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T22:15:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-31-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-31.ec2.internal uid: 4c17c7d0-b0ac-493a-ae18-321f6096c61b resourceVersion: "145962" uid: 5c89bec5-f121-40a0-85ff-2bd092cd95fa spec: sourcePod: network-check-source-6f78d59f99-j4c22 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-29T22:21:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.35644ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:15:57Z" - latency: 2.714686ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-29T23:15:57Z" - latency: 1.335751ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:14:57Z" - latency: 1.770116ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-29T23:14:57Z" - latency: 1.225237ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:13:57Z" - latency: 1.74772ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-29T23:13:57Z" - latency: 977.402µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:12:57Z" - latency: 1.908631ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-29T23:12:57Z" - latency: 1.114424ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:11:57Z" - latency: 2.323438ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-29T23:11:57Z" kind: List metadata: resourceVersion: ""