apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:59:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-123-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-123.ec2.internal uid: 02a70f46-1819-488e-b178-de96c4d1a1b7 resourceVersion: "53879" uid: 75dbcbd6-ffc4-4b28-a172-2b63b9e88e99 spec: sourcePod: network-check-source-989f8b8dc-jlv7l targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T00:06:12Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.134276ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:34:12Z" - latency: 878.165µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:33:12Z" - latency: 1.127117ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:32:12Z" - latency: 1.224959ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:31:12Z" - latency: 1.442695ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:30:12Z" - latency: 931.438µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:29:12Z" - latency: 787.296µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:28:12Z" - latency: 1.82933ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:27:12Z" - latency: 1.230861ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:12Z" - latency: 883.34µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:59:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-123-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-123.ec2.internal uid: 02a70f46-1819-488e-b178-de96c4d1a1b7 resourceVersion: "54893" uid: 3e21b9f0-4197-452a-a5f6-2e566016b546 spec: sourcePod: network-check-source-989f8b8dc-jlv7l targetEndpoint: aac38ff398abd43f9ac6fc2b7c4be0d8-a3735ded058ca5ed.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T00:05:12Z" message: 'load-balancer-api-external: tcp connection to aac38ff398abd43f9ac6fc2b7c4be0d8-a3735ded058ca5ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.671743ms message: 'load-balancer-api-external: tcp connection to aac38ff398abd43f9ac6fc2b7c4be0d8-a3735ded058ca5ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:35:12Z" - latency: 7.407951ms message: 'load-balancer-api-external: resolved host name aac38ff398abd43f9ac6fc2b7c4be0d8-a3735ded058ca5ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:35:12Z" - latency: 5.373313ms message: 'load-balancer-api-external: tcp connection to aac38ff398abd43f9ac6fc2b7c4be0d8-a3735ded058ca5ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:34:12Z" - latency: 7.264213ms message: 'load-balancer-api-external: resolved host name aac38ff398abd43f9ac6fc2b7c4be0d8-a3735ded058ca5ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:34:12Z" - latency: 3.955723ms message: 'load-balancer-api-external: tcp connection to aac38ff398abd43f9ac6fc2b7c4be0d8-a3735ded058ca5ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:33:12Z" - latency: 9.078663ms message: 'load-balancer-api-external: resolved host name aac38ff398abd43f9ac6fc2b7c4be0d8-a3735ded058ca5ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:33:12Z" - latency: 4.99665ms message: 'load-balancer-api-external: tcp connection to aac38ff398abd43f9ac6fc2b7c4be0d8-a3735ded058ca5ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:32:12Z" - latency: 6.650598ms message: 'load-balancer-api-external: resolved host name aac38ff398abd43f9ac6fc2b7c4be0d8-a3735ded058ca5ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:32:12Z" - latency: 4.388884ms message: 'load-balancer-api-external: tcp connection to aac38ff398abd43f9ac6fc2b7c4be0d8-a3735ded058ca5ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:31:12Z" - latency: 9.697523ms message: 'load-balancer-api-external: resolved host name aac38ff398abd43f9ac6fc2b7c4be0d8-a3735ded058ca5ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:31:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:59:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-123-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-123.ec2.internal uid: 02a70f46-1819-488e-b178-de96c4d1a1b7 resourceVersion: "54892" uid: b842ba3b-1d70-46be-8d66-f980c5ba046e spec: sourcePod: network-check-source-989f8b8dc-jlv7l targetEndpoint: aac38ff398abd43f9ac6fc2b7c4be0d8-a3735ded058ca5ed.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T00:05:12Z" message: 'load-balancer-api-internal: tcp connection to aac38ff398abd43f9ac6fc2b7c4be0d8-a3735ded058ca5ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.628568ms message: 'load-balancer-api-internal: tcp connection to aac38ff398abd43f9ac6fc2b7c4be0d8-a3735ded058ca5ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:35:12Z" - latency: 7.274129ms message: 'load-balancer-api-internal: resolved host name aac38ff398abd43f9ac6fc2b7c4be0d8-a3735ded058ca5ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:35:12Z" - latency: 5.398791ms message: 'load-balancer-api-internal: tcp connection to aac38ff398abd43f9ac6fc2b7c4be0d8-a3735ded058ca5ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:34:12Z" - latency: 7.234545ms message: 'load-balancer-api-internal: resolved host name aac38ff398abd43f9ac6fc2b7c4be0d8-a3735ded058ca5ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:34:12Z" - latency: 3.921917ms message: 'load-balancer-api-internal: tcp connection to aac38ff398abd43f9ac6fc2b7c4be0d8-a3735ded058ca5ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:33:12Z" - latency: 9.060209ms message: 'load-balancer-api-internal: resolved host name aac38ff398abd43f9ac6fc2b7c4be0d8-a3735ded058ca5ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:33:12Z" - latency: 5.006967ms message: 'load-balancer-api-internal: tcp connection to aac38ff398abd43f9ac6fc2b7c4be0d8-a3735ded058ca5ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:32:12Z" - latency: 6.565696ms message: 'load-balancer-api-internal: resolved host name aac38ff398abd43f9ac6fc2b7c4be0d8-a3735ded058ca5ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:32:12Z" - latency: 4.395607ms message: 'load-balancer-api-internal: tcp connection to aac38ff398abd43f9ac6fc2b7c4be0d8-a3735ded058ca5ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:31:12Z" - latency: 9.673343ms message: 'load-balancer-api-internal: resolved host name aac38ff398abd43f9ac6fc2b7c4be0d8-a3735ded058ca5ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:31:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:59:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-123-to-network-check-target-ip-10-0-129-125 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-123.ec2.internal uid: 02a70f46-1819-488e-b178-de96c4d1a1b7 resourceVersion: "53878" uid: c62fa488-3c97-4801-881b-b69b03471bd0 spec: sourcePod: network-check-source-989f8b8dc-jlv7l targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T00:06:12Z" message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.478386ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:34:12Z" - latency: 2.001736ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:33:12Z" - latency: 2.232288ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:32:12Z" - latency: 2.198573ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:31:12Z" - latency: 2.232765ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:30:12Z" - latency: 2.18003ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:29:12Z" - latency: 2.138239ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:28:12Z" - latency: 2.181871ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:27:12Z" - latency: 2.253905ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:12Z" - latency: 2.039735ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:59:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-123-to-network-check-target-ip-10-0-129-135 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-123.ec2.internal uid: 02a70f46-1819-488e-b178-de96c4d1a1b7 resourceVersion: "53877" uid: ab04186f-b38d-473a-98e6-8588ccecf271 spec: sourcePod: network-check-source-989f8b8dc-jlv7l targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T00:06:12Z" message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.939974ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:34:12Z" - latency: 1.88375ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:33:12Z" - latency: 2.361266ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:32:12Z" - latency: 2.324138ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:31:12Z" - latency: 2.068964ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:30:12Z" - latency: 2.210148ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:29:12Z" - latency: 2.056437ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:28:12Z" - latency: 2.717661ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:27:12Z" - latency: 2.358001ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:12Z" - latency: 2.007428ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:59:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-123-to-network-check-target-ip-10-0-141-123 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-123.ec2.internal uid: 02a70f46-1819-488e-b178-de96c4d1a1b7 resourceVersion: "53876" uid: 6afa546d-0c79-4be7-8e94-358324d94f2d spec: sourcePod: network-check-source-989f8b8dc-jlv7l targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T00:06:12Z" message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.237403ms message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:34:12Z" - latency: 941.654µs message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:33:12Z" - latency: 859.771µs message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:32:12Z" - latency: 866.148µs message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:31:12Z" - latency: 1.022756ms message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:30:12Z" - latency: 1.051147ms message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:29:12Z" - latency: 769.67µs message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:28:12Z" - latency: 852.594µs message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:27:12Z" - latency: 848.123µs message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:12Z" - latency: 1.114832ms message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:59:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-123-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-123.ec2.internal uid: 02a70f46-1819-488e-b178-de96c4d1a1b7 resourceVersion: "54891" uid: 370d5b8e-4b80-4ed7-8b1c-092770d2092d spec: sourcePod: network-check-source-989f8b8dc-jlv7l targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T00:05:12Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 887.987µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:35:12Z" - latency: 1.687501ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:35:12Z" - latency: 998.256µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:34:12Z" - latency: 1.609188ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:34:12Z" - latency: 909.531µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:33:12Z" - latency: 1.796617ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:33:12Z" - latency: 1.142608ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:32:12Z" - latency: 1.932456ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:32:12Z" - latency: 929.69µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:31:12Z" - latency: 1.488593ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:31:12Z" kind: List metadata: resourceVersion: ""