apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:29:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-251-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-251.ec2.internal uid: aa3560b0-b744-4981-8502-91203ace3a42 resourceVersion: "18278" uid: 99fdbfe8-ff1e-4d52-a74f-abf5c630cd77 spec: sourcePod: network-check-source-7f44b6dd87-zfr9x targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-26T11:36:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 846.975µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:43:35Z" - latency: 980.689µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:42:35Z" - latency: 1.383274ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:41:35Z" - latency: 1.075903ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:40:35Z" - latency: 965.491µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:39:35Z" - latency: 917.917µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:38:35Z" - latency: 1.180757ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:37:35Z" - latency: 1.115843ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:36:35Z" - latency: 1.000796ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:35:35Z" - latency: 1.065048ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:34:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:29:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-251-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-251.ec2.internal uid: aa3560b0-b744-4981-8502-91203ace3a42 resourceVersion: "20417" uid: 6c0bdcb1-1b2d-4570-85ce-1254b1d34a21 spec: sourcePod: network-check-source-7f44b6dd87-zfr9x targetEndpoint: a2f445a7986f7472cbdd1d4c38f11f4f-212036798096cf0a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T11:35:35Z" message: 'load-balancer-api-external: tcp connection to a2f445a7986f7472cbdd1d4c38f11f4f-212036798096cf0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.37794ms message: 'load-balancer-api-external: tcp connection to a2f445a7986f7472cbdd1d4c38f11f4f-212036798096cf0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:47:35Z" - latency: 6.043891ms message: 'load-balancer-api-external: resolved host name a2f445a7986f7472cbdd1d4c38f11f4f-212036798096cf0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T11:47:35Z" - latency: 5.216056ms message: 'load-balancer-api-external: tcp connection to a2f445a7986f7472cbdd1d4c38f11f4f-212036798096cf0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:46:35Z" - latency: 8.199293ms message: 'load-balancer-api-external: resolved host name a2f445a7986f7472cbdd1d4c38f11f4f-212036798096cf0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T11:46:35Z" - latency: 4.286418ms message: 'load-balancer-api-external: tcp connection to a2f445a7986f7472cbdd1d4c38f11f4f-212036798096cf0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:45:35Z" - latency: 6.639856ms message: 'load-balancer-api-external: resolved host name a2f445a7986f7472cbdd1d4c38f11f4f-212036798096cf0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T11:45:35Z" - latency: 4.250472ms message: 'load-balancer-api-external: tcp connection to a2f445a7986f7472cbdd1d4c38f11f4f-212036798096cf0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:44:35Z" - latency: 5.961826ms message: 'load-balancer-api-external: resolved host name a2f445a7986f7472cbdd1d4c38f11f4f-212036798096cf0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T11:44:35Z" - latency: 5.296996ms message: 'load-balancer-api-external: tcp connection to a2f445a7986f7472cbdd1d4c38f11f4f-212036798096cf0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:43:35Z" - latency: 6.310843ms message: 'load-balancer-api-external: resolved host name a2f445a7986f7472cbdd1d4c38f11f4f-212036798096cf0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T11:43:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:29:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-251-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-251.ec2.internal uid: aa3560b0-b744-4981-8502-91203ace3a42 resourceVersion: "20416" uid: bb3ed71a-46f0-4010-9897-38212830d504 spec: sourcePod: network-check-source-7f44b6dd87-zfr9x targetEndpoint: a2f445a7986f7472cbdd1d4c38f11f4f-212036798096cf0a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T11:35:35Z" message: 'load-balancer-api-internal: tcp connection to a2f445a7986f7472cbdd1d4c38f11f4f-212036798096cf0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.701909ms message: 'load-balancer-api-internal: tcp connection to a2f445a7986f7472cbdd1d4c38f11f4f-212036798096cf0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:47:35Z" - latency: 5.958363ms message: 'load-balancer-api-internal: resolved host name a2f445a7986f7472cbdd1d4c38f11f4f-212036798096cf0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T11:47:35Z" - latency: 5.24134ms message: 'load-balancer-api-internal: tcp connection to a2f445a7986f7472cbdd1d4c38f11f4f-212036798096cf0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:46:35Z" - latency: 8.126788ms message: 'load-balancer-api-internal: resolved host name a2f445a7986f7472cbdd1d4c38f11f4f-212036798096cf0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T11:46:35Z" - latency: 4.265281ms message: 'load-balancer-api-internal: tcp connection to a2f445a7986f7472cbdd1d4c38f11f4f-212036798096cf0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:45:35Z" - latency: 6.589832ms message: 'load-balancer-api-internal: resolved host name a2f445a7986f7472cbdd1d4c38f11f4f-212036798096cf0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T11:45:35Z" - latency: 4.39151ms message: 'load-balancer-api-internal: tcp connection to a2f445a7986f7472cbdd1d4c38f11f4f-212036798096cf0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:44:35Z" - latency: 6.004834ms message: 'load-balancer-api-internal: resolved host name a2f445a7986f7472cbdd1d4c38f11f4f-212036798096cf0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T11:44:35Z" - latency: 5.330802ms message: 'load-balancer-api-internal: tcp connection to a2f445a7986f7472cbdd1d4c38f11f4f-212036798096cf0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:43:35Z" - latency: 6.287727ms message: 'load-balancer-api-internal: resolved host name a2f445a7986f7472cbdd1d4c38f11f4f-212036798096cf0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T11:43:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:29:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-251-to-network-check-target-ip-10-0-130-251 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-251.ec2.internal uid: aa3560b0-b744-4981-8502-91203ace3a42 resourceVersion: "18275" uid: 030042d4-fef3-4249-9fa7-fc9f507a0d3f spec: sourcePod: network-check-source-7f44b6dd87-zfr9x targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-26T11:36:35Z" message: 'network-check-target-ip-10-0-130-251: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.076756ms message: 'network-check-target-ip-10-0-130-251: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:43:35Z" - latency: 801.586µs message: 'network-check-target-ip-10-0-130-251: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:42:35Z" - latency: 816.565µs message: 'network-check-target-ip-10-0-130-251: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:41:35Z" - latency: 950.265µs message: 'network-check-target-ip-10-0-130-251: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:40:35Z" - latency: 883.397µs message: 'network-check-target-ip-10-0-130-251: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:39:35Z" - latency: 801.141µs message: 'network-check-target-ip-10-0-130-251: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:38:35Z" - latency: 1.272882ms message: 'network-check-target-ip-10-0-130-251: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:37:35Z" - latency: 1.08889ms message: 'network-check-target-ip-10-0-130-251: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:36:35Z" - latency: 954.479µs message: 'network-check-target-ip-10-0-130-251: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:35:35Z" - latency: 1.113525ms message: 'network-check-target-ip-10-0-130-251: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:34:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:29:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-251-to-network-check-target-ip-10-0-132-203 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-251.ec2.internal uid: aa3560b0-b744-4981-8502-91203ace3a42 resourceVersion: "18276" uid: 30c3d5a1-c5bf-4dc0-a1f6-9478163fcb71 spec: sourcePod: network-check-source-7f44b6dd87-zfr9x targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-26T11:36:35Z" message: 'network-check-target-ip-10-0-132-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.946722ms message: 'network-check-target-ip-10-0-132-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:43:35Z" - latency: 1.896491ms message: 'network-check-target-ip-10-0-132-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:42:35Z" - latency: 2.458247ms message: 'network-check-target-ip-10-0-132-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:41:35Z" - latency: 1.863082ms message: 'network-check-target-ip-10-0-132-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:40:35Z" - latency: 2.006837ms message: 'network-check-target-ip-10-0-132-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:39:35Z" - latency: 2.205795ms message: 'network-check-target-ip-10-0-132-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:38:35Z" - latency: 2.271737ms message: 'network-check-target-ip-10-0-132-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:37:35Z" - latency: 2.27877ms message: 'network-check-target-ip-10-0-132-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:36:35Z" - latency: 2.368334ms message: 'network-check-target-ip-10-0-132-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:35:35Z" - latency: 2.163022ms message: 'network-check-target-ip-10-0-132-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:34:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:29:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-251-to-network-check-target-ip-10-0-137-17 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-251.ec2.internal uid: aa3560b0-b744-4981-8502-91203ace3a42 resourceVersion: "18277" uid: 41c49a3a-1d66-4559-8bb0-8dfc28387640 spec: sourcePod: network-check-source-7f44b6dd87-zfr9x targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-26T11:36:35Z" message: 'network-check-target-ip-10-0-137-17: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.279833ms message: 'network-check-target-ip-10-0-137-17: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:43:35Z" - latency: 2.20398ms message: 'network-check-target-ip-10-0-137-17: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:42:35Z" - latency: 2.074259ms message: 'network-check-target-ip-10-0-137-17: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:41:35Z" - latency: 2.252327ms message: 'network-check-target-ip-10-0-137-17: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:40:35Z" - latency: 2.315479ms message: 'network-check-target-ip-10-0-137-17: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:39:35Z" - latency: 2.198983ms message: 'network-check-target-ip-10-0-137-17: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:38:35Z" - latency: 2.332627ms message: 'network-check-target-ip-10-0-137-17: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:37:35Z" - latency: 2.205256ms message: 'network-check-target-ip-10-0-137-17: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:36:35Z" - latency: 2.051248ms message: 'network-check-target-ip-10-0-137-17: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:35:35Z" - latency: 2.438373ms message: 'network-check-target-ip-10-0-137-17: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:34:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:29:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-251-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-251.ec2.internal uid: aa3560b0-b744-4981-8502-91203ace3a42 resourceVersion: "20415" uid: 60a18c41-9384-4978-9829-787bde4d0f70 spec: sourcePod: network-check-source-7f44b6dd87-zfr9x targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-26T11:35:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 844.238µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:47:35Z" - latency: 1.628505ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T11:47:35Z" - latency: 857.651µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:46:35Z" - latency: 1.670575ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T11:46:35Z" - latency: 982.231µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:45:35Z" - latency: 1.737042ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T11:45:35Z" - latency: 1.391709ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:44:35Z" - latency: 1.832212ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T11:44:35Z" - latency: 758.838µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:43:35Z" - latency: 1.923784ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T11:43:35Z" kind: List metadata: resourceVersion: ""