apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:11:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-133-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-133.ec2.internal uid: a874f5b1-140d-4fe8-b55d-c2f78b2142b0 resourceVersion: "32957" uid: 721fa7b4-b162-44b6-80c0-cede18ced893 spec: sourcePod: network-check-source-7b678d77c7-6dpmh targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T18:18:13Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 912.181µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:53:13Z" - latency: 929.054µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:52:13Z" - latency: 972.247µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:51:13Z" - latency: 1.116642ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:50:13Z" - latency: 946.462µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:49:13Z" - latency: 1.191304ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:48:13Z" - latency: 892.621µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:47:13Z" - latency: 1.027861ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:46:13Z" - latency: 1.092382ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:45:13Z" - latency: 1.122939ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:44:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:11:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-133-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-133.ec2.internal uid: a874f5b1-140d-4fe8-b55d-c2f78b2142b0 resourceVersion: "32958" uid: 5107c78a-ddd5-4632-b2ef-bc327b1112dc spec: sourcePod: network-check-source-7b678d77c7-6dpmh targetEndpoint: a8e25f99a0b474cb696c6c3dd69f9c89-baab7f4883e282aa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T18:17:13Z" message: 'load-balancer-api-external: tcp connection to a8e25f99a0b474cb696c6c3dd69f9c89-baab7f4883e282aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.783181ms message: 'load-balancer-api-external: tcp connection to a8e25f99a0b474cb696c6c3dd69f9c89-baab7f4883e282aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:53:13Z" - latency: 8.622807ms message: 'load-balancer-api-external: resolved host name a8e25f99a0b474cb696c6c3dd69f9c89-baab7f4883e282aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:53:13Z" - latency: 5.157298ms message: 'load-balancer-api-external: tcp connection to a8e25f99a0b474cb696c6c3dd69f9c89-baab7f4883e282aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:52:13Z" - latency: 7.421668ms message: 'load-balancer-api-external: resolved host name a8e25f99a0b474cb696c6c3dd69f9c89-baab7f4883e282aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:52:13Z" - latency: 4.78281ms message: 'load-balancer-api-external: tcp connection to a8e25f99a0b474cb696c6c3dd69f9c89-baab7f4883e282aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:51:13Z" - latency: 8.934309ms message: 'load-balancer-api-external: resolved host name a8e25f99a0b474cb696c6c3dd69f9c89-baab7f4883e282aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:51:13Z" - latency: 3.76565ms message: 'load-balancer-api-external: tcp connection to a8e25f99a0b474cb696c6c3dd69f9c89-baab7f4883e282aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:50:13Z" - latency: 7.826823ms message: 'load-balancer-api-external: resolved host name a8e25f99a0b474cb696c6c3dd69f9c89-baab7f4883e282aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:50:13Z" - latency: 4.386871ms message: 'load-balancer-api-external: tcp connection to a8e25f99a0b474cb696c6c3dd69f9c89-baab7f4883e282aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:49:13Z" - latency: 8.089265ms message: 'load-balancer-api-external: resolved host name a8e25f99a0b474cb696c6c3dd69f9c89-baab7f4883e282aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:49:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:11:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-133-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-133.ec2.internal uid: a874f5b1-140d-4fe8-b55d-c2f78b2142b0 resourceVersion: "32959" uid: b50eb739-52c4-49fb-883c-3f18cf04f549 spec: sourcePod: network-check-source-7b678d77c7-6dpmh targetEndpoint: a8e25f99a0b474cb696c6c3dd69f9c89-baab7f4883e282aa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T18:17:13Z" message: 'load-balancer-api-internal: tcp connection to a8e25f99a0b474cb696c6c3dd69f9c89-baab7f4883e282aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.861911ms message: 'load-balancer-api-internal: tcp connection to a8e25f99a0b474cb696c6c3dd69f9c89-baab7f4883e282aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:53:13Z" - latency: 8.546668ms message: 'load-balancer-api-internal: resolved host name a8e25f99a0b474cb696c6c3dd69f9c89-baab7f4883e282aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:53:13Z" - latency: 5.166719ms message: 'load-balancer-api-internal: tcp connection to a8e25f99a0b474cb696c6c3dd69f9c89-baab7f4883e282aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:52:13Z" - latency: 7.396204ms message: 'load-balancer-api-internal: resolved host name a8e25f99a0b474cb696c6c3dd69f9c89-baab7f4883e282aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:52:13Z" - latency: 4.771212ms message: 'load-balancer-api-internal: tcp connection to a8e25f99a0b474cb696c6c3dd69f9c89-baab7f4883e282aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:51:13Z" - latency: 8.838781ms message: 'load-balancer-api-internal: resolved host name a8e25f99a0b474cb696c6c3dd69f9c89-baab7f4883e282aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:51:13Z" - latency: 3.993621ms message: 'load-balancer-api-internal: tcp connection to a8e25f99a0b474cb696c6c3dd69f9c89-baab7f4883e282aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:50:13Z" - latency: 7.90199ms message: 'load-balancer-api-internal: resolved host name a8e25f99a0b474cb696c6c3dd69f9c89-baab7f4883e282aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:50:13Z" - latency: 4.454267ms message: 'load-balancer-api-internal: tcp connection to a8e25f99a0b474cb696c6c3dd69f9c89-baab7f4883e282aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:49:13Z" - latency: 8.039722ms message: 'load-balancer-api-internal: resolved host name a8e25f99a0b474cb696c6c3dd69f9c89-baab7f4883e282aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:49:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:11:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-133-to-network-check-target-ip-10-0-128-59 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-133.ec2.internal uid: a874f5b1-140d-4fe8-b55d-c2f78b2142b0 resourceVersion: "32955" uid: ead11a49-b49f-4df2-a2e6-96ada4137c25 spec: sourcePod: network-check-source-7b678d77c7-6dpmh targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:18:13Z" message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.189017ms message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:53:13Z" - latency: 2.376519ms message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:52:13Z" - latency: 2.10832ms message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:51:13Z" - latency: 2.109373ms message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:50:13Z" - latency: 2.118104ms message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:49:13Z" - latency: 2.238731ms message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:48:13Z" - latency: 2.203961ms message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:47:13Z" - latency: 2.214815ms message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:46:13Z" - latency: 2.230202ms message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:45:13Z" - latency: 1.823182ms message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:44:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:11:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-133-to-network-check-target-ip-10-0-134-133 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-133.ec2.internal uid: a874f5b1-140d-4fe8-b55d-c2f78b2142b0 resourceVersion: "32953" uid: ffc5054b-49b0-40b3-b11a-9d87583f184f spec: sourcePod: network-check-source-7b678d77c7-6dpmh targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:18:13Z" message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 889.96µs message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:53:13Z" - latency: 816.171µs message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:52:13Z" - latency: 1.105712ms message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:51:13Z" - latency: 868.006µs message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:50:13Z" - latency: 775.497µs message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:49:13Z" - latency: 732.511µs message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:48:13Z" - latency: 1.304142ms message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:47:13Z" - latency: 769.531µs message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:46:13Z" - latency: 960.904µs message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:45:13Z" - latency: 823.128µs message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:44:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:11:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-133-to-network-check-target-ip-10-0-134-55 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-133.ec2.internal uid: a874f5b1-140d-4fe8-b55d-c2f78b2142b0 resourceVersion: "32954" uid: ab99bcdb-3983-4906-baa3-3ed6c050ab76 spec: sourcePod: network-check-source-7b678d77c7-6dpmh targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:18:13Z" message: 'network-check-target-ip-10-0-134-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.102731ms message: 'network-check-target-ip-10-0-134-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:53:13Z" - latency: 1.998241ms message: 'network-check-target-ip-10-0-134-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:52:13Z" - latency: 2.180681ms message: 'network-check-target-ip-10-0-134-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:51:13Z" - latency: 2.291471ms message: 'network-check-target-ip-10-0-134-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:50:13Z" - latency: 2.109081ms message: 'network-check-target-ip-10-0-134-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:49:13Z" - latency: 1.896439ms message: 'network-check-target-ip-10-0-134-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:48:13Z" - latency: 2.181193ms message: 'network-check-target-ip-10-0-134-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:47:13Z" - latency: 2.154425ms message: 'network-check-target-ip-10-0-134-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:46:13Z" - latency: 2.197783ms message: 'network-check-target-ip-10-0-134-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:45:13Z" - latency: 1.997524ms message: 'network-check-target-ip-10-0-134-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:44:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:11:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-133-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-133.ec2.internal uid: a874f5b1-140d-4fe8-b55d-c2f78b2142b0 resourceVersion: "32956" uid: 0307dd64-f682-4b26-bac6-4d052c4e1d78 spec: sourcePod: network-check-source-7b678d77c7-6dpmh targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T18:17:13Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 986.801µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:53:13Z" - latency: 1.662161ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:53:13Z" - latency: 872.404µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:52:13Z" - latency: 1.67979ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:52:13Z" - latency: 811.705µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:51:13Z" - latency: 1.687713ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:51:13Z" - latency: 925.834µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:50:13Z" - latency: 1.706129ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:50:13Z" - latency: 723.252µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:49:13Z" - latency: 1.583126ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:49:13Z" kind: List metadata: resourceVersion: ""