apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T22:18:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-183-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-183.ec2.internal uid: 4fe682ef-2e0f-4405-9840-69d03b64167e resourceVersion: "39920" uid: ed40cf9a-2f0b-4f5b-8a5b-8616ca56da5f spec: sourcePod: network-check-source-8894fc9bd-7qnvc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T22:25:31Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.676336ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:14:31Z" - latency: 995.033µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:13:31Z" - latency: 914.899µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:12:31Z" - latency: 940.879µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:11:31Z" - latency: 1.065936ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:10:31Z" - latency: 1.188015ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:09:31Z" - latency: 908.629µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:08:31Z" - latency: 1.078101ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:07:31Z" - latency: 1.01169ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:06:31Z" - latency: 875.079µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:05:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T22:18:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-183-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-183.ec2.internal uid: 4fe682ef-2e0f-4405-9840-69d03b64167e resourceVersion: "41997" uid: c2be882f-1062-4186-b22d-e961273d4b01 spec: sourcePod: network-check-source-8894fc9bd-7qnvc targetEndpoint: a9066cf2dc2f44dec9f839e2f9f8b9ef-64e3d764390a030a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T22:24:31Z" message: 'load-balancer-api-external: tcp connection to a9066cf2dc2f44dec9f839e2f9f8b9ef-64e3d764390a030a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.571114ms message: 'load-balancer-api-external: tcp connection to a9066cf2dc2f44dec9f839e2f9f8b9ef-64e3d764390a030a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:18:31Z" - latency: 8.004016ms message: 'load-balancer-api-external: resolved host name a9066cf2dc2f44dec9f839e2f9f8b9ef-64e3d764390a030a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T23:18:31Z" - latency: 4.911672ms message: 'load-balancer-api-external: tcp connection to a9066cf2dc2f44dec9f839e2f9f8b9ef-64e3d764390a030a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:17:31Z" - latency: 8.478075ms message: 'load-balancer-api-external: resolved host name a9066cf2dc2f44dec9f839e2f9f8b9ef-64e3d764390a030a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T23:17:31Z" - latency: 4.731549ms message: 'load-balancer-api-external: tcp connection to a9066cf2dc2f44dec9f839e2f9f8b9ef-64e3d764390a030a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:16:31Z" - latency: 7.207065ms message: 'load-balancer-api-external: resolved host name a9066cf2dc2f44dec9f839e2f9f8b9ef-64e3d764390a030a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T23:16:31Z" - latency: 5.309296ms message: 'load-balancer-api-external: tcp connection to a9066cf2dc2f44dec9f839e2f9f8b9ef-64e3d764390a030a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:15:31Z" - latency: 8.45688ms message: 'load-balancer-api-external: resolved host name a9066cf2dc2f44dec9f839e2f9f8b9ef-64e3d764390a030a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T23:15:31Z" - latency: 4.872876ms message: 'load-balancer-api-external: tcp connection to a9066cf2dc2f44dec9f839e2f9f8b9ef-64e3d764390a030a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:14:31Z" - latency: 8.336561ms message: 'load-balancer-api-external: resolved host name a9066cf2dc2f44dec9f839e2f9f8b9ef-64e3d764390a030a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T23:14:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T22:18:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-183-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-183.ec2.internal uid: 4fe682ef-2e0f-4405-9840-69d03b64167e resourceVersion: "41998" uid: 31cb7619-e37f-4dda-adaf-debc925035ce spec: sourcePod: network-check-source-8894fc9bd-7qnvc targetEndpoint: a9066cf2dc2f44dec9f839e2f9f8b9ef-64e3d764390a030a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T22:24:31Z" message: 'load-balancer-api-internal: tcp connection to a9066cf2dc2f44dec9f839e2f9f8b9ef-64e3d764390a030a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.589568ms message: 'load-balancer-api-internal: tcp connection to a9066cf2dc2f44dec9f839e2f9f8b9ef-64e3d764390a030a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:18:31Z" - latency: 8.020193ms message: 'load-balancer-api-internal: resolved host name a9066cf2dc2f44dec9f839e2f9f8b9ef-64e3d764390a030a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T23:18:31Z" - latency: 4.920934ms message: 'load-balancer-api-internal: tcp connection to a9066cf2dc2f44dec9f839e2f9f8b9ef-64e3d764390a030a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:17:31Z" - latency: 8.509115ms message: 'load-balancer-api-internal: resolved host name a9066cf2dc2f44dec9f839e2f9f8b9ef-64e3d764390a030a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T23:17:31Z" - latency: 4.604892ms message: 'load-balancer-api-internal: tcp connection to a9066cf2dc2f44dec9f839e2f9f8b9ef-64e3d764390a030a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:16:31Z" - latency: 7.262898ms message: 'load-balancer-api-internal: resolved host name a9066cf2dc2f44dec9f839e2f9f8b9ef-64e3d764390a030a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T23:16:31Z" - latency: 4.292262ms message: 'load-balancer-api-internal: tcp connection to a9066cf2dc2f44dec9f839e2f9f8b9ef-64e3d764390a030a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:15:31Z" - latency: 8.542942ms message: 'load-balancer-api-internal: resolved host name a9066cf2dc2f44dec9f839e2f9f8b9ef-64e3d764390a030a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T23:15:31Z" - latency: 5.003386ms message: 'load-balancer-api-internal: tcp connection to a9066cf2dc2f44dec9f839e2f9f8b9ef-64e3d764390a030a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:14:31Z" - latency: 8.349932ms message: 'load-balancer-api-internal: resolved host name a9066cf2dc2f44dec9f839e2f9f8b9ef-64e3d764390a030a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T23:14:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T22:18:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-183-to-network-check-target-ip-10-0-130-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-183.ec2.internal uid: 4fe682ef-2e0f-4405-9840-69d03b64167e resourceVersion: "39918" uid: 93ab7826-c858-4b6a-9c0a-4deadee0db16 spec: sourcePod: network-check-source-8894fc9bd-7qnvc targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T22:25:31Z" message: 'network-check-target-ip-10-0-130-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.732546ms message: 'network-check-target-ip-10-0-130-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:14:31Z" - latency: 1.767801ms message: 'network-check-target-ip-10-0-130-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:13:31Z" - latency: 1.755649ms message: 'network-check-target-ip-10-0-130-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:12:31Z" - latency: 1.877916ms message: 'network-check-target-ip-10-0-130-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:11:31Z" - latency: 1.763565ms message: 'network-check-target-ip-10-0-130-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:10:31Z" - latency: 1.781184ms message: 'network-check-target-ip-10-0-130-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:09:31Z" - latency: 1.935999ms message: 'network-check-target-ip-10-0-130-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:08:31Z" - latency: 1.836939ms message: 'network-check-target-ip-10-0-130-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:07:31Z" - latency: 1.904388ms message: 'network-check-target-ip-10-0-130-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:06:31Z" - latency: 1.939733ms message: 'network-check-target-ip-10-0-130-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:05:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T22:18:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-183-to-network-check-target-ip-10-0-133-183 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-183.ec2.internal uid: 4fe682ef-2e0f-4405-9840-69d03b64167e resourceVersion: "39917" uid: de41871b-c4fd-477f-9fad-4e297b92fdec spec: sourcePod: network-check-source-8894fc9bd-7qnvc targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T22:25:31Z" message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 682.905µs message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:14:31Z" - latency: 1.28227ms message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:13:31Z" - latency: 760.952µs message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:12:31Z" - latency: 973.003µs message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:11:31Z" - latency: 1.17377ms message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:10:31Z" - latency: 1.28697ms message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:09:31Z" - latency: 959.469µs message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:08:31Z" - latency: 729.184µs message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:07:31Z" - latency: 779.34µs message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:06:31Z" - latency: 871.207µs message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:05:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T22:18:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-183-to-network-check-target-ip-10-0-136-39 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-183.ec2.internal uid: 4fe682ef-2e0f-4405-9840-69d03b64167e resourceVersion: "39919" uid: 65cb997c-a996-483b-82a8-c475ff169be5 spec: sourcePod: network-check-source-8894fc9bd-7qnvc targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T22:25:31Z" message: 'network-check-target-ip-10-0-136-39: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.141515ms message: 'network-check-target-ip-10-0-136-39: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:14:31Z" - latency: 1.905332ms message: 'network-check-target-ip-10-0-136-39: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:13:31Z" - latency: 2.078999ms message: 'network-check-target-ip-10-0-136-39: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:12:31Z" - latency: 1.909155ms message: 'network-check-target-ip-10-0-136-39: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:11:31Z" - latency: 2.095562ms message: 'network-check-target-ip-10-0-136-39: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:10:31Z" - latency: 1.882373ms message: 'network-check-target-ip-10-0-136-39: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:09:31Z" - latency: 2.003236ms message: 'network-check-target-ip-10-0-136-39: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:08:31Z" - latency: 2.038113ms message: 'network-check-target-ip-10-0-136-39: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:07:31Z" - latency: 2.297911ms message: 'network-check-target-ip-10-0-136-39: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:06:31Z" - latency: 1.896603ms message: 'network-check-target-ip-10-0-136-39: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:05:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T22:18:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-183-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-183.ec2.internal uid: 4fe682ef-2e0f-4405-9840-69d03b64167e resourceVersion: "41996" uid: b39d798f-41d8-4f98-a210-b9c69403223a spec: sourcePod: network-check-source-8894fc9bd-7qnvc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T22:24:31Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 745.772µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:18:31Z" - latency: 1.746356ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T23:18:31Z" - latency: 642.661µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:17:31Z" - latency: 1.549025ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T23:17:31Z" - latency: 886.488µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:16:31Z" - latency: 1.61763ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T23:16:31Z" - latency: 780.696µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:15:31Z" - latency: 1.681362ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T23:15:31Z" - latency: 718.286µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T23:14:31Z" - latency: 1.643246ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T23:14:31Z" kind: List metadata: resourceVersion: ""