apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:22:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-203-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-203.ec2.internal uid: 4b99bf87-05e8-4e5f-aa94-d4b155ce49a3 resourceVersion: "18795" uid: a9d6a468-3a2a-40a7-942c-96637af9e2e6 spec: sourcePod: network-check-source-7b678d77c7-8282h targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T18:29:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 959.905µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:36:19Z" - latency: 1.226466ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:35:19Z" - latency: 1.25615ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:34:19Z" - latency: 853.425µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:33:19Z" - latency: 813.996µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:32:19Z" - latency: 984.856µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:31:19Z" - latency: 1.011166ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:30:19Z" - latency: 823.74µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:29:19Z" - latency: 811.928µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:28:19Z" - latency: 840.174µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:27:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:22:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-203-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-203.ec2.internal uid: 4b99bf87-05e8-4e5f-aa94-d4b155ce49a3 resourceVersion: "20833" uid: 262330ff-7d2b-48fc-8349-b5fbbf94a9d7 spec: sourcePod: network-check-source-7b678d77c7-8282h targetEndpoint: a0387c0487c8147b3a42dc225c745b8b-1a371c7687df2630.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T18:28:19Z" message: 'load-balancer-api-external: tcp connection to a0387c0487c8147b3a42dc225c745b8b-1a371c7687df2630.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.547604ms message: 'load-balancer-api-external: tcp connection to a0387c0487c8147b3a42dc225c745b8b-1a371c7687df2630.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:40:19Z" - latency: 9.500644ms message: 'load-balancer-api-external: resolved host name a0387c0487c8147b3a42dc225c745b8b-1a371c7687df2630.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:40:19Z" - latency: 4.475858ms message: 'load-balancer-api-external: tcp connection to a0387c0487c8147b3a42dc225c745b8b-1a371c7687df2630.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:39:19Z" - latency: 7.561384ms message: 'load-balancer-api-external: resolved host name a0387c0487c8147b3a42dc225c745b8b-1a371c7687df2630.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:39:19Z" - latency: 5.88155ms message: 'load-balancer-api-external: tcp connection to a0387c0487c8147b3a42dc225c745b8b-1a371c7687df2630.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:38:19Z" - latency: 6.925099ms message: 'load-balancer-api-external: resolved host name a0387c0487c8147b3a42dc225c745b8b-1a371c7687df2630.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:38:19Z" - latency: 6.310579ms message: 'load-balancer-api-external: tcp connection to a0387c0487c8147b3a42dc225c745b8b-1a371c7687df2630.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:37:19Z" - latency: 6.988539ms message: 'load-balancer-api-external: resolved host name a0387c0487c8147b3a42dc225c745b8b-1a371c7687df2630.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:37:19Z" - latency: 5.093685ms message: 'load-balancer-api-external: tcp connection to a0387c0487c8147b3a42dc225c745b8b-1a371c7687df2630.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:36:19Z" - latency: 7.28555ms message: 'load-balancer-api-external: resolved host name a0387c0487c8147b3a42dc225c745b8b-1a371c7687df2630.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:36:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:22:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-203-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-203.ec2.internal uid: 4b99bf87-05e8-4e5f-aa94-d4b155ce49a3 resourceVersion: "20834" uid: 40ec99a8-1403-4f73-abf0-d4154986d53e spec: sourcePod: network-check-source-7b678d77c7-8282h targetEndpoint: a0387c0487c8147b3a42dc225c745b8b-1a371c7687df2630.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T18:28:19Z" message: 'load-balancer-api-internal: tcp connection to a0387c0487c8147b3a42dc225c745b8b-1a371c7687df2630.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.133008ms message: 'load-balancer-api-internal: tcp connection to a0387c0487c8147b3a42dc225c745b8b-1a371c7687df2630.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:40:19Z" - latency: 9.554063ms message: 'load-balancer-api-internal: resolved host name a0387c0487c8147b3a42dc225c745b8b-1a371c7687df2630.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:40:19Z" - latency: 4.504233ms message: 'load-balancer-api-internal: tcp connection to a0387c0487c8147b3a42dc225c745b8b-1a371c7687df2630.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:39:19Z" - latency: 7.627855ms message: 'load-balancer-api-internal: resolved host name a0387c0487c8147b3a42dc225c745b8b-1a371c7687df2630.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:39:19Z" - latency: 5.824631ms message: 'load-balancer-api-internal: tcp connection to a0387c0487c8147b3a42dc225c745b8b-1a371c7687df2630.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:38:19Z" - latency: 6.959087ms message: 'load-balancer-api-internal: resolved host name a0387c0487c8147b3a42dc225c745b8b-1a371c7687df2630.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:38:19Z" - latency: 4.559046ms message: 'load-balancer-api-internal: tcp connection to a0387c0487c8147b3a42dc225c745b8b-1a371c7687df2630.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:37:19Z" - latency: 7.032326ms message: 'load-balancer-api-internal: resolved host name a0387c0487c8147b3a42dc225c745b8b-1a371c7687df2630.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:37:19Z" - latency: 5.335522ms message: 'load-balancer-api-internal: tcp connection to a0387c0487c8147b3a42dc225c745b8b-1a371c7687df2630.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:36:19Z" - latency: 7.371514ms message: 'load-balancer-api-internal: resolved host name a0387c0487c8147b3a42dc225c745b8b-1a371c7687df2630.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:36:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:22:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-203-to-network-check-target-ip-10-0-128-68 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-203.ec2.internal uid: 4b99bf87-05e8-4e5f-aa94-d4b155ce49a3 resourceVersion: "18793" uid: ab1153a8-d9ec-4953-a285-f1cbfa8dadc4 spec: sourcePod: network-check-source-7b678d77c7-8282h targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:29:19Z" message: 'network-check-target-ip-10-0-128-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.870912ms message: 'network-check-target-ip-10-0-128-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:36:19Z" - latency: 2.144738ms message: 'network-check-target-ip-10-0-128-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:35:19Z" - latency: 1.724913ms message: 'network-check-target-ip-10-0-128-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:34:19Z" - latency: 1.848491ms message: 'network-check-target-ip-10-0-128-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:33:19Z" - latency: 1.659603ms message: 'network-check-target-ip-10-0-128-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:32:19Z" - latency: 1.85973ms message: 'network-check-target-ip-10-0-128-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:31:19Z" - latency: 1.855222ms message: 'network-check-target-ip-10-0-128-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:30:19Z" - latency: 1.725059ms message: 'network-check-target-ip-10-0-128-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:29:19Z" - latency: 1.948839ms message: 'network-check-target-ip-10-0-128-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:28:19Z" - latency: 1.721136ms message: 'network-check-target-ip-10-0-128-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:27:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:22:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-203-to-network-check-target-ip-10-0-131-203 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-203.ec2.internal uid: 4b99bf87-05e8-4e5f-aa94-d4b155ce49a3 resourceVersion: "18792" uid: 277ceb5e-0438-48d2-bb9b-f323cd1ca1ad spec: sourcePod: network-check-source-7b678d77c7-8282h targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:29:19Z" message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.123056ms message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:36:19Z" - latency: 1.693483ms message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:35:19Z" - latency: 762.971µs message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:34:19Z" - latency: 1.3303ms message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:33:19Z" - latency: 843.481µs message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:32:19Z" - latency: 779.947µs message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:31:19Z" - latency: 706.933µs message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:30:19Z" - latency: 683.486µs message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:29:19Z" - latency: 954.318µs message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:28:19Z" - latency: 770.47µs message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:27:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:22:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-203-to-network-check-target-ip-10-0-141-219 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-203.ec2.internal uid: 4b99bf87-05e8-4e5f-aa94-d4b155ce49a3 resourceVersion: "18794" uid: 04e03757-3174-4d74-aa52-a1db8e081e46 spec: sourcePod: network-check-source-7b678d77c7-8282h targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:29:19Z" message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.117151ms message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:36:19Z" - latency: 2.532863ms message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:35:19Z" - latency: 1.940564ms message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:34:19Z" - latency: 2.196418ms message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:33:19Z" - latency: 2.013914ms message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:32:19Z" - latency: 2.256199ms message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:31:19Z" - latency: 1.98033ms message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:30:19Z" - latency: 2.110568ms message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:29:19Z" - latency: 2.365568ms message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:28:19Z" - latency: 2.377849ms message: 'network-check-target-ip-10-0-141-219: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:27:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:22:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-203-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-203.ec2.internal uid: 4b99bf87-05e8-4e5f-aa94-d4b155ce49a3 resourceVersion: "20832" uid: 7282c2e9-0533-45b3-a406-ce50cf415d95 spec: sourcePod: network-check-source-7b678d77c7-8282h targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T18:28:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 799.954µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:40:19Z" - latency: 1.581181ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:40:19Z" - latency: 946.57µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:39:19Z" - latency: 1.701126ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:39:19Z" - latency: 1.144055ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:38:19Z" - latency: 1.674336ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:38:19Z" - latency: 1.219119ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:37:19Z" - latency: 1.694107ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:37:19Z" - latency: 948.754µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:36:19Z" - latency: 1.866676ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:36:19Z" kind: List metadata: resourceVersion: ""