apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T23:23:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-248-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-248.ec2.internal uid: e2c52749-cd44-43b2-938a-c7ff1f3c2551 resourceVersion: "72265" uid: 20d1cdff-6c1d-4381-9051-2d1cac99459a spec: sourcePod: network-check-source-7d88cb55d8-7nmvl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-27T23:30:25Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.473848ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:12:25Z" - latency: 1.055929ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:11:25Z" - latency: 868.988µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:10:25Z" - latency: 1.235227ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:09:25Z" - latency: 1.120729ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:08:25Z" - latency: 976.143µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:07:25Z" - latency: 1.061515ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:06:25Z" - latency: 1.724206ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:05:25Z" - latency: 1.068556ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:04:25Z" - latency: 1.041205ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:03:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T23:23:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-248-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-248.ec2.internal uid: e2c52749-cd44-43b2-938a-c7ff1f3c2551 resourceVersion: "71321" uid: 5d6f1020-575d-4ade-a85b-42e1dec4cd8e spec: sourcePod: network-check-source-7d88cb55d8-7nmvl targetEndpoint: a442f86fbc12a498e83f39de4d53ceb2-3bb7756da97c4259.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T23:29:25Z" message: 'load-balancer-api-external: tcp connection to a442f86fbc12a498e83f39de4d53ceb2-3bb7756da97c4259.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.242936ms message: 'load-balancer-api-external: tcp connection to a442f86fbc12a498e83f39de4d53ceb2-3bb7756da97c4259.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:11:25Z" - latency: 9.718474ms message: 'load-balancer-api-external: resolved host name a442f86fbc12a498e83f39de4d53ceb2-3bb7756da97c4259.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T00:11:25Z" - latency: 5.015282ms message: 'load-balancer-api-external: tcp connection to a442f86fbc12a498e83f39de4d53ceb2-3bb7756da97c4259.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:10:25Z" - latency: 9.011251ms message: 'load-balancer-api-external: resolved host name a442f86fbc12a498e83f39de4d53ceb2-3bb7756da97c4259.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T00:10:25Z" - latency: 4.56782ms message: 'load-balancer-api-external: tcp connection to a442f86fbc12a498e83f39de4d53ceb2-3bb7756da97c4259.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:09:25Z" - latency: 9.670858ms message: 'load-balancer-api-external: resolved host name a442f86fbc12a498e83f39de4d53ceb2-3bb7756da97c4259.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T00:09:25Z" - latency: 4.218072ms message: 'load-balancer-api-external: tcp connection to a442f86fbc12a498e83f39de4d53ceb2-3bb7756da97c4259.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:08:25Z" - latency: 8.838767ms message: 'load-balancer-api-external: resolved host name a442f86fbc12a498e83f39de4d53ceb2-3bb7756da97c4259.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T00:08:25Z" - latency: 5.627956ms message: 'load-balancer-api-external: tcp connection to a442f86fbc12a498e83f39de4d53ceb2-3bb7756da97c4259.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:07:25Z" - latency: 9.316438ms message: 'load-balancer-api-external: resolved host name a442f86fbc12a498e83f39de4d53ceb2-3bb7756da97c4259.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T00:07:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T23:23:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-248-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-248.ec2.internal uid: e2c52749-cd44-43b2-938a-c7ff1f3c2551 resourceVersion: "71322" uid: 69a9ebb5-7fe2-46b5-b0ab-27b2e9308dc4 spec: sourcePod: network-check-source-7d88cb55d8-7nmvl targetEndpoint: a442f86fbc12a498e83f39de4d53ceb2-3bb7756da97c4259.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T23:29:25Z" message: 'load-balancer-api-internal: tcp connection to a442f86fbc12a498e83f39de4d53ceb2-3bb7756da97c4259.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.254313ms message: 'load-balancer-api-internal: tcp connection to a442f86fbc12a498e83f39de4d53ceb2-3bb7756da97c4259.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:11:25Z" - latency: 9.765486ms message: 'load-balancer-api-internal: resolved host name a442f86fbc12a498e83f39de4d53ceb2-3bb7756da97c4259.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T00:11:25Z" - latency: 3.758013ms message: 'load-balancer-api-internal: tcp connection to a442f86fbc12a498e83f39de4d53ceb2-3bb7756da97c4259.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:10:25Z" - latency: 8.974012ms message: 'load-balancer-api-internal: resolved host name a442f86fbc12a498e83f39de4d53ceb2-3bb7756da97c4259.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T00:10:25Z" - latency: 4.611674ms message: 'load-balancer-api-internal: tcp connection to a442f86fbc12a498e83f39de4d53ceb2-3bb7756da97c4259.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:09:25Z" - latency: 9.695544ms message: 'load-balancer-api-internal: resolved host name a442f86fbc12a498e83f39de4d53ceb2-3bb7756da97c4259.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T00:09:25Z" - latency: 4.206324ms message: 'load-balancer-api-internal: tcp connection to a442f86fbc12a498e83f39de4d53ceb2-3bb7756da97c4259.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:08:25Z" - latency: 8.910656ms message: 'load-balancer-api-internal: resolved host name a442f86fbc12a498e83f39de4d53ceb2-3bb7756da97c4259.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T00:08:25Z" - latency: 5.589167ms message: 'load-balancer-api-internal: tcp connection to a442f86fbc12a498e83f39de4d53ceb2-3bb7756da97c4259.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:07:25Z" - latency: 9.406224ms message: 'load-balancer-api-internal: resolved host name a442f86fbc12a498e83f39de4d53ceb2-3bb7756da97c4259.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T00:07:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T23:23:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-248-to-network-check-target-ip-10-0-136-102 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-248.ec2.internal uid: e2c52749-cd44-43b2-938a-c7ff1f3c2551 resourceVersion: "72263" uid: 4da90c84-f72c-4073-b448-0a5867de04a2 spec: sourcePod: network-check-source-7d88cb55d8-7nmvl targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-27T23:30:25Z" message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.028819ms message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:12:25Z" - latency: 2.333109ms message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:11:25Z" - latency: 2.213102ms message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:10:25Z" - latency: 2.278239ms message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:09:25Z" - latency: 2.080292ms message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:08:25Z" - latency: 2.359746ms message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:07:25Z" - latency: 1.972428ms message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:06:25Z" - latency: 2.355707ms message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:05:25Z" - latency: 2.299759ms message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:04:25Z" - latency: 1.962635ms message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:03:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T23:23:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-248-to-network-check-target-ip-10-0-141-248 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-248.ec2.internal uid: e2c52749-cd44-43b2-938a-c7ff1f3c2551 resourceVersion: "72262" uid: e5ed6ef4-66aa-47f8-884b-f054ca95023c spec: sourcePod: network-check-source-7d88cb55d8-7nmvl targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-27T23:30:25Z" message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.613593ms message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:12:25Z" - latency: 1.357917ms message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:11:25Z" - latency: 891.363µs message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:10:25Z" - latency: 1.264953ms message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:09:25Z" - latency: 1.30645ms message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:08:25Z" - latency: 936.834µs message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:07:25Z" - latency: 922.051µs message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:06:25Z" - latency: 958.01µs message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:05:25Z" - latency: 1.17834ms message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:04:25Z" - latency: 978.79µs message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:03:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T23:23:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-248-to-network-check-target-ip-10-0-142-53 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-248.ec2.internal uid: e2c52749-cd44-43b2-938a-c7ff1f3c2551 resourceVersion: "72264" uid: 7d264d1e-f287-468a-922e-71b53bdf5bbd spec: sourcePod: network-check-source-7d88cb55d8-7nmvl targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-27T23:30:25Z" message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.468218ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:12:25Z" - latency: 2.294683ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:11:25Z" - latency: 2.115048ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:10:25Z" - latency: 2.307252ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:09:25Z" - latency: 1.886213ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:08:25Z" - latency: 2.037902ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:07:25Z" - latency: 1.967623ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:06:25Z" - latency: 1.988001ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:05:25Z" - latency: 1.877356ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:04:25Z" - latency: 1.660653ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:03:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T23:23:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-248-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-248.ec2.internal uid: e2c52749-cd44-43b2-938a-c7ff1f3c2551 resourceVersion: "71319" uid: efeb138d-f8df-44a5-bc77-d17fb3ef92d2 spec: sourcePod: network-check-source-7d88cb55d8-7nmvl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-27T23:29:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 902.481µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:11:25Z" - latency: 1.764037ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T00:11:25Z" - latency: 859.916µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:10:25Z" - latency: 2.398709ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T00:10:25Z" - latency: 1.423022ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:09:25Z" - latency: 2.025469ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T00:09:25Z" - latency: 914.729µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:08:25Z" - latency: 1.745208ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T00:08:25Z" - latency: 940.56µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:07:25Z" - latency: 1.755254ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T00:07:25Z" kind: List metadata: resourceVersion: ""