apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T15:01:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-199-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-199.ec2.internal uid: a4a682d5-5194-4015-b04e-468283595b70 resourceVersion: "26280" uid: 2751fef5-bb76-4a97-b690-e1dbe8b928c2 spec: sourcePod: network-check-source-8894fc9bd-4mhjz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-23T15:08:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.161929ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:43:02Z" - latency: 1.336372ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:42:02Z" - latency: 1.106625ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:41:02Z" - latency: 1.077943ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:40:02Z" - latency: 966.1µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:39:02Z" - latency: 817.484µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:38:02Z" - latency: 1.083138ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:37:02Z" - latency: 1.260628ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:36:02Z" - latency: 872.888µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:35:02Z" - latency: 1.117418ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:34:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T15:01:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-199-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-199.ec2.internal uid: a4a682d5-5194-4015-b04e-468283595b70 resourceVersion: "26281" uid: 9610918c-fc18-4fa3-aba4-eaad64b6c2c4 spec: sourcePod: network-check-source-8894fc9bd-4mhjz targetEndpoint: af61c59681f4b4780853142ec2d28b02-ae7a07c23c44a6cd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T15:07:02Z" message: 'load-balancer-api-external: tcp connection to af61c59681f4b4780853142ec2d28b02-ae7a07c23c44a6cd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.434813ms message: 'load-balancer-api-external: tcp connection to af61c59681f4b4780853142ec2d28b02-ae7a07c23c44a6cd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:43:02Z" - latency: 8.269345ms message: 'load-balancer-api-external: resolved host name af61c59681f4b4780853142ec2d28b02-ae7a07c23c44a6cd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T15:43:02Z" - latency: 4.944958ms message: 'load-balancer-api-external: tcp connection to af61c59681f4b4780853142ec2d28b02-ae7a07c23c44a6cd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:42:02Z" - latency: 7.967922ms message: 'load-balancer-api-external: resolved host name af61c59681f4b4780853142ec2d28b02-ae7a07c23c44a6cd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T15:42:02Z" - latency: 5.258505ms message: 'load-balancer-api-external: tcp connection to af61c59681f4b4780853142ec2d28b02-ae7a07c23c44a6cd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:41:02Z" - latency: 7.756412ms message: 'load-balancer-api-external: resolved host name af61c59681f4b4780853142ec2d28b02-ae7a07c23c44a6cd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T15:41:02Z" - latency: 4.800589ms message: 'load-balancer-api-external: tcp connection to af61c59681f4b4780853142ec2d28b02-ae7a07c23c44a6cd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:40:02Z" - latency: 8.102941ms message: 'load-balancer-api-external: resolved host name af61c59681f4b4780853142ec2d28b02-ae7a07c23c44a6cd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T15:40:02Z" - latency: 4.306759ms message: 'load-balancer-api-external: tcp connection to af61c59681f4b4780853142ec2d28b02-ae7a07c23c44a6cd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:39:02Z" - latency: 7.505723ms message: 'load-balancer-api-external: resolved host name af61c59681f4b4780853142ec2d28b02-ae7a07c23c44a6cd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T15:39:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T15:01:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-199-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-199.ec2.internal uid: a4a682d5-5194-4015-b04e-468283595b70 resourceVersion: "26282" uid: 469e0fc5-8b70-4b04-8ca6-fe4d501d3e49 spec: sourcePod: network-check-source-8894fc9bd-4mhjz targetEndpoint: af61c59681f4b4780853142ec2d28b02-ae7a07c23c44a6cd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T15:07:02Z" message: 'load-balancer-api-internal: tcp connection to af61c59681f4b4780853142ec2d28b02-ae7a07c23c44a6cd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.459721ms message: 'load-balancer-api-internal: tcp connection to af61c59681f4b4780853142ec2d28b02-ae7a07c23c44a6cd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:43:02Z" - latency: 8.318126ms message: 'load-balancer-api-internal: resolved host name af61c59681f4b4780853142ec2d28b02-ae7a07c23c44a6cd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T15:43:02Z" - latency: 4.943132ms message: 'load-balancer-api-internal: tcp connection to af61c59681f4b4780853142ec2d28b02-ae7a07c23c44a6cd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:42:02Z" - latency: 8.053007ms message: 'load-balancer-api-internal: resolved host name af61c59681f4b4780853142ec2d28b02-ae7a07c23c44a6cd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T15:42:02Z" - latency: 5.248532ms message: 'load-balancer-api-internal: tcp connection to af61c59681f4b4780853142ec2d28b02-ae7a07c23c44a6cd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:41:02Z" - latency: 7.800516ms message: 'load-balancer-api-internal: resolved host name af61c59681f4b4780853142ec2d28b02-ae7a07c23c44a6cd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T15:41:02Z" - latency: 4.629059ms message: 'load-balancer-api-internal: tcp connection to af61c59681f4b4780853142ec2d28b02-ae7a07c23c44a6cd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:40:02Z" - latency: 8.169756ms message: 'load-balancer-api-internal: resolved host name af61c59681f4b4780853142ec2d28b02-ae7a07c23c44a6cd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T15:40:02Z" - latency: 4.315008ms message: 'load-balancer-api-internal: tcp connection to af61c59681f4b4780853142ec2d28b02-ae7a07c23c44a6cd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:39:02Z" - latency: 7.578988ms message: 'load-balancer-api-internal: resolved host name af61c59681f4b4780853142ec2d28b02-ae7a07c23c44a6cd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T15:39:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T15:01:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-199-to-network-check-target-ip-10-0-135-40 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-199.ec2.internal uid: a4a682d5-5194-4015-b04e-468283595b70 resourceVersion: "26278" uid: f00b8fdc-bd2b-44de-b3b7-7fbb934df0de spec: sourcePod: network-check-source-8894fc9bd-4mhjz targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-23T15:08:02Z" message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.704579ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:43:02Z" - latency: 1.896424ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:42:02Z" - latency: 1.744136ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:41:02Z" - latency: 1.935441ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:40:02Z" - latency: 1.843973ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:39:02Z" - latency: 2.389581ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:38:02Z" - latency: 1.696839ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:37:02Z" - latency: 1.74121ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:36:02Z" - latency: 1.635132ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:35:02Z" - latency: 1.857838ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:34:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T15:01:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-199-to-network-check-target-ip-10-0-141-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-199.ec2.internal uid: a4a682d5-5194-4015-b04e-468283595b70 resourceVersion: "26277" uid: 14ff3ecf-c064-4053-ae65-e8222a63bf3a spec: sourcePod: network-check-source-8894fc9bd-4mhjz targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-23T15:08:02Z" message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.103495ms message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:43:02Z" - latency: 2.069092ms message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:42:02Z" - latency: 2.49841ms message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:41:02Z" - latency: 2.251986ms message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:40:02Z" - latency: 2.46416ms message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:39:02Z" - latency: 2.420152ms message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:38:02Z" - latency: 1.980106ms message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:37:02Z" - latency: 2.0156ms message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:36:02Z" - latency: 2.132905ms message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:35:02Z" - latency: 2.577528ms message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:34:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T15:01:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-199-to-network-check-target-ip-10-0-143-199 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-199.ec2.internal uid: a4a682d5-5194-4015-b04e-468283595b70 resourceVersion: "26276" uid: 5507ebbd-59cb-41a5-912e-2af82ea750cd spec: sourcePod: network-check-source-8894fc9bd-4mhjz targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-23T15:08:02Z" message: 'network-check-target-ip-10-0-143-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.020139ms message: 'network-check-target-ip-10-0-143-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:43:02Z" - latency: 1.462082ms message: 'network-check-target-ip-10-0-143-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:42:02Z" - latency: 1.084542ms message: 'network-check-target-ip-10-0-143-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:41:02Z" - latency: 799.536µs message: 'network-check-target-ip-10-0-143-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:40:02Z" - latency: 895.153µs message: 'network-check-target-ip-10-0-143-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:39:02Z" - latency: 876.659µs message: 'network-check-target-ip-10-0-143-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:38:02Z" - latency: 813.473µs message: 'network-check-target-ip-10-0-143-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:37:02Z" - latency: 1.04258ms message: 'network-check-target-ip-10-0-143-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:36:02Z" - latency: 779.323µs message: 'network-check-target-ip-10-0-143-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:35:02Z" - latency: 1.296703ms message: 'network-check-target-ip-10-0-143-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:34:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T15:01:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-199-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-199.ec2.internal uid: a4a682d5-5194-4015-b04e-468283595b70 resourceVersion: "26279" uid: 2c0e57c5-bc63-4ed9-a8e0-8d3a9f3637de spec: sourcePod: network-check-source-8894fc9bd-4mhjz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-23T15:07:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 893.326µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:43:02Z" - latency: 1.713355ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T15:43:02Z" - latency: 928.679µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:42:02Z" - latency: 1.853804ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T15:42:02Z" - latency: 966.642µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:41:02Z" - latency: 1.790843ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T15:41:02Z" - latency: 836.53µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:40:02Z" - latency: 1.626653ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T15:40:02Z" - latency: 929.897µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T15:39:02Z" - latency: 1.767742ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T15:39:02Z" kind: List metadata: resourceVersion: ""