apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T18:45:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-179-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-179.us-west-2.compute.internal uid: 0bc97d9e-8430-4184-96fc-7e8a882299d8 resourceVersion: "110433" uid: 95616891-4d2e-4356-9ca6-916ca5d447c6 spec: sourcePod: network-check-source-6f78d59f99-mzf7t targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T18:52:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.041486ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:55:50Z" - latency: 1.377532ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:54:50Z" - latency: 1.53986ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:53:50Z" - latency: 1.634862ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:52:50Z" - latency: 957.905µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:51:50Z" - latency: 1.470121ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:50:50Z" - latency: 1.248497ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:49:50Z" - latency: 1.379312ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:48:50Z" - latency: 1.874393ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:47:50Z" - latency: 869.627µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:46:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T18:45:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-179-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-179.us-west-2.compute.internal uid: 0bc97d9e-8430-4184-96fc-7e8a882299d8 resourceVersion: "107840" uid: d1e85714-7193-434d-a9cd-3b8952eb4c2d spec: sourcePod: network-check-source-6f78d59f99-mzf7t targetEndpoint: a3904a6b916d941eabd9d7e63c223c68-8c1f0edaac096962.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T18:51:51Z" message: 'load-balancer-api-external: tcp connection to a3904a6b916d941eabd9d7e63c223c68-8c1f0edaac096962.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.546208ms message: 'load-balancer-api-external: tcp connection to a3904a6b916d941eabd9d7e63c223c68-8c1f0edaac096962.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:51:50Z" - latency: 7.249195ms message: 'load-balancer-api-external: resolved host name a3904a6b916d941eabd9d7e63c223c68-8c1f0edaac096962.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:51:50Z" - latency: 52.566161ms message: 'load-balancer-api-external: tcp connection to a3904a6b916d941eabd9d7e63c223c68-8c1f0edaac096962.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:50:50Z" - latency: 6.857538ms message: 'load-balancer-api-external: resolved host name a3904a6b916d941eabd9d7e63c223c68-8c1f0edaac096962.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:50:50Z" - latency: 56.041009ms message: 'load-balancer-api-external: tcp connection to a3904a6b916d941eabd9d7e63c223c68-8c1f0edaac096962.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:49:50Z" - latency: 6.974417ms message: 'load-balancer-api-external: resolved host name a3904a6b916d941eabd9d7e63c223c68-8c1f0edaac096962.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:49:50Z" - latency: 55.128986ms message: 'load-balancer-api-external: tcp connection to a3904a6b916d941eabd9d7e63c223c68-8c1f0edaac096962.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:48:50Z" - latency: 7.01188ms message: 'load-balancer-api-external: resolved host name a3904a6b916d941eabd9d7e63c223c68-8c1f0edaac096962.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:48:50Z" - latency: 56.246674ms message: 'load-balancer-api-external: tcp connection to a3904a6b916d941eabd9d7e63c223c68-8c1f0edaac096962.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:47:50Z" - latency: 9.291196ms message: 'load-balancer-api-external: resolved host name a3904a6b916d941eabd9d7e63c223c68-8c1f0edaac096962.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:47:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T18:45:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-179-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-179.us-west-2.compute.internal uid: 0bc97d9e-8430-4184-96fc-7e8a882299d8 resourceVersion: "107841" uid: 35ec83eb-7570-4a5f-98c7-98d297d0abe9 spec: sourcePod: network-check-source-6f78d59f99-mzf7t targetEndpoint: a3904a6b916d941eabd9d7e63c223c68-8c1f0edaac096962.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T18:51:51Z" message: 'load-balancer-api-internal: tcp connection to a3904a6b916d941eabd9d7e63c223c68-8c1f0edaac096962.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 56.426626ms message: 'load-balancer-api-internal: tcp connection to a3904a6b916d941eabd9d7e63c223c68-8c1f0edaac096962.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:51:50Z" - latency: 7.270712ms message: 'load-balancer-api-internal: resolved host name a3904a6b916d941eabd9d7e63c223c68-8c1f0edaac096962.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:51:50Z" - latency: 57.069803ms message: 'load-balancer-api-internal: tcp connection to a3904a6b916d941eabd9d7e63c223c68-8c1f0edaac096962.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:50:50Z" - latency: 6.782959ms message: 'load-balancer-api-internal: resolved host name a3904a6b916d941eabd9d7e63c223c68-8c1f0edaac096962.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:50:50Z" - latency: 56.059497ms message: 'load-balancer-api-internal: tcp connection to a3904a6b916d941eabd9d7e63c223c68-8c1f0edaac096962.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:49:50Z" - latency: 6.903514ms message: 'load-balancer-api-internal: resolved host name a3904a6b916d941eabd9d7e63c223c68-8c1f0edaac096962.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:49:50Z" - latency: 53.254328ms message: 'load-balancer-api-internal: tcp connection to a3904a6b916d941eabd9d7e63c223c68-8c1f0edaac096962.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:48:50Z" - latency: 6.971539ms message: 'load-balancer-api-internal: resolved host name a3904a6b916d941eabd9d7e63c223c68-8c1f0edaac096962.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:48:50Z" - latency: 56.242437ms message: 'load-balancer-api-internal: tcp connection to a3904a6b916d941eabd9d7e63c223c68-8c1f0edaac096962.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:47:50Z" - latency: 9.324936ms message: 'load-balancer-api-internal: resolved host name a3904a6b916d941eabd9d7e63c223c68-8c1f0edaac096962.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:47:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T18:45:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-179-to-network-check-target-ip-10-0-133-236 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-179.us-west-2.compute.internal uid: 0bc97d9e-8430-4184-96fc-7e8a882299d8 resourceVersion: "110474" uid: 33b13065-8c00-4d36-bbb9-1605f82aeaca spec: sourcePod: network-check-source-6f78d59f99-mzf7t targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T18:52:56Z" message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.597807ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:55:56Z" - latency: 693.795µs message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:54:56Z" - latency: 1.001435ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:53:56Z" - latency: 2.33496ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:52:56Z" - latency: 2.345694ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:51:56Z" - latency: 2.430458ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:50:56Z" - latency: 2.571045ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:49:56Z" - latency: 999.676µs message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:48:56Z" - latency: 2.589409ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:47:56Z" - latency: 2.57186ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:46:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T18:45:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-179-to-network-check-target-ip-10-0-137-192 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-179.us-west-2.compute.internal uid: 0bc97d9e-8430-4184-96fc-7e8a882299d8 resourceVersion: "110431" uid: 7c16584f-1907-42bc-85ce-3e6299d90a2a spec: sourcePod: network-check-source-6f78d59f99-mzf7t targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T18:52:50Z" message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.002365ms message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:55:50Z" - latency: 2.109358ms message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:54:50Z" - latency: 2.238522ms message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:53:50Z" - latency: 2.38119ms message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:52:50Z" - latency: 2.165042ms message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:51:50Z" - latency: 2.198994ms message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:50:50Z" - latency: 2.26911ms message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:49:50Z" - latency: 7.310139ms message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:48:50Z" - latency: 3.216365ms message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:47:50Z" - latency: 2.169114ms message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:46:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T18:45:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-179-to-network-check-target-ip-10-0-139-179 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-179.us-west-2.compute.internal uid: 0bc97d9e-8430-4184-96fc-7e8a882299d8 resourceVersion: "110430" uid: 5e366fd4-c096-4d8f-9d32-7cccd94a30f7 spec: sourcePod: network-check-source-6f78d59f99-mzf7t targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T18:52:50Z" message: 'network-check-target-ip-10-0-139-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 959.561µs message: 'network-check-target-ip-10-0-139-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:55:50Z" - latency: 956.595µs message: 'network-check-target-ip-10-0-139-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:54:50Z" - latency: 1.124873ms message: 'network-check-target-ip-10-0-139-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:53:50Z" - latency: 1.119711ms message: 'network-check-target-ip-10-0-139-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:52:50Z" - latency: 1.282327ms message: 'network-check-target-ip-10-0-139-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:51:50Z" - latency: 1.322758ms message: 'network-check-target-ip-10-0-139-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:50:50Z" - latency: 1.189769ms message: 'network-check-target-ip-10-0-139-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:49:50Z" - latency: 1.007462ms message: 'network-check-target-ip-10-0-139-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:48:50Z" - latency: 2.569454ms message: 'network-check-target-ip-10-0-139-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:47:50Z" - latency: 953.142µs message: 'network-check-target-ip-10-0-139-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:46:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T18:45:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-179-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-179.us-west-2.compute.internal uid: 0bc97d9e-8430-4184-96fc-7e8a882299d8 resourceVersion: "107839" uid: 1c1b1072-a9b7-441b-b322-d327281a8a58 spec: sourcePod: network-check-source-6f78d59f99-mzf7t targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T18:51:50Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 962.588µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:51:50Z" - latency: 1.885014ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T19:51:50Z" - latency: 1.062904ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:50:50Z" - latency: 1.848558ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T19:50:50Z" - latency: 1.081026ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:49:50Z" - latency: 1.946503ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T19:49:50Z" - latency: 2.343855ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:48:50Z" - latency: 2.001282ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T19:48:50Z" - latency: 1.426324ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:47:50Z" - latency: 2.929275ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T19:47:50Z" kind: List metadata: resourceVersion: ""