apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T20:09:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-249-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-249.ec2.internal uid: 292e5bf3-aa2c-4bfe-ba78-104d25db23d3 resourceVersion: "55672" uid: af911924-b4c8-4300-a681-25c265e4d561 spec: sourcePod: network-check-source-869dcfcdcd-vqt87 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T20:16:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.196744ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:44:57Z" - latency: 1.102048ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:43:57Z" - latency: 1.220961ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:42:57Z" - latency: 870.445µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:41:57Z" - latency: 1.01942ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:40:57Z" - latency: 1.430746ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:39:57Z" - latency: 1.140286ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:38:57Z" - latency: 940.566µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:37:57Z" - latency: 987.373µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:36:57Z" - latency: 1.03411ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:35:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T20:09:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-249-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-249.ec2.internal uid: 292e5bf3-aa2c-4bfe-ba78-104d25db23d3 resourceVersion: "56816" uid: f5bc9df5-04a0-47d0-8034-7e4b74954e96 spec: sourcePod: network-check-source-869dcfcdcd-vqt87 targetEndpoint: aad1b3a813b2b4dd79cd4cb2e9a35288-e7840672136983b1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T20:15:57Z" message: 'load-balancer-api-external: tcp connection to aad1b3a813b2b4dd79cd4cb2e9a35288-e7840672136983b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.54089ms message: 'load-balancer-api-external: tcp connection to aad1b3a813b2b4dd79cd4cb2e9a35288-e7840672136983b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:45:57Z" - latency: 9.11624ms message: 'load-balancer-api-external: resolved host name aad1b3a813b2b4dd79cd4cb2e9a35288-e7840672136983b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T20:45:57Z" - latency: 4.055564ms message: 'load-balancer-api-external: tcp connection to aad1b3a813b2b4dd79cd4cb2e9a35288-e7840672136983b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:44:57Z" - latency: 9.211617ms message: 'load-balancer-api-external: resolved host name aad1b3a813b2b4dd79cd4cb2e9a35288-e7840672136983b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T20:44:57Z" - latency: 6.109135ms message: 'load-balancer-api-external: tcp connection to aad1b3a813b2b4dd79cd4cb2e9a35288-e7840672136983b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:43:57Z" - latency: 6.321917ms message: 'load-balancer-api-external: resolved host name aad1b3a813b2b4dd79cd4cb2e9a35288-e7840672136983b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T20:43:57Z" - latency: 4.213073ms message: 'load-balancer-api-external: tcp connection to aad1b3a813b2b4dd79cd4cb2e9a35288-e7840672136983b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:42:57Z" - latency: 9.14914ms message: 'load-balancer-api-external: resolved host name aad1b3a813b2b4dd79cd4cb2e9a35288-e7840672136983b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T20:42:57Z" - latency: 4.864671ms message: 'load-balancer-api-external: tcp connection to aad1b3a813b2b4dd79cd4cb2e9a35288-e7840672136983b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:41:57Z" - latency: 8.095743ms message: 'load-balancer-api-external: resolved host name aad1b3a813b2b4dd79cd4cb2e9a35288-e7840672136983b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T20:41:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T20:09:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-249-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-249.ec2.internal uid: 292e5bf3-aa2c-4bfe-ba78-104d25db23d3 resourceVersion: "56815" uid: 5c521c0a-6c27-4f41-8248-8fd9c5d4aa4e spec: sourcePod: network-check-source-869dcfcdcd-vqt87 targetEndpoint: aad1b3a813b2b4dd79cd4cb2e9a35288-e7840672136983b1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T20:15:57Z" message: 'load-balancer-api-internal: tcp connection to aad1b3a813b2b4dd79cd4cb2e9a35288-e7840672136983b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.576137ms message: 'load-balancer-api-internal: tcp connection to aad1b3a813b2b4dd79cd4cb2e9a35288-e7840672136983b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:45:57Z" - latency: 9.041154ms message: 'load-balancer-api-internal: resolved host name aad1b3a813b2b4dd79cd4cb2e9a35288-e7840672136983b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T20:45:57Z" - latency: 4.212446ms message: 'load-balancer-api-internal: tcp connection to aad1b3a813b2b4dd79cd4cb2e9a35288-e7840672136983b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:44:57Z" - latency: 9.26007ms message: 'load-balancer-api-internal: resolved host name aad1b3a813b2b4dd79cd4cb2e9a35288-e7840672136983b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T20:44:57Z" - latency: 4.954385ms message: 'load-balancer-api-internal: tcp connection to aad1b3a813b2b4dd79cd4cb2e9a35288-e7840672136983b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:43:57Z" - latency: 6.439956ms message: 'load-balancer-api-internal: resolved host name aad1b3a813b2b4dd79cd4cb2e9a35288-e7840672136983b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T20:43:57Z" - latency: 4.20569ms message: 'load-balancer-api-internal: tcp connection to aad1b3a813b2b4dd79cd4cb2e9a35288-e7840672136983b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:42:57Z" - latency: 9.203161ms message: 'load-balancer-api-internal: resolved host name aad1b3a813b2b4dd79cd4cb2e9a35288-e7840672136983b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T20:42:57Z" - latency: 4.844644ms message: 'load-balancer-api-internal: tcp connection to aad1b3a813b2b4dd79cd4cb2e9a35288-e7840672136983b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:41:57Z" - latency: 8.226991ms message: 'load-balancer-api-internal: resolved host name aad1b3a813b2b4dd79cd4cb2e9a35288-e7840672136983b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T20:41:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T20:09:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-249-to-network-check-target-ip-10-0-139-14 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-249.ec2.internal uid: 292e5bf3-aa2c-4bfe-ba78-104d25db23d3 resourceVersion: "55671" uid: 587e293f-8c54-4682-93d7-9f6503ae6375 spec: sourcePod: network-check-source-869dcfcdcd-vqt87 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T20:16:57Z" message: 'network-check-target-ip-10-0-139-14: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.613263ms message: 'network-check-target-ip-10-0-139-14: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:44:57Z" - latency: 2.552327ms message: 'network-check-target-ip-10-0-139-14: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:43:57Z" - latency: 2.731875ms message: 'network-check-target-ip-10-0-139-14: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:42:57Z" - latency: 2.1604ms message: 'network-check-target-ip-10-0-139-14: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:41:57Z" - latency: 2.750344ms message: 'network-check-target-ip-10-0-139-14: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:40:57Z" - latency: 2.270682ms message: 'network-check-target-ip-10-0-139-14: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:39:57Z" - latency: 2.386041ms message: 'network-check-target-ip-10-0-139-14: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:38:57Z" - latency: 2.353831ms message: 'network-check-target-ip-10-0-139-14: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:37:57Z" - latency: 2.392329ms message: 'network-check-target-ip-10-0-139-14: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:36:57Z" - latency: 2.545306ms message: 'network-check-target-ip-10-0-139-14: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:35:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T20:09:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-249-to-network-check-target-ip-10-0-140-63 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-249.ec2.internal uid: 292e5bf3-aa2c-4bfe-ba78-104d25db23d3 resourceVersion: "55670" uid: dbbd6faa-ed7d-4e87-8cd2-6d22db53cfe2 spec: sourcePod: network-check-source-869dcfcdcd-vqt87 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T20:16:57Z" message: 'network-check-target-ip-10-0-140-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.036907ms message: 'network-check-target-ip-10-0-140-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:44:57Z" - latency: 2.041515ms message: 'network-check-target-ip-10-0-140-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:43:57Z" - latency: 2.167635ms message: 'network-check-target-ip-10-0-140-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:42:57Z" - latency: 1.749442ms message: 'network-check-target-ip-10-0-140-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:41:57Z" - latency: 2.284361ms message: 'network-check-target-ip-10-0-140-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:40:57Z" - latency: 2.500178ms message: 'network-check-target-ip-10-0-140-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:39:57Z" - latency: 1.896058ms message: 'network-check-target-ip-10-0-140-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:38:57Z" - latency: 2.051436ms message: 'network-check-target-ip-10-0-140-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:37:57Z" - latency: 1.903516ms message: 'network-check-target-ip-10-0-140-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:36:57Z" - latency: 1.895599ms message: 'network-check-target-ip-10-0-140-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:35:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T20:09:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-249-to-network-check-target-ip-10-0-142-249 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-249.ec2.internal uid: 292e5bf3-aa2c-4bfe-ba78-104d25db23d3 resourceVersion: "55669" uid: 3f323fb7-977f-43b4-a2c0-7b052e983abf spec: sourcePod: network-check-source-869dcfcdcd-vqt87 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T20:16:57Z" message: 'network-check-target-ip-10-0-142-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 822.241µs message: 'network-check-target-ip-10-0-142-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:44:57Z" - latency: 901.228µs message: 'network-check-target-ip-10-0-142-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:43:57Z" - latency: 863.86µs message: 'network-check-target-ip-10-0-142-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:42:57Z" - latency: 820.51µs message: 'network-check-target-ip-10-0-142-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:41:57Z" - latency: 1.527623ms message: 'network-check-target-ip-10-0-142-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:40:57Z" - latency: 816.062µs message: 'network-check-target-ip-10-0-142-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:39:57Z" - latency: 1.02678ms message: 'network-check-target-ip-10-0-142-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:38:57Z" - latency: 981.932µs message: 'network-check-target-ip-10-0-142-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:37:57Z" - latency: 931.017µs message: 'network-check-target-ip-10-0-142-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:36:57Z" - latency: 1.120942ms message: 'network-check-target-ip-10-0-142-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:35:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T20:09:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-249-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-249.ec2.internal uid: 292e5bf3-aa2c-4bfe-ba78-104d25db23d3 resourceVersion: "56814" uid: e567f2ce-237e-4284-9c4d-e8b0acd234a6 spec: sourcePod: network-check-source-869dcfcdcd-vqt87 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T20:15:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.088345ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:45:57Z" - latency: 2.263534ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T20:45:57Z" - latency: 1.215937ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:44:57Z" - latency: 1.991751ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T20:44:57Z" - latency: 952.367µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:43:57Z" - latency: 1.687984ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T20:43:57Z" - latency: 1.201266ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:42:57Z" - latency: 1.722646ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T20:42:57Z" - latency: 1.341127ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T20:41:57Z" - latency: 1.656674ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T20:41:57Z" kind: List metadata: resourceVersion: ""