apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T19:18:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-142-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-142.ec2.internal uid: baacef2c-e1e1-4a1b-988f-1ade227ba5e9 resourceVersion: "62689" uid: 932f384b-1d12-4915-8c52-acec85d8ac82 spec: sourcePod: network-check-source-7bc5b6bf85-46n86 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-20T19:25:18Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.08777ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:00:18Z" - latency: 919.616µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:59:18Z" - latency: 910.524µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:58:18Z" - latency: 1.160596ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:57:18Z" - latency: 968.699µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:56:18Z" - latency: 1.027675ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:55:18Z" - latency: 1.353127ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:54:18Z" - latency: 1.196691ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:53:18Z" - latency: 1.20086ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:52:18Z" - latency: 1.123151ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:51:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T19:18:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-142-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-142.ec2.internal uid: baacef2c-e1e1-4a1b-988f-1ade227ba5e9 resourceVersion: "62691" uid: 9bf9db5a-bb39-4e87-ba8c-38a996677bde spec: sourcePod: network-check-source-7bc5b6bf85-46n86 targetEndpoint: a60b52ad432e7457fb60cea60b6a26f6-6433bf54ef7515d0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T19:24:18Z" message: 'load-balancer-api-external: tcp connection to a60b52ad432e7457fb60cea60b6a26f6-6433bf54ef7515d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.41232ms message: 'load-balancer-api-external: tcp connection to a60b52ad432e7457fb60cea60b6a26f6-6433bf54ef7515d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:00:18Z" - latency: 7.504923ms message: 'load-balancer-api-external: resolved host name a60b52ad432e7457fb60cea60b6a26f6-6433bf54ef7515d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T20:00:18Z" - latency: 3.846708ms message: 'load-balancer-api-external: tcp connection to a60b52ad432e7457fb60cea60b6a26f6-6433bf54ef7515d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:59:18Z" - latency: 10.53564ms message: 'load-balancer-api-external: resolved host name a60b52ad432e7457fb60cea60b6a26f6-6433bf54ef7515d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T19:59:18Z" - latency: 5.339871ms message: 'load-balancer-api-external: tcp connection to a60b52ad432e7457fb60cea60b6a26f6-6433bf54ef7515d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:58:18Z" - latency: 7.720148ms message: 'load-balancer-api-external: resolved host name a60b52ad432e7457fb60cea60b6a26f6-6433bf54ef7515d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T19:58:18Z" - latency: 3.537183ms message: 'load-balancer-api-external: tcp connection to a60b52ad432e7457fb60cea60b6a26f6-6433bf54ef7515d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:57:18Z" - latency: 7.408132ms message: 'load-balancer-api-external: resolved host name a60b52ad432e7457fb60cea60b6a26f6-6433bf54ef7515d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T19:57:18Z" - latency: 3.649047ms message: 'load-balancer-api-external: tcp connection to a60b52ad432e7457fb60cea60b6a26f6-6433bf54ef7515d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:56:18Z" - latency: 13.700806ms message: 'load-balancer-api-external: resolved host name a60b52ad432e7457fb60cea60b6a26f6-6433bf54ef7515d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T19:56:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T19:18:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-142-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-142.ec2.internal uid: baacef2c-e1e1-4a1b-988f-1ade227ba5e9 resourceVersion: "62690" uid: f909c2c6-db35-4a93-91a5-895cf150a338 spec: sourcePod: network-check-source-7bc5b6bf85-46n86 targetEndpoint: a60b52ad432e7457fb60cea60b6a26f6-6433bf54ef7515d0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T19:24:18Z" message: 'load-balancer-api-internal: tcp connection to a60b52ad432e7457fb60cea60b6a26f6-6433bf54ef7515d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.769129ms message: 'load-balancer-api-internal: tcp connection to a60b52ad432e7457fb60cea60b6a26f6-6433bf54ef7515d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:00:18Z" - latency: 7.53063ms message: 'load-balancer-api-internal: resolved host name a60b52ad432e7457fb60cea60b6a26f6-6433bf54ef7515d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T20:00:18Z" - latency: 3.859229ms message: 'load-balancer-api-internal: tcp connection to a60b52ad432e7457fb60cea60b6a26f6-6433bf54ef7515d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:59:18Z" - latency: 10.43738ms message: 'load-balancer-api-internal: resolved host name a60b52ad432e7457fb60cea60b6a26f6-6433bf54ef7515d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T19:59:18Z" - latency: 5.330054ms message: 'load-balancer-api-internal: tcp connection to a60b52ad432e7457fb60cea60b6a26f6-6433bf54ef7515d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:58:18Z" - latency: 7.748268ms message: 'load-balancer-api-internal: resolved host name a60b52ad432e7457fb60cea60b6a26f6-6433bf54ef7515d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T19:58:18Z" - latency: 3.542552ms message: 'load-balancer-api-internal: tcp connection to a60b52ad432e7457fb60cea60b6a26f6-6433bf54ef7515d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:57:18Z" - latency: 7.442976ms message: 'load-balancer-api-internal: resolved host name a60b52ad432e7457fb60cea60b6a26f6-6433bf54ef7515d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T19:57:18Z" - latency: 3.91908ms message: 'load-balancer-api-internal: tcp connection to a60b52ad432e7457fb60cea60b6a26f6-6433bf54ef7515d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:56:18Z" - latency: 13.718626ms message: 'load-balancer-api-internal: resolved host name a60b52ad432e7457fb60cea60b6a26f6-6433bf54ef7515d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T19:56:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T19:18:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-142-to-network-check-target-ip-10-0-132-142 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-142.ec2.internal uid: baacef2c-e1e1-4a1b-988f-1ade227ba5e9 resourceVersion: "62685" uid: 1a876580-190c-413f-a112-74e8d2d83b46 spec: sourcePod: network-check-source-7bc5b6bf85-46n86 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-20T19:25:18Z" message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.055581ms message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:00:18Z" - latency: 885.164µs message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:59:18Z" - latency: 1.804066ms message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:58:18Z" - latency: 1.342629ms message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:57:18Z" - latency: 1.12656ms message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:56:18Z" - latency: 910.024µs message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:55:18Z" - latency: 1.473652ms message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:54:18Z" - latency: 1.419227ms message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:53:18Z" - latency: 990.68µs message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:52:18Z" - latency: 953.658µs message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:51:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T19:18:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-142-to-network-check-target-ip-10-0-135-129 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-142.ec2.internal uid: baacef2c-e1e1-4a1b-988f-1ade227ba5e9 resourceVersion: "62686" uid: 2eb35ee7-add4-4066-a5ed-6100e44488cc spec: sourcePod: network-check-source-7bc5b6bf85-46n86 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-20T19:25:18Z" message: 'network-check-target-ip-10-0-135-129: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.554146ms message: 'network-check-target-ip-10-0-135-129: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:00:18Z" - latency: 2.412705ms message: 'network-check-target-ip-10-0-135-129: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:59:18Z" - latency: 2.52522ms message: 'network-check-target-ip-10-0-135-129: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:58:18Z" - latency: 2.478725ms message: 'network-check-target-ip-10-0-135-129: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:57:18Z" - latency: 2.024872ms message: 'network-check-target-ip-10-0-135-129: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:56:18Z" - latency: 2.006852ms message: 'network-check-target-ip-10-0-135-129: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:55:18Z" - latency: 2.968908ms message: 'network-check-target-ip-10-0-135-129: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:54:18Z" - latency: 2.353548ms message: 'network-check-target-ip-10-0-135-129: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:53:18Z" - latency: 2.507451ms message: 'network-check-target-ip-10-0-135-129: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:52:18Z" - latency: 2.404299ms message: 'network-check-target-ip-10-0-135-129: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:51:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T19:18:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-142-to-network-check-target-ip-10-0-141-43 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-142.ec2.internal uid: baacef2c-e1e1-4a1b-988f-1ade227ba5e9 resourceVersion: "62687" uid: 5fea4d7c-0803-4d9e-ba15-e790f20169d5 spec: sourcePod: network-check-source-7bc5b6bf85-46n86 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-20T19:25:18Z" message: 'network-check-target-ip-10-0-141-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.565233ms message: 'network-check-target-ip-10-0-141-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:00:18Z" - latency: 2.366901ms message: 'network-check-target-ip-10-0-141-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:59:18Z" - latency: 2.417709ms message: 'network-check-target-ip-10-0-141-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:58:18Z" - latency: 2.436093ms message: 'network-check-target-ip-10-0-141-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:57:18Z" - latency: 2.479278ms message: 'network-check-target-ip-10-0-141-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:56:18Z" - latency: 2.555291ms message: 'network-check-target-ip-10-0-141-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:55:18Z" - latency: 2.473418ms message: 'network-check-target-ip-10-0-141-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:54:18Z" - latency: 2.259845ms message: 'network-check-target-ip-10-0-141-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:53:18Z" - latency: 2.414558ms message: 'network-check-target-ip-10-0-141-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:52:18Z" - latency: 2.379897ms message: 'network-check-target-ip-10-0-141-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:51:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T19:18:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-142-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-142.ec2.internal uid: baacef2c-e1e1-4a1b-988f-1ade227ba5e9 resourceVersion: "62688" uid: a0942dd1-6363-403e-9f69-e92be36e7cd9 spec: sourcePod: network-check-source-7bc5b6bf85-46n86 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-20T19:24:18Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 897.65µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:00:18Z" - latency: 1.977476ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T20:00:18Z" - latency: 1.040254ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:59:18Z" - latency: 2.251986ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T19:59:18Z" - latency: 806.881µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:58:18Z" - latency: 2.214951ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T19:58:18Z" - latency: 1.181556ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:57:18Z" - latency: 2.062689ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T19:57:18Z" - latency: 1.123184ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T19:56:18Z" - latency: 1.771092ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T19:56:18Z" kind: List metadata: resourceVersion: ""