apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:51:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-82-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-82.ec2.internal uid: acc9d770-0fa6-436e-9790-964f42838ca1 resourceVersion: "43561" uid: 0b604d0f-26d3-49e8-bfd5-2b98db3f2c10 spec: sourcePod: network-check-source-6947749cfc-4msss targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-15T05:58:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 898.371µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:54:54Z" - latency: 953.312µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:53:54Z" - latency: 940.39µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:52:54Z" - latency: 1.169732ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:51:54Z" - latency: 1.237987ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:50:54Z" - latency: 947.285µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:49:54Z" - latency: 1.096756ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:48:54Z" - latency: 950.537µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:47:54Z" - latency: 1.105105ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:46:54Z" - latency: 879.637µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:45:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:51:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-82-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-82.ec2.internal uid: acc9d770-0fa6-436e-9790-964f42838ca1 resourceVersion: "41727" uid: 063f28d9-ebda-4a6e-a95c-1b900dff58ae spec: sourcePod: network-check-source-6947749cfc-4msss targetEndpoint: a06b71c8a62d346d8bd060f676611784-46bedcd60ea56f08.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-15T05:57:54Z" message: 'load-balancer-api-external: tcp connection to a06b71c8a62d346d8bd060f676611784-46bedcd60ea56f08.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.571184ms message: 'load-balancer-api-external: tcp connection to a06b71c8a62d346d8bd060f676611784-46bedcd60ea56f08.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:51:54Z" - latency: 7.683778ms message: 'load-balancer-api-external: resolved host name a06b71c8a62d346d8bd060f676611784-46bedcd60ea56f08.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:51:54Z" - latency: 3.998852ms message: 'load-balancer-api-external: tcp connection to a06b71c8a62d346d8bd060f676611784-46bedcd60ea56f08.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:50:54Z" - latency: 8.819919ms message: 'load-balancer-api-external: resolved host name a06b71c8a62d346d8bd060f676611784-46bedcd60ea56f08.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:50:54Z" - latency: 5.228722ms message: 'load-balancer-api-external: tcp connection to a06b71c8a62d346d8bd060f676611784-46bedcd60ea56f08.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:49:54Z" - latency: 8.840557ms message: 'load-balancer-api-external: resolved host name a06b71c8a62d346d8bd060f676611784-46bedcd60ea56f08.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:49:54Z" - latency: 4.722964ms message: 'load-balancer-api-external: tcp connection to a06b71c8a62d346d8bd060f676611784-46bedcd60ea56f08.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:48:54Z" - latency: 8.592165ms message: 'load-balancer-api-external: resolved host name a06b71c8a62d346d8bd060f676611784-46bedcd60ea56f08.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:48:54Z" - latency: 4.033721ms message: 'load-balancer-api-external: tcp connection to a06b71c8a62d346d8bd060f676611784-46bedcd60ea56f08.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:47:54Z" - latency: 8.266724ms message: 'load-balancer-api-external: resolved host name a06b71c8a62d346d8bd060f676611784-46bedcd60ea56f08.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:47:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:51:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-82-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-82.ec2.internal uid: acc9d770-0fa6-436e-9790-964f42838ca1 resourceVersion: "41728" uid: 8f22c1c7-4f2b-49df-81f7-8cfee660b992 spec: sourcePod: network-check-source-6947749cfc-4msss targetEndpoint: a06b71c8a62d346d8bd060f676611784-46bedcd60ea56f08.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-15T05:57:54Z" message: 'load-balancer-api-internal: tcp connection to a06b71c8a62d346d8bd060f676611784-46bedcd60ea56f08.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.621306ms message: 'load-balancer-api-internal: tcp connection to a06b71c8a62d346d8bd060f676611784-46bedcd60ea56f08.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:51:54Z" - latency: 7.628146ms message: 'load-balancer-api-internal: resolved host name a06b71c8a62d346d8bd060f676611784-46bedcd60ea56f08.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:51:54Z" - latency: 4.240735ms message: 'load-balancer-api-internal: tcp connection to a06b71c8a62d346d8bd060f676611784-46bedcd60ea56f08.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:50:54Z" - latency: 8.769549ms message: 'load-balancer-api-internal: resolved host name a06b71c8a62d346d8bd060f676611784-46bedcd60ea56f08.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:50:54Z" - latency: 5.264399ms message: 'load-balancer-api-internal: tcp connection to a06b71c8a62d346d8bd060f676611784-46bedcd60ea56f08.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:49:54Z" - latency: 8.903826ms message: 'load-balancer-api-internal: resolved host name a06b71c8a62d346d8bd060f676611784-46bedcd60ea56f08.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:49:54Z" - latency: 4.635433ms message: 'load-balancer-api-internal: tcp connection to a06b71c8a62d346d8bd060f676611784-46bedcd60ea56f08.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:48:54Z" - latency: 8.607679ms message: 'load-balancer-api-internal: resolved host name a06b71c8a62d346d8bd060f676611784-46bedcd60ea56f08.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:48:54Z" - latency: 3.864404ms message: 'load-balancer-api-internal: tcp connection to a06b71c8a62d346d8bd060f676611784-46bedcd60ea56f08.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:47:54Z" - latency: 8.319304ms message: 'load-balancer-api-internal: resolved host name a06b71c8a62d346d8bd060f676611784-46bedcd60ea56f08.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:47:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:51:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-82-to-network-check-target-ip-10-0-131-82 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-82.ec2.internal uid: acc9d770-0fa6-436e-9790-964f42838ca1 resourceVersion: "43558" uid: 6e973ac1-2c59-4cb6-9329-bc8f12f3c87f spec: sourcePod: network-check-source-6947749cfc-4msss targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-15T05:58:54Z" message: 'network-check-target-ip-10-0-131-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 912.356µs message: 'network-check-target-ip-10-0-131-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:54:54Z" - latency: 1.255522ms message: 'network-check-target-ip-10-0-131-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:53:54Z" - latency: 995.614µs message: 'network-check-target-ip-10-0-131-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:52:54Z" - latency: 938.602µs message: 'network-check-target-ip-10-0-131-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:51:54Z" - latency: 1.468775ms message: 'network-check-target-ip-10-0-131-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:50:54Z" - latency: 1.67633ms message: 'network-check-target-ip-10-0-131-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:49:54Z" - latency: 1.229056ms message: 'network-check-target-ip-10-0-131-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:48:54Z" - latency: 1.318316ms message: 'network-check-target-ip-10-0-131-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:47:54Z" - latency: 1.446166ms message: 'network-check-target-ip-10-0-131-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:46:54Z" - latency: 1.367767ms message: 'network-check-target-ip-10-0-131-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:45:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:51:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-82-to-network-check-target-ip-10-0-135-102 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-82.ec2.internal uid: acc9d770-0fa6-436e-9790-964f42838ca1 resourceVersion: "43560" uid: 8154c51d-84a0-44df-b6ae-1586c83350d0 spec: sourcePod: network-check-source-6947749cfc-4msss targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-15T05:58:54Z" message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.205216ms message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:54:54Z" - latency: 2.280477ms message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:53:54Z" - latency: 2.410922ms message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:52:54Z" - latency: 2.289213ms message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:51:54Z" - latency: 2.638664ms message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:50:54Z" - latency: 2.273678ms message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:49:54Z" - latency: 2.278961ms message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:48:54Z" - latency: 2.36141ms message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:47:54Z" - latency: 2.449327ms message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:46:54Z" - latency: 2.531502ms message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:45:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:51:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-82-to-network-check-target-ip-10-0-138-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-82.ec2.internal uid: acc9d770-0fa6-436e-9790-964f42838ca1 resourceVersion: "43559" uid: bdb24320-6812-48b8-9c7f-a8719c6056bb spec: sourcePod: network-check-source-6947749cfc-4msss targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-15T05:58:54Z" message: 'network-check-target-ip-10-0-138-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.993142ms message: 'network-check-target-ip-10-0-138-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:54:54Z" - latency: 2.258224ms message: 'network-check-target-ip-10-0-138-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:53:54Z" - latency: 2.240198ms message: 'network-check-target-ip-10-0-138-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:52:54Z" - latency: 2.210343ms message: 'network-check-target-ip-10-0-138-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:51:54Z" - latency: 2.4278ms message: 'network-check-target-ip-10-0-138-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:50:54Z" - latency: 2.555567ms message: 'network-check-target-ip-10-0-138-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:49:54Z" - latency: 2.185581ms message: 'network-check-target-ip-10-0-138-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:48:54Z" - latency: 2.31225ms message: 'network-check-target-ip-10-0-138-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:47:54Z" - latency: 2.459591ms message: 'network-check-target-ip-10-0-138-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:46:54Z" - latency: 2.528922ms message: 'network-check-target-ip-10-0-138-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:45:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:51:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-82-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-82.ec2.internal uid: acc9d770-0fa6-436e-9790-964f42838ca1 resourceVersion: "41726" uid: 7c44f1ad-2b49-4fc4-a1a6-8b4f985bc859 spec: sourcePod: network-check-source-6947749cfc-4msss targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-15T05:57:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.180004ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:51:54Z" - latency: 1.86381ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T06:51:54Z" - latency: 797.835µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:50:54Z" - latency: 2.223032ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T06:50:54Z" - latency: 853.112µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:49:54Z" - latency: 2.003571ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T06:49:54Z" - latency: 949.393µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:48:54Z" - latency: 1.71323ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T06:48:54Z" - latency: 1.014961ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:47:54Z" - latency: 1.71974ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T06:47:54Z" kind: List metadata: resourceVersion: ""