apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T23:12:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-143-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-143.ec2.internal uid: 7f654453-f462-4d76-a536-126444053e91 resourceVersion: "23248" uid: 75ec0cfd-8111-4a64-b392-ee55af111771 spec: sourcePod: network-check-source-685456655f-jl4jc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-09T23:19:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 886.257µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:19:23Z" - latency: 888.503µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:18:23Z" - latency: 960.41µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:17:23Z" - latency: 1.338711ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:16:23Z" - latency: 1.385609ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:15:23Z" - latency: 1.617418ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:14:23Z" - latency: 1.372514ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:13:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T23:12:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-143-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-143.ec2.internal uid: 7f654453-f462-4d76-a536-126444053e91 resourceVersion: "22187" uid: bb25fe66-7a01-446b-8cbf-79a46e32217e spec: sourcePod: network-check-source-685456655f-jl4jc targetEndpoint: a20d6d4f43a904ccca05303f0daa2fe4-bed0139caa420563.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T23:18:23Z" message: 'load-balancer-api-external: tcp connection to a20d6d4f43a904ccca05303f0daa2fe4-bed0139caa420563.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.64894ms message: 'load-balancer-api-external: tcp connection to a20d6d4f43a904ccca05303f0daa2fe4-bed0139caa420563.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:18:23Z" - latency: 7.832501ms message: 'load-balancer-api-external: resolved host name a20d6d4f43a904ccca05303f0daa2fe4-bed0139caa420563.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T23:18:23Z" - latency: 4.055143ms message: 'load-balancer-api-external: tcp connection to a20d6d4f43a904ccca05303f0daa2fe4-bed0139caa420563.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:17:23Z" - latency: 6.269913ms message: 'load-balancer-api-external: resolved host name a20d6d4f43a904ccca05303f0daa2fe4-bed0139caa420563.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T23:17:23Z" - latency: 3.949721ms message: 'load-balancer-api-external: tcp connection to a20d6d4f43a904ccca05303f0daa2fe4-bed0139caa420563.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:16:23Z" - latency: 8.185885ms message: 'load-balancer-api-external: resolved host name a20d6d4f43a904ccca05303f0daa2fe4-bed0139caa420563.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T23:16:23Z" - latency: 4.189553ms message: 'load-balancer-api-external: tcp connection to a20d6d4f43a904ccca05303f0daa2fe4-bed0139caa420563.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:15:23Z" - latency: 8.866726ms message: 'load-balancer-api-external: resolved host name a20d6d4f43a904ccca05303f0daa2fe4-bed0139caa420563.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T23:15:23Z" - latency: 4.747384ms message: 'load-balancer-api-external: tcp connection to a20d6d4f43a904ccca05303f0daa2fe4-bed0139caa420563.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:14:23Z" - latency: 9.81273ms message: 'load-balancer-api-external: resolved host name a20d6d4f43a904ccca05303f0daa2fe4-bed0139caa420563.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T23:14:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T23:12:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-143-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-143.ec2.internal uid: 7f654453-f462-4d76-a536-126444053e91 resourceVersion: "22186" uid: 699b28c0-370b-4498-9b62-fefd7dabedb8 spec: sourcePod: network-check-source-685456655f-jl4jc targetEndpoint: a20d6d4f43a904ccca05303f0daa2fe4-bed0139caa420563.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T23:18:23Z" message: 'load-balancer-api-internal: tcp connection to a20d6d4f43a904ccca05303f0daa2fe4-bed0139caa420563.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.627066ms message: 'load-balancer-api-internal: tcp connection to a20d6d4f43a904ccca05303f0daa2fe4-bed0139caa420563.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:18:23Z" - latency: 7.881322ms message: 'load-balancer-api-internal: resolved host name a20d6d4f43a904ccca05303f0daa2fe4-bed0139caa420563.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T23:18:23Z" - latency: 4.060454ms message: 'load-balancer-api-internal: tcp connection to a20d6d4f43a904ccca05303f0daa2fe4-bed0139caa420563.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:17:23Z" - latency: 6.315267ms message: 'load-balancer-api-internal: resolved host name a20d6d4f43a904ccca05303f0daa2fe4-bed0139caa420563.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T23:17:23Z" - latency: 3.966814ms message: 'load-balancer-api-internal: tcp connection to a20d6d4f43a904ccca05303f0daa2fe4-bed0139caa420563.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:16:23Z" - latency: 8.249945ms message: 'load-balancer-api-internal: resolved host name a20d6d4f43a904ccca05303f0daa2fe4-bed0139caa420563.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T23:16:23Z" - latency: 2.893159ms message: 'load-balancer-api-internal: tcp connection to a20d6d4f43a904ccca05303f0daa2fe4-bed0139caa420563.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:15:23Z" - latency: 8.818974ms message: 'load-balancer-api-internal: resolved host name a20d6d4f43a904ccca05303f0daa2fe4-bed0139caa420563.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T23:15:23Z" - latency: 4.73898ms message: 'load-balancer-api-internal: tcp connection to a20d6d4f43a904ccca05303f0daa2fe4-bed0139caa420563.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:14:23Z" - latency: 9.847899ms message: 'load-balancer-api-internal: resolved host name a20d6d4f43a904ccca05303f0daa2fe4-bed0139caa420563.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T23:14:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T23:12:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-143-to-network-check-target-ip-10-0-137-106 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-143.ec2.internal uid: 7f654453-f462-4d76-a536-126444053e91 resourceVersion: "23246" uid: 1cd13d9c-751f-4af9-8754-ff74efed72db spec: sourcePod: network-check-source-685456655f-jl4jc targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-09T23:19:23Z" message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.202122ms message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:19:23Z" - latency: 1.880307ms message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:18:23Z" - latency: 2.10808ms message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:17:23Z" - latency: 2.537901ms message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:16:23Z" - latency: 2.196118ms message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:15:23Z" - latency: 2.227675ms message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:14:23Z" - latency: 2.13161ms message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:13:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T23:12:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-143-to-network-check-target-ip-10-0-137-143 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-143.ec2.internal uid: 7f654453-f462-4d76-a536-126444053e91 resourceVersion: "23245" uid: 9babdb4d-9d54-4078-9474-1ecf97023af0 spec: sourcePod: network-check-source-685456655f-jl4jc targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-09T23:19:23Z" message: 'network-check-target-ip-10-0-137-143: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 889.446µs message: 'network-check-target-ip-10-0-137-143: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:19:23Z" - latency: 816.708µs message: 'network-check-target-ip-10-0-137-143: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:18:23Z" - latency: 854.408µs message: 'network-check-target-ip-10-0-137-143: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:17:23Z" - latency: 812.32µs message: 'network-check-target-ip-10-0-137-143: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:16:23Z" - latency: 1.527849ms message: 'network-check-target-ip-10-0-137-143: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:15:23Z" - latency: 2.095338ms message: 'network-check-target-ip-10-0-137-143: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:14:23Z" - latency: 1.254999ms message: 'network-check-target-ip-10-0-137-143: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:13:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T23:12:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-143-to-network-check-target-ip-10-0-143-254 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-143.ec2.internal uid: 7f654453-f462-4d76-a536-126444053e91 resourceVersion: "23247" uid: 456a16e5-143a-4e0f-b599-e9a519d7ac0a spec: sourcePod: network-check-source-685456655f-jl4jc targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-09T23:19:23Z" message: 'network-check-target-ip-10-0-143-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.416111ms message: 'network-check-target-ip-10-0-143-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:19:23Z" - latency: 2.379034ms message: 'network-check-target-ip-10-0-143-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:18:23Z" - latency: 2.155892ms message: 'network-check-target-ip-10-0-143-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:17:23Z" - latency: 2.340255ms message: 'network-check-target-ip-10-0-143-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:16:23Z" - latency: 2.793446ms message: 'network-check-target-ip-10-0-143-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:15:23Z" - latency: 2.866185ms message: 'network-check-target-ip-10-0-143-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:14:23Z" - latency: 2.609395ms message: 'network-check-target-ip-10-0-143-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:13:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T23:12:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-143-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-143.ec2.internal uid: 7f654453-f462-4d76-a536-126444053e91 resourceVersion: "22185" uid: e55699b1-94a9-4e63-8ba7-94e8a2f525b0 spec: sourcePod: network-check-source-685456655f-jl4jc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-09T23:18:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 930.326µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:18:23Z" - latency: 1.734651ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T23:18:23Z" - latency: 890.571µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:17:23Z" - latency: 1.921457ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T23:17:23Z" - latency: 844.906µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:16:23Z" - latency: 1.753545ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T23:16:23Z" - latency: 997.181µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:15:23Z" - latency: 1.772809ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T23:15:23Z" - latency: 1.005963ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T23:14:23Z" - latency: 2.234911ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T23:14:23Z" kind: List metadata: resourceVersion: ""