apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:39:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-106-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-106.ec2.internal uid: b121eb3c-c143-4d10-95a7-51cd33248732 resourceVersion: "32036" uid: d4598d78-e8d1-4e9c-ab5e-0c548e70b519 spec: sourcePod: network-check-source-989f8b8dc-7j6j6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T20:46:01Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.083293ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:21:01Z" - latency: 1.062115ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:20:01Z" - latency: 1.201687ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:19:01Z" - latency: 959.294µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:18:01Z" - latency: 902.39µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:17:01Z" - latency: 895.949µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:16:01Z" - latency: 1.08424ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:15:01Z" - latency: 993.051µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:14:01Z" - latency: 1.052845ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:13:01Z" - latency: 1.006538ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:12:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:39:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-106-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-106.ec2.internal uid: b121eb3c-c143-4d10-95a7-51cd33248732 resourceVersion: "32457" uid: e21ce722-fb88-4118-8d3a-f4e0d98d11e6 spec: sourcePod: network-check-source-989f8b8dc-7j6j6 targetEndpoint: a45d3a63166594b94819e2a571f16648-a4edbc3f375c7a78.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T20:46:01Z" message: 'load-balancer-api-external: tcp connection to a45d3a63166594b94819e2a571f16648-a4edbc3f375c7a78.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.247134ms message: 'load-balancer-api-external: tcp connection to a45d3a63166594b94819e2a571f16648-a4edbc3f375c7a78.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:22:01Z" - latency: 6.219022ms message: 'load-balancer-api-external: resolved host name a45d3a63166594b94819e2a571f16648-a4edbc3f375c7a78.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:22:01Z" - latency: 4.796554ms message: 'load-balancer-api-external: tcp connection to a45d3a63166594b94819e2a571f16648-a4edbc3f375c7a78.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:21:01Z" - latency: 7.686474ms message: 'load-balancer-api-external: resolved host name a45d3a63166594b94819e2a571f16648-a4edbc3f375c7a78.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:21:01Z" - latency: 5.848148ms message: 'load-balancer-api-external: tcp connection to a45d3a63166594b94819e2a571f16648-a4edbc3f375c7a78.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:20:01Z" - latency: 6.205489ms message: 'load-balancer-api-external: resolved host name a45d3a63166594b94819e2a571f16648-a4edbc3f375c7a78.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:20:01Z" - latency: 5.686719ms message: 'load-balancer-api-external: tcp connection to a45d3a63166594b94819e2a571f16648-a4edbc3f375c7a78.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:19:01Z" - latency: 6.828934ms message: 'load-balancer-api-external: resolved host name a45d3a63166594b94819e2a571f16648-a4edbc3f375c7a78.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:19:01Z" - latency: 4.353977ms message: 'load-balancer-api-external: tcp connection to a45d3a63166594b94819e2a571f16648-a4edbc3f375c7a78.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:18:01Z" - latency: 6.049417ms message: 'load-balancer-api-external: resolved host name a45d3a63166594b94819e2a571f16648-a4edbc3f375c7a78.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:18:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:39:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-106-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-106.ec2.internal uid: b121eb3c-c143-4d10-95a7-51cd33248732 resourceVersion: "32456" uid: 08fa28e9-89d2-4a28-9294-0bd5e970c40f spec: sourcePod: network-check-source-989f8b8dc-7j6j6 targetEndpoint: a45d3a63166594b94819e2a571f16648-a4edbc3f375c7a78.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T20:46:01Z" message: 'load-balancer-api-internal: tcp connection to a45d3a63166594b94819e2a571f16648-a4edbc3f375c7a78.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.77579ms message: 'load-balancer-api-internal: tcp connection to a45d3a63166594b94819e2a571f16648-a4edbc3f375c7a78.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:22:01Z" - latency: 6.245007ms message: 'load-balancer-api-internal: resolved host name a45d3a63166594b94819e2a571f16648-a4edbc3f375c7a78.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:22:01Z" - latency: 4.739982ms message: 'load-balancer-api-internal: tcp connection to a45d3a63166594b94819e2a571f16648-a4edbc3f375c7a78.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:21:01Z" - latency: 7.839936ms message: 'load-balancer-api-internal: resolved host name a45d3a63166594b94819e2a571f16648-a4edbc3f375c7a78.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:21:01Z" - latency: 5.800254ms message: 'load-balancer-api-internal: tcp connection to a45d3a63166594b94819e2a571f16648-a4edbc3f375c7a78.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:20:01Z" - latency: 6.247616ms message: 'load-balancer-api-internal: resolved host name a45d3a63166594b94819e2a571f16648-a4edbc3f375c7a78.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:20:01Z" - latency: 5.674155ms message: 'load-balancer-api-internal: tcp connection to a45d3a63166594b94819e2a571f16648-a4edbc3f375c7a78.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:19:01Z" - latency: 6.874908ms message: 'load-balancer-api-internal: resolved host name a45d3a63166594b94819e2a571f16648-a4edbc3f375c7a78.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:19:01Z" - latency: 4.366928ms message: 'load-balancer-api-internal: tcp connection to a45d3a63166594b94819e2a571f16648-a4edbc3f375c7a78.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:18:01Z" - latency: 5.921569ms message: 'load-balancer-api-internal: resolved host name a45d3a63166594b94819e2a571f16648-a4edbc3f375c7a78.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T21:18:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:39:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-106-to-network-check-target-ip-10-0-132-244 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-106.ec2.internal uid: b121eb3c-c143-4d10-95a7-51cd33248732 resourceVersion: "32034" uid: 57382213-844f-41eb-887b-7c9a0c716e74 spec: sourcePod: network-check-source-989f8b8dc-7j6j6 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T20:46:01Z" message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.324584ms message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:21:01Z" - latency: 2.067443ms message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:20:01Z" - latency: 2.058907ms message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:19:01Z" - latency: 2.095318ms message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:18:01Z" - latency: 1.872791ms message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:17:01Z" - latency: 1.889989ms message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:16:01Z" - latency: 2.086532ms message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:15:01Z" - latency: 2.217015ms message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:14:01Z" - latency: 2.260062ms message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:13:01Z" - latency: 2.045326ms message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:12:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:39:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-106-to-network-check-target-ip-10-0-137-106 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-106.ec2.internal uid: b121eb3c-c143-4d10-95a7-51cd33248732 resourceVersion: "32033" uid: 82e4eaef-5d43-4be9-a51a-40dfc1079798 spec: sourcePod: network-check-source-989f8b8dc-7j6j6 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T20:46:01Z" message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.434085ms message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:21:01Z" - latency: 896.998µs message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:20:01Z" - latency: 907.655µs message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:19:01Z" - latency: 1.322468ms message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:18:01Z" - latency: 765.782µs message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:17:01Z" - latency: 836.871µs message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:16:01Z" - latency: 1.267234ms message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:15:01Z" - latency: 966.754µs message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:14:01Z" - latency: 1.161586ms message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:13:01Z" - latency: 886.628µs message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:12:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:39:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-106-to-network-check-target-ip-10-0-142-142 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-106.ec2.internal uid: b121eb3c-c143-4d10-95a7-51cd33248732 resourceVersion: "32035" uid: 51b91c33-ca5c-44bb-9787-e7adabc46339 spec: sourcePod: network-check-source-989f8b8dc-7j6j6 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T20:46:01Z" message: 'network-check-target-ip-10-0-142-142: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.235493ms message: 'network-check-target-ip-10-0-142-142: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:21:01Z" - latency: 2.154072ms message: 'network-check-target-ip-10-0-142-142: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:20:01Z" - latency: 2.043306ms message: 'network-check-target-ip-10-0-142-142: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:19:01Z" - latency: 2.155318ms message: 'network-check-target-ip-10-0-142-142: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:18:01Z" - latency: 2.064497ms message: 'network-check-target-ip-10-0-142-142: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:17:01Z" - latency: 1.99764ms message: 'network-check-target-ip-10-0-142-142: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:16:01Z" - latency: 1.790667ms message: 'network-check-target-ip-10-0-142-142: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:15:01Z" - latency: 2.097388ms message: 'network-check-target-ip-10-0-142-142: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:14:01Z" - latency: 1.958169ms message: 'network-check-target-ip-10-0-142-142: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:13:01Z" - latency: 2.200661ms message: 'network-check-target-ip-10-0-142-142: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:12:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:39:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-106-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-106.ec2.internal uid: b121eb3c-c143-4d10-95a7-51cd33248732 resourceVersion: "32455" uid: bb3b9c67-b0b7-4ee4-b6b1-02d454af3e78 spec: sourcePod: network-check-source-989f8b8dc-7j6j6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T20:46:01Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.028174ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:22:01Z" - latency: 1.842233ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T21:22:01Z" - latency: 893.438µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:21:01Z" - latency: 2.415687ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T21:21:01Z" - latency: 1.123652ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:20:01Z" - latency: 1.724108ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T21:20:01Z" - latency: 846.292µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:19:01Z" - latency: 1.922805ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T21:19:01Z" - latency: 716.133µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:18:01Z" - latency: 1.668889ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T21:18:01Z" kind: List metadata: resourceVersion: ""