apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-03T20:43:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-199-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-199.ec2.internal uid: 47e6ab61-ebf7-48bf-baac-ee8fe7662354 resourceVersion: "56094" uid: c9ccf021-0c43-4eda-8f91-252f30dda133 spec: sourcePod: network-check-source-989f8b8dc-w8d88 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-03T20:50:45Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 879.708µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:18:45Z" - latency: 1.43349ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:17:45Z" - latency: 1.23631ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:16:45Z" - latency: 765.81µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:15:45Z" - latency: 807.547µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:14:45Z" - latency: 1.077744ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:13:45Z" - latency: 1.086437ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:12:45Z" - latency: 1.069238ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:11:45Z" - latency: 1.182731ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:10:45Z" - latency: 991.724µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:09:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-03T20:43:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-199-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-199.ec2.internal uid: 47e6ab61-ebf7-48bf-baac-ee8fe7662354 resourceVersion: "51276" uid: a5c8d03e-8f8a-410d-9329-4a943450ff4a spec: sourcePod: network-check-source-989f8b8dc-w8d88 targetEndpoint: abe8000b7f49f41fabf3f96dbf53ae7b-7e98f44b5bddae44.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-03T20:49:45Z" message: 'load-balancer-api-external: tcp connection to abe8000b7f49f41fabf3f96dbf53ae7b-7e98f44b5bddae44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.370982ms message: 'load-balancer-api-external: tcp connection to abe8000b7f49f41fabf3f96dbf53ae7b-7e98f44b5bddae44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:13:45Z" - latency: 8.701026ms message: 'load-balancer-api-external: resolved host name abe8000b7f49f41fabf3f96dbf53ae7b-7e98f44b5bddae44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T21:13:45Z" - latency: 3.05851ms message: 'load-balancer-api-external: tcp connection to abe8000b7f49f41fabf3f96dbf53ae7b-7e98f44b5bddae44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:12:45Z" - latency: 7.833889ms message: 'load-balancer-api-external: resolved host name abe8000b7f49f41fabf3f96dbf53ae7b-7e98f44b5bddae44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T21:12:45Z" - latency: 4.532369ms message: 'load-balancer-api-external: tcp connection to abe8000b7f49f41fabf3f96dbf53ae7b-7e98f44b5bddae44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:11:45Z" - latency: 7.573338ms message: 'load-balancer-api-external: resolved host name abe8000b7f49f41fabf3f96dbf53ae7b-7e98f44b5bddae44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T21:11:45Z" - latency: 5.257649ms message: 'load-balancer-api-external: tcp connection to abe8000b7f49f41fabf3f96dbf53ae7b-7e98f44b5bddae44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:10:45Z" - latency: 6.584124ms message: 'load-balancer-api-external: resolved host name abe8000b7f49f41fabf3f96dbf53ae7b-7e98f44b5bddae44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T21:10:45Z" - latency: 3.535953ms message: 'load-balancer-api-external: tcp connection to abe8000b7f49f41fabf3f96dbf53ae7b-7e98f44b5bddae44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:09:45Z" - latency: 8.126496ms message: 'load-balancer-api-external: resolved host name abe8000b7f49f41fabf3f96dbf53ae7b-7e98f44b5bddae44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T21:09:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-03T20:43:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-199-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-199.ec2.internal uid: 47e6ab61-ebf7-48bf-baac-ee8fe7662354 resourceVersion: "51275" uid: 3d2b2a63-eba9-4b96-929a-2355155a6239 spec: sourcePod: network-check-source-989f8b8dc-w8d88 targetEndpoint: abe8000b7f49f41fabf3f96dbf53ae7b-7e98f44b5bddae44.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-03T20:49:45Z" message: 'load-balancer-api-internal: tcp connection to abe8000b7f49f41fabf3f96dbf53ae7b-7e98f44b5bddae44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.461194ms message: 'load-balancer-api-internal: tcp connection to abe8000b7f49f41fabf3f96dbf53ae7b-7e98f44b5bddae44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:13:45Z" - latency: 8.678033ms message: 'load-balancer-api-internal: resolved host name abe8000b7f49f41fabf3f96dbf53ae7b-7e98f44b5bddae44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T21:13:45Z" - latency: 3.001406ms message: 'load-balancer-api-internal: tcp connection to abe8000b7f49f41fabf3f96dbf53ae7b-7e98f44b5bddae44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:12:45Z" - latency: 7.71379ms message: 'load-balancer-api-internal: resolved host name abe8000b7f49f41fabf3f96dbf53ae7b-7e98f44b5bddae44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T21:12:45Z" - latency: 4.585695ms message: 'load-balancer-api-internal: tcp connection to abe8000b7f49f41fabf3f96dbf53ae7b-7e98f44b5bddae44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:11:45Z" - latency: 7.504897ms message: 'load-balancer-api-internal: resolved host name abe8000b7f49f41fabf3f96dbf53ae7b-7e98f44b5bddae44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T21:11:45Z" - latency: 4.985401ms message: 'load-balancer-api-internal: tcp connection to abe8000b7f49f41fabf3f96dbf53ae7b-7e98f44b5bddae44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:10:45Z" - latency: 6.424394ms message: 'load-balancer-api-internal: resolved host name abe8000b7f49f41fabf3f96dbf53ae7b-7e98f44b5bddae44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T21:10:45Z" - latency: 4.178986ms message: 'load-balancer-api-internal: tcp connection to abe8000b7f49f41fabf3f96dbf53ae7b-7e98f44b5bddae44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:09:45Z" - latency: 8.072405ms message: 'load-balancer-api-internal: resolved host name abe8000b7f49f41fabf3f96dbf53ae7b-7e98f44b5bddae44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T21:09:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-03T20:43:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-199-to-network-check-target-ip-10-0-128-87 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-199.ec2.internal uid: 47e6ab61-ebf7-48bf-baac-ee8fe7662354 resourceVersion: "56092" uid: b2d5168b-f361-4a09-a507-b9a589b74761 spec: sourcePod: network-check-source-989f8b8dc-w8d88 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-03T20:50:45Z" message: 'network-check-target-ip-10-0-128-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.0005ms message: 'network-check-target-ip-10-0-128-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:18:45Z" - latency: 1.878131ms message: 'network-check-target-ip-10-0-128-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:17:45Z" - latency: 1.748001ms message: 'network-check-target-ip-10-0-128-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:16:45Z" - latency: 1.613547ms message: 'network-check-target-ip-10-0-128-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:15:45Z" - latency: 1.972637ms message: 'network-check-target-ip-10-0-128-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:14:45Z" - latency: 2.082913ms message: 'network-check-target-ip-10-0-128-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:13:45Z" - latency: 1.796989ms message: 'network-check-target-ip-10-0-128-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:12:45Z" - latency: 2.164624ms message: 'network-check-target-ip-10-0-128-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:11:45Z" - latency: 2.033309ms message: 'network-check-target-ip-10-0-128-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:10:45Z" - latency: 2.413589ms message: 'network-check-target-ip-10-0-128-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:09:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-03T20:43:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-199-to-network-check-target-ip-10-0-129-236 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-199.ec2.internal uid: 47e6ab61-ebf7-48bf-baac-ee8fe7662354 resourceVersion: "56093" uid: 28fd6064-65b9-4357-81b8-66043e321bd3 spec: sourcePod: network-check-source-989f8b8dc-w8d88 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-03T20:50:45Z" message: 'network-check-target-ip-10-0-129-236: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.245979ms message: 'network-check-target-ip-10-0-129-236: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:18:45Z" - latency: 2.370336ms message: 'network-check-target-ip-10-0-129-236: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:17:45Z" - latency: 2.179334ms message: 'network-check-target-ip-10-0-129-236: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:16:45Z" - latency: 1.969791ms message: 'network-check-target-ip-10-0-129-236: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:15:45Z" - latency: 2.218823ms message: 'network-check-target-ip-10-0-129-236: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:14:45Z" - latency: 2.132105ms message: 'network-check-target-ip-10-0-129-236: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:13:45Z" - latency: 2.551892ms message: 'network-check-target-ip-10-0-129-236: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:12:45Z" - latency: 2.239331ms message: 'network-check-target-ip-10-0-129-236: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:11:45Z" - latency: 2.455492ms message: 'network-check-target-ip-10-0-129-236: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:10:45Z" - latency: 2.176563ms message: 'network-check-target-ip-10-0-129-236: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:09:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-03T20:43:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-199-to-network-check-target-ip-10-0-131-199 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-199.ec2.internal uid: 47e6ab61-ebf7-48bf-baac-ee8fe7662354 resourceVersion: "56091" uid: 3c4f23d8-838d-4e28-8551-63c1a2903b87 spec: sourcePod: network-check-source-989f8b8dc-w8d88 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-03T20:50:45Z" message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.110871ms message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:18:45Z" - latency: 897.919µs message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:17:45Z" - latency: 823.256µs message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:16:45Z" - latency: 674.67µs message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:15:45Z" - latency: 727.828µs message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:14:45Z" - latency: 791.306µs message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:13:45Z" - latency: 930.274µs message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:12:45Z" - latency: 1.387687ms message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:11:45Z" - latency: 1.219361ms message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:10:45Z" - latency: 869.547µs message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:09:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-03T20:43:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-199-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-199.ec2.internal uid: 47e6ab61-ebf7-48bf-baac-ee8fe7662354 resourceVersion: "51274" uid: e085c8d1-a26a-4396-95f7-16b0d1705720 spec: sourcePod: network-check-source-989f8b8dc-w8d88 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-03T20:49:45Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 749.712µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:13:45Z" - latency: 1.702747ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-03T21:13:45Z" - latency: 1.024204ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:12:45Z" - latency: 1.976588ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-03T21:12:45Z" - latency: 863.927µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:11:45Z" - latency: 2.182052ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-03T21:11:45Z" - latency: 789.839µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:10:45Z" - latency: 1.497221ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-03T21:10:45Z" - latency: 1.169113ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-03T21:09:45Z" - latency: 1.707603ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-03T21:09:45Z" kind: List metadata: resourceVersion: ""