apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T21:10:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-66-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-66.ec2.internal uid: 0d933394-5407-47ca-80cf-adb667f042b5 resourceVersion: "71003" uid: efd7d511-d6f5-492a-bfd9-1797dff56e58 spec: sourcePod: network-check-source-7d88cb55d8-5mbkm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T21:17: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.127608ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:59:02Z" - latency: 1.533121ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:58:02Z" - latency: 803.979µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:57:02Z" - latency: 1.023556ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:56:02Z" - latency: 1.339134ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:55:02Z" - latency: 849.584µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:54:02Z" - latency: 1.18347ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:53:02Z" - latency: 1.087268ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:52:02Z" - latency: 811.446µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:51:02Z" - latency: 875.431µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:50:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T21:10:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-66-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-66.ec2.internal uid: 0d933394-5407-47ca-80cf-adb667f042b5 resourceVersion: "69769" uid: b664055f-d74d-40e0-bdda-661373f8be88 spec: sourcePod: network-check-source-7d88cb55d8-5mbkm targetEndpoint: a078845a2198b4eb598323db375ed653-8c7fbedf04a78960.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T21:16:02Z" message: 'load-balancer-api-external: tcp connection to a078845a2198b4eb598323db375ed653-8c7fbedf04a78960.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.059323ms message: 'load-balancer-api-external: tcp connection to a078845a2198b4eb598323db375ed653-8c7fbedf04a78960.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:58:02Z" - latency: 7.864733ms message: 'load-balancer-api-external: resolved host name a078845a2198b4eb598323db375ed653-8c7fbedf04a78960.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:58:02Z" - latency: 4.531605ms message: 'load-balancer-api-external: tcp connection to a078845a2198b4eb598323db375ed653-8c7fbedf04a78960.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:57:02Z" - latency: 8.697713ms message: 'load-balancer-api-external: resolved host name a078845a2198b4eb598323db375ed653-8c7fbedf04a78960.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:57:02Z" - latency: 6.573847ms message: 'load-balancer-api-external: tcp connection to a078845a2198b4eb598323db375ed653-8c7fbedf04a78960.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:56:02Z" - latency: 10.103793ms message: 'load-balancer-api-external: resolved host name a078845a2198b4eb598323db375ed653-8c7fbedf04a78960.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:56:02Z" - latency: 4.569514ms message: 'load-balancer-api-external: tcp connection to a078845a2198b4eb598323db375ed653-8c7fbedf04a78960.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:55:02Z" - latency: 8.526642ms message: 'load-balancer-api-external: resolved host name a078845a2198b4eb598323db375ed653-8c7fbedf04a78960.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:55:02Z" - latency: 3.288039ms message: 'load-balancer-api-external: tcp connection to a078845a2198b4eb598323db375ed653-8c7fbedf04a78960.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:54:02Z" - latency: 9.77376ms message: 'load-balancer-api-external: resolved host name a078845a2198b4eb598323db375ed653-8c7fbedf04a78960.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:54:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T21:10:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-66-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-66.ec2.internal uid: 0d933394-5407-47ca-80cf-adb667f042b5 resourceVersion: "69770" uid: 4691e434-fb98-4fc3-8fd0-1560d35f924d spec: sourcePod: network-check-source-7d88cb55d8-5mbkm targetEndpoint: a078845a2198b4eb598323db375ed653-8c7fbedf04a78960.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T21:16:02Z" message: 'load-balancer-api-internal: tcp connection to a078845a2198b4eb598323db375ed653-8c7fbedf04a78960.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.061781ms message: 'load-balancer-api-internal: tcp connection to a078845a2198b4eb598323db375ed653-8c7fbedf04a78960.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:58:02Z" - latency: 7.942914ms message: 'load-balancer-api-internal: resolved host name a078845a2198b4eb598323db375ed653-8c7fbedf04a78960.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:58:02Z" - latency: 4.850422ms message: 'load-balancer-api-internal: tcp connection to a078845a2198b4eb598323db375ed653-8c7fbedf04a78960.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:57:02Z" - latency: 8.748961ms message: 'load-balancer-api-internal: resolved host name a078845a2198b4eb598323db375ed653-8c7fbedf04a78960.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:57:02Z" - latency: 3.842526ms message: 'load-balancer-api-internal: tcp connection to a078845a2198b4eb598323db375ed653-8c7fbedf04a78960.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:56:02Z" - latency: 10.136648ms message: 'load-balancer-api-internal: resolved host name a078845a2198b4eb598323db375ed653-8c7fbedf04a78960.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:56:02Z" - latency: 4.692368ms message: 'load-balancer-api-internal: tcp connection to a078845a2198b4eb598323db375ed653-8c7fbedf04a78960.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:55:02Z" - latency: 8.551528ms message: 'load-balancer-api-internal: resolved host name a078845a2198b4eb598323db375ed653-8c7fbedf04a78960.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:55:02Z" - latency: 3.368912ms message: 'load-balancer-api-internal: tcp connection to a078845a2198b4eb598323db375ed653-8c7fbedf04a78960.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:54:02Z" - latency: 9.822908ms message: 'load-balancer-api-internal: resolved host name a078845a2198b4eb598323db375ed653-8c7fbedf04a78960.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:54:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T21:10:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-66-to-network-check-target-ip-10-0-134-66 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-66.ec2.internal uid: 0d933394-5407-47ca-80cf-adb667f042b5 resourceVersion: "71000" uid: 0d337ca9-8178-4ef5-83c2-6876ed804938 spec: sourcePod: network-check-source-7d88cb55d8-5mbkm targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T21:17:02Z" message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.040325ms message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:59:02Z" - latency: 1.196961ms message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:58:02Z" - latency: 1.417348ms message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:57:02Z" - latency: 932.987µs message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:56:02Z" - latency: 789.135µs message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:55:02Z" - latency: 860.27µs message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:54:02Z" - latency: 965.486µs message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:53:02Z" - latency: 1.22374ms message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:52:02Z" - latency: 837.977µs message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:51:02Z" - latency: 1.121404ms message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:50:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T21:10:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-66-to-network-check-target-ip-10-0-138-99 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-66.ec2.internal uid: 0d933394-5407-47ca-80cf-adb667f042b5 resourceVersion: "71001" uid: 22dfafc3-8871-4b4d-9ba2-10e831bc9181 spec: sourcePod: network-check-source-7d88cb55d8-5mbkm targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T21:17:02Z" message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.865026ms message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:59:02Z" - latency: 1.999426ms message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:58:02Z" - latency: 2.013704ms message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:57:02Z" - latency: 1.921242ms message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:56:02Z" - latency: 1.937623ms message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:55:02Z" - latency: 1.789648ms message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:54:02Z" - latency: 1.807463ms message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:53:02Z" - latency: 2.105774ms message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:52:02Z" - latency: 2.011203ms message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:51:02Z" - latency: 1.82627ms message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:50:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T21:10:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-66-to-network-check-target-ip-10-0-143-168 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-66.ec2.internal uid: 0d933394-5407-47ca-80cf-adb667f042b5 resourceVersion: "71002" uid: 0b5a0c0e-58dc-4a25-8e7d-d9505d7a383b spec: sourcePod: network-check-source-7d88cb55d8-5mbkm targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T21:17:02Z" message: 'network-check-target-ip-10-0-143-168: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.895679ms message: 'network-check-target-ip-10-0-143-168: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:59:02Z" - latency: 2.112837ms message: 'network-check-target-ip-10-0-143-168: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:58:02Z" - latency: 2.532055ms message: 'network-check-target-ip-10-0-143-168: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:57:02Z" - latency: 2.43993ms message: 'network-check-target-ip-10-0-143-168: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:56:02Z" - latency: 1.920392ms message: 'network-check-target-ip-10-0-143-168: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:55:02Z" - latency: 2.104433ms message: 'network-check-target-ip-10-0-143-168: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:54:02Z" - latency: 2.165896ms message: 'network-check-target-ip-10-0-143-168: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:53:02Z" - latency: 2.469784ms message: 'network-check-target-ip-10-0-143-168: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:52:02Z" - latency: 2.474952ms message: 'network-check-target-ip-10-0-143-168: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:51:02Z" - latency: 2.379229ms message: 'network-check-target-ip-10-0-143-168: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:50:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T21:10:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-66-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-66.ec2.internal uid: 0d933394-5407-47ca-80cf-adb667f042b5 resourceVersion: "69768" uid: 9da43251-2d54-4567-8581-87a6856431e7 spec: sourcePod: network-check-source-7d88cb55d8-5mbkm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T21:16:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 966.364µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:58:02Z" - latency: 2.036383ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T21:58:02Z" - latency: 981.612µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:57:02Z" - latency: 2.015311ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T21:57:02Z" - latency: 1.211779ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:56:02Z" - latency: 1.899434ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T21:56:02Z" - latency: 806.046µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:55:02Z" - latency: 1.976914ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T21:55:02Z" - latency: 828.788µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:54:02Z" - latency: 1.721706ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T21:54:02Z" kind: List metadata: resourceVersion: ""