apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T18:59:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-150-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-150.ec2.internal uid: 3e10f856-d456-430a-ae50-7106af39af69 resourceVersion: "63662" uid: 42f8756c-c843-4072-82d0-d2e28c81b209 spec: sourcePod: network-check-source-7bc5b6bf85-hvh9k targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-22T19:06: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.178808ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:41:02Z" - latency: 1.418478ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:40:02Z" - latency: 1.522827ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:39:02Z" - latency: 1.098379ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:38:02Z" - latency: 1.13236ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:37:02Z" - latency: 990.602µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:36:02Z" - latency: 1.343119ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:35:02Z" - latency: 992.183µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:34:02Z" - latency: 1.360626ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:33:02Z" - latency: 1.039342ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:32:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T18:59:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-150-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-150.ec2.internal uid: 3e10f856-d456-430a-ae50-7106af39af69 resourceVersion: "63663" uid: a60fcfa5-2c6f-4044-90e6-1fcac4a5b694 spec: sourcePod: network-check-source-7bc5b6bf85-hvh9k targetEndpoint: af4a9f7b03b2e43ffbf58bbc939c2168-44c304e03ce0e641.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T19:05:02Z" message: 'load-balancer-api-external: tcp connection to af4a9f7b03b2e43ffbf58bbc939c2168-44c304e03ce0e641.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.067668ms message: 'load-balancer-api-external: tcp connection to af4a9f7b03b2e43ffbf58bbc939c2168-44c304e03ce0e641.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:41:02Z" - latency: 7.874006ms message: 'load-balancer-api-external: resolved host name af4a9f7b03b2e43ffbf58bbc939c2168-44c304e03ce0e641.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T19:41:02Z" - latency: 4.509486ms message: 'load-balancer-api-external: tcp connection to af4a9f7b03b2e43ffbf58bbc939c2168-44c304e03ce0e641.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:40:02Z" - latency: 8.314403ms message: 'load-balancer-api-external: resolved host name af4a9f7b03b2e43ffbf58bbc939c2168-44c304e03ce0e641.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T19:40:02Z" - latency: 5.490012ms message: 'load-balancer-api-external: tcp connection to af4a9f7b03b2e43ffbf58bbc939c2168-44c304e03ce0e641.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:39:02Z" - latency: 7.195545ms message: 'load-balancer-api-external: resolved host name af4a9f7b03b2e43ffbf58bbc939c2168-44c304e03ce0e641.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T19:39:02Z" - latency: 4.581409ms message: 'load-balancer-api-external: tcp connection to af4a9f7b03b2e43ffbf58bbc939c2168-44c304e03ce0e641.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:38:02Z" - latency: 14.019161ms message: 'load-balancer-api-external: resolved host name af4a9f7b03b2e43ffbf58bbc939c2168-44c304e03ce0e641.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T19:38:02Z" - latency: 5.311042ms message: 'load-balancer-api-external: tcp connection to af4a9f7b03b2e43ffbf58bbc939c2168-44c304e03ce0e641.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:37:02Z" - latency: 6.804092ms message: 'load-balancer-api-external: resolved host name af4a9f7b03b2e43ffbf58bbc939c2168-44c304e03ce0e641.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T19:37:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T18:59:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-150-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-150.ec2.internal uid: 3e10f856-d456-430a-ae50-7106af39af69 resourceVersion: "63664" uid: 361dd9a7-cec9-465d-9557-21e9e531c3b2 spec: sourcePod: network-check-source-7bc5b6bf85-hvh9k targetEndpoint: af4a9f7b03b2e43ffbf58bbc939c2168-44c304e03ce0e641.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T19:05:02Z" message: 'load-balancer-api-internal: tcp connection to af4a9f7b03b2e43ffbf58bbc939c2168-44c304e03ce0e641.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.06688ms message: 'load-balancer-api-internal: tcp connection to af4a9f7b03b2e43ffbf58bbc939c2168-44c304e03ce0e641.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:41:02Z" - latency: 7.985258ms message: 'load-balancer-api-internal: resolved host name af4a9f7b03b2e43ffbf58bbc939c2168-44c304e03ce0e641.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T19:41:02Z" - latency: 4.443852ms message: 'load-balancer-api-internal: tcp connection to af4a9f7b03b2e43ffbf58bbc939c2168-44c304e03ce0e641.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:40:02Z" - latency: 8.237999ms message: 'load-balancer-api-internal: resolved host name af4a9f7b03b2e43ffbf58bbc939c2168-44c304e03ce0e641.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T19:40:02Z" - latency: 5.561997ms message: 'load-balancer-api-internal: tcp connection to af4a9f7b03b2e43ffbf58bbc939c2168-44c304e03ce0e641.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:39:02Z" - latency: 7.15955ms message: 'load-balancer-api-internal: resolved host name af4a9f7b03b2e43ffbf58bbc939c2168-44c304e03ce0e641.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T19:39:02Z" - latency: 4.493564ms message: 'load-balancer-api-internal: tcp connection to af4a9f7b03b2e43ffbf58bbc939c2168-44c304e03ce0e641.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:38:02Z" - latency: 14.049126ms message: 'load-balancer-api-internal: resolved host name af4a9f7b03b2e43ffbf58bbc939c2168-44c304e03ce0e641.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T19:38:02Z" - latency: 5.298547ms message: 'load-balancer-api-internal: tcp connection to af4a9f7b03b2e43ffbf58bbc939c2168-44c304e03ce0e641.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:37:02Z" - latency: 6.833308ms message: 'load-balancer-api-internal: resolved host name af4a9f7b03b2e43ffbf58bbc939c2168-44c304e03ce0e641.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T19:37:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T18:59:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-150-to-network-check-target-ip-10-0-132-150 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-150.ec2.internal uid: 3e10f856-d456-430a-ae50-7106af39af69 resourceVersion: "63658" uid: 5dde88f6-e64c-4f12-9431-5c8fc8a5699a spec: sourcePod: network-check-source-7bc5b6bf85-hvh9k targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-22T19:06:02Z" message: 'network-check-target-ip-10-0-132-150: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 949.12µs message: 'network-check-target-ip-10-0-132-150: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:41:02Z" - latency: 1.082587ms message: 'network-check-target-ip-10-0-132-150: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:40:02Z" - latency: 1.686147ms message: 'network-check-target-ip-10-0-132-150: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:39:02Z" - latency: 848.903µs message: 'network-check-target-ip-10-0-132-150: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:38:02Z" - latency: 1.570773ms message: 'network-check-target-ip-10-0-132-150: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:37:02Z" - latency: 1.135553ms message: 'network-check-target-ip-10-0-132-150: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:36:02Z" - latency: 1.103696ms message: 'network-check-target-ip-10-0-132-150: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:35:02Z" - latency: 1.61612ms message: 'network-check-target-ip-10-0-132-150: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:34:02Z" - latency: 1.151019ms message: 'network-check-target-ip-10-0-132-150: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:33:02Z" - latency: 953.831µs message: 'network-check-target-ip-10-0-132-150: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:32:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T18:59:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-150-to-network-check-target-ip-10-0-136-84 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-150.ec2.internal uid: 3e10f856-d456-430a-ae50-7106af39af69 resourceVersion: "63659" uid: bdea2e0f-d076-4d24-889e-bfd7af010a74 spec: sourcePod: network-check-source-7bc5b6bf85-hvh9k targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-22T19:06:02Z" message: 'network-check-target-ip-10-0-136-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.68572ms message: 'network-check-target-ip-10-0-136-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:41:02Z" - latency: 2.398435ms message: 'network-check-target-ip-10-0-136-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:40:02Z" - latency: 2.993893ms message: 'network-check-target-ip-10-0-136-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:39:02Z" - latency: 2.217643ms message: 'network-check-target-ip-10-0-136-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:38:02Z" - latency: 2.836578ms message: 'network-check-target-ip-10-0-136-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:37:02Z" - latency: 2.091747ms message: 'network-check-target-ip-10-0-136-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:36:02Z" - latency: 2.028448ms message: 'network-check-target-ip-10-0-136-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:35:02Z" - latency: 2.393073ms message: 'network-check-target-ip-10-0-136-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:34:02Z" - latency: 2.493863ms message: 'network-check-target-ip-10-0-136-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:33:02Z" - latency: 1.974799ms message: 'network-check-target-ip-10-0-136-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:32:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T18:59:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-150-to-network-check-target-ip-10-0-142-177 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-150.ec2.internal uid: 3e10f856-d456-430a-ae50-7106af39af69 resourceVersion: "63660" uid: cec3d5f3-1af1-4913-84b1-bd734b85d69e spec: sourcePod: network-check-source-7bc5b6bf85-hvh9k targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-22T19:06:02Z" message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.463478ms message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:41:02Z" - latency: 2.535565ms message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:40:02Z" - latency: 2.561528ms message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:39:02Z" - latency: 2.391607ms message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:38:02Z" - latency: 2.536392ms message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:37:02Z" - latency: 2.676031ms message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:36:02Z" - latency: 2.691969ms message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:35:02Z" - latency: 2.50752ms message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:34:02Z" - latency: 2.497655ms message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:33:02Z" - latency: 2.6682ms message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:32:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T18:59:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-150-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-150.ec2.internal uid: 3e10f856-d456-430a-ae50-7106af39af69 resourceVersion: "63661" uid: 45887bab-5457-4688-92fd-2c46be78fbef spec: sourcePod: network-check-source-7bc5b6bf85-hvh9k targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-22T19:05:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 973.848µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:41:02Z" - latency: 2.040018ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T19:41:02Z" - latency: 1.00849ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:40:02Z" - latency: 1.871828ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T19:40:02Z" - latency: 1.205831ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:39:02Z" - latency: 1.851833ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T19:39:02Z" - latency: 1.251368ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:38:02Z" - latency: 1.825847ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T19:38:02Z" - latency: 904.542µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:37:02Z" - latency: 1.60298ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T19:37:02Z" kind: List metadata: resourceVersion: ""