apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T14:29:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-132-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-132.ec2.internal uid: 4e25995f-9780-43b8-9b70-1c35745ffb45 resourceVersion: "43076" uid: f4aae60c-ea13-4392-b67e-37b936333daa spec: sourcePod: network-check-source-8894fc9bd-kj5df targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-24T14:36:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 855.977µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:04:02Z" - latency: 1.144919ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:03:02Z" - latency: 838.095µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:02:02Z" - latency: 1.06715ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:01:02Z" - latency: 932.826µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:00:02Z" - latency: 800.977µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T14:59:02Z" - latency: 868.867µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T14:58:02Z" - latency: 1.043077ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T14:57:02Z" - latency: 877.934µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T14:56:02Z" - latency: 846.159µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T14:55:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T14:29:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-132-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-132.ec2.internal uid: 4e25995f-9780-43b8-9b70-1c35745ffb45 resourceVersion: "43853" uid: 6d9fea22-03ab-4f0b-868b-7bc080896a95 spec: sourcePod: network-check-source-8894fc9bd-kj5df targetEndpoint: ac967476e400b4b769414ee30f15823b-8465cee92b2a1494.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T14:35:02Z" message: 'load-balancer-api-external: tcp connection to ac967476e400b4b769414ee30f15823b-8465cee92b2a1494.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.526161ms message: 'load-balancer-api-external: tcp connection to ac967476e400b4b769414ee30f15823b-8465cee92b2a1494.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:05:02Z" - latency: 8.254381ms message: 'load-balancer-api-external: resolved host name ac967476e400b4b769414ee30f15823b-8465cee92b2a1494.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T15:05:02Z" - latency: 4.577944ms message: 'load-balancer-api-external: tcp connection to ac967476e400b4b769414ee30f15823b-8465cee92b2a1494.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:04:02Z" - latency: 9.172929ms message: 'load-balancer-api-external: resolved host name ac967476e400b4b769414ee30f15823b-8465cee92b2a1494.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T15:04:02Z" - latency: 7.451932ms message: 'load-balancer-api-external: tcp connection to ac967476e400b4b769414ee30f15823b-8465cee92b2a1494.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:03:02Z" - latency: 8.979552ms message: 'load-balancer-api-external: resolved host name ac967476e400b4b769414ee30f15823b-8465cee92b2a1494.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T15:03:02Z" - latency: 5.578461ms message: 'load-balancer-api-external: tcp connection to ac967476e400b4b769414ee30f15823b-8465cee92b2a1494.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:02:02Z" - latency: 11.48989ms message: 'load-balancer-api-external: resolved host name ac967476e400b4b769414ee30f15823b-8465cee92b2a1494.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T15:02:02Z" - latency: 5.656738ms message: 'load-balancer-api-external: tcp connection to ac967476e400b4b769414ee30f15823b-8465cee92b2a1494.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:01:02Z" - latency: 8.307289ms message: 'load-balancer-api-external: resolved host name ac967476e400b4b769414ee30f15823b-8465cee92b2a1494.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T15:01:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T14:29:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-132-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-132.ec2.internal uid: 4e25995f-9780-43b8-9b70-1c35745ffb45 resourceVersion: "43852" uid: 35a4b547-6223-42dc-8bdd-3775eb9a4fc6 spec: sourcePod: network-check-source-8894fc9bd-kj5df targetEndpoint: ac967476e400b4b769414ee30f15823b-8465cee92b2a1494.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T14:35:02Z" message: 'load-balancer-api-internal: tcp connection to ac967476e400b4b769414ee30f15823b-8465cee92b2a1494.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.653709ms message: 'load-balancer-api-internal: tcp connection to ac967476e400b4b769414ee30f15823b-8465cee92b2a1494.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:05:02Z" - latency: 8.270005ms message: 'load-balancer-api-internal: resolved host name ac967476e400b4b769414ee30f15823b-8465cee92b2a1494.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T15:05:02Z" - latency: 4.348891ms message: 'load-balancer-api-internal: tcp connection to ac967476e400b4b769414ee30f15823b-8465cee92b2a1494.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:04:02Z" - latency: 9.170565ms message: 'load-balancer-api-internal: resolved host name ac967476e400b4b769414ee30f15823b-8465cee92b2a1494.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T15:04:02Z" - latency: 4.976333ms message: 'load-balancer-api-internal: tcp connection to ac967476e400b4b769414ee30f15823b-8465cee92b2a1494.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:03:02Z" - latency: 8.947708ms message: 'load-balancer-api-internal: resolved host name ac967476e400b4b769414ee30f15823b-8465cee92b2a1494.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T15:03:02Z" - latency: 5.544614ms message: 'load-balancer-api-internal: tcp connection to ac967476e400b4b769414ee30f15823b-8465cee92b2a1494.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:02:02Z" - latency: 11.525708ms message: 'load-balancer-api-internal: resolved host name ac967476e400b4b769414ee30f15823b-8465cee92b2a1494.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T15:02:02Z" - latency: 5.667731ms message: 'load-balancer-api-internal: tcp connection to ac967476e400b4b769414ee30f15823b-8465cee92b2a1494.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:01:02Z" - latency: 8.327396ms message: 'load-balancer-api-internal: resolved host name ac967476e400b4b769414ee30f15823b-8465cee92b2a1494.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T15:01:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T14:29:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-132-to-network-check-target-ip-10-0-128-169 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-132.ec2.internal uid: 4e25995f-9780-43b8-9b70-1c35745ffb45 resourceVersion: "43075" uid: 29b16c1d-777d-4c27-ac9e-ddc6b6ee1c19 spec: sourcePod: network-check-source-8894fc9bd-kj5df targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T14:36:02Z" message: 'network-check-target-ip-10-0-128-169: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.992624ms message: 'network-check-target-ip-10-0-128-169: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:04:02Z" - latency: 2.171375ms message: 'network-check-target-ip-10-0-128-169: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:03:02Z" - latency: 2.359651ms message: 'network-check-target-ip-10-0-128-169: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:02:02Z" - latency: 2.550067ms message: 'network-check-target-ip-10-0-128-169: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:01:02Z" - latency: 2.404616ms message: 'network-check-target-ip-10-0-128-169: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:00:02Z" - latency: 1.749059ms message: 'network-check-target-ip-10-0-128-169: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T14:59:02Z" - latency: 2.416213ms message: 'network-check-target-ip-10-0-128-169: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T14:58:02Z" - latency: 2.219609ms message: 'network-check-target-ip-10-0-128-169: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T14:57:02Z" - latency: 2.195118ms message: 'network-check-target-ip-10-0-128-169: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T14:56:02Z" - latency: 1.853763ms message: 'network-check-target-ip-10-0-128-169: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T14:55:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T14:29:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-132-to-network-check-target-ip-10-0-136-132 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-132.ec2.internal uid: 4e25995f-9780-43b8-9b70-1c35745ffb45 resourceVersion: "43073" uid: 8b4b3756-6913-4e35-ad78-1a7d9021ca15 spec: sourcePod: network-check-source-8894fc9bd-kj5df targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-24T14:36:02Z" message: 'network-check-target-ip-10-0-136-132: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 869.899µs message: 'network-check-target-ip-10-0-136-132: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:04:02Z" - latency: 762.926µs message: 'network-check-target-ip-10-0-136-132: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:03:02Z" - latency: 1.411203ms message: 'network-check-target-ip-10-0-136-132: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:02:02Z" - latency: 1.30215ms message: 'network-check-target-ip-10-0-136-132: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:01:02Z" - latency: 1.529639ms message: 'network-check-target-ip-10-0-136-132: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:00:02Z" - latency: 782.985µs message: 'network-check-target-ip-10-0-136-132: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T14:59:02Z" - latency: 721.121µs message: 'network-check-target-ip-10-0-136-132: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T14:58:02Z" - latency: 1.555919ms message: 'network-check-target-ip-10-0-136-132: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T14:57:02Z" - latency: 1.156133ms message: 'network-check-target-ip-10-0-136-132: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T14:56:02Z" - latency: 807.888µs message: 'network-check-target-ip-10-0-136-132: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T14:55:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T14:29:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-132-to-network-check-target-ip-10-0-138-116 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-132.ec2.internal uid: 4e25995f-9780-43b8-9b70-1c35745ffb45 resourceVersion: "43074" uid: f1f3309d-58da-47ac-bf7f-1e12a02c737d spec: sourcePod: network-check-source-8894fc9bd-kj5df targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T14:36:02Z" message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.290039ms message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:04:02Z" - latency: 1.962761ms message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:03:02Z" - latency: 2.403887ms message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:02:02Z" - latency: 2.182697ms message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:01:02Z" - latency: 2.434082ms message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:00:02Z" - latency: 2.170751ms message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T14:59:02Z" - latency: 2.084132ms message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T14:58:02Z" - latency: 2.553295ms message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T14:57:02Z" - latency: 2.240838ms message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T14:56:02Z" - latency: 2.358348ms message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T14:55:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T14:29:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-132-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-132.ec2.internal uid: 4e25995f-9780-43b8-9b70-1c35745ffb45 resourceVersion: "43851" uid: 11443849-c5bc-4ef3-b571-7d63ce047ad7 spec: sourcePod: network-check-source-8894fc9bd-kj5df targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-24T14:35:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.059153ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:05:02Z" - latency: 1.610968ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T15:05:02Z" - latency: 797.849µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:04:02Z" - latency: 1.852703ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T15:04:02Z" - latency: 908.671µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:03:02Z" - latency: 1.683705ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T15:03:02Z" - latency: 1.045088ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:02:02Z" - latency: 4.591516ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T15:02:02Z" - latency: 1.155785ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T15:01:02Z" - latency: 1.750313ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T15:01:02Z" kind: List metadata: resourceVersion: ""