apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T16:46:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-239-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-239.ec2.internal uid: 3d6a509d-6471-4b11-aba2-b20b99c56998 resourceVersion: "49085" uid: e87132d4-6a2e-4e22-a775-8340aeebe34a spec: sourcePod: network-check-source-989f8b8dc-x5z8s targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T16:53: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.08009ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:21:51Z" - latency: 900.752µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:20:51Z" - latency: 929.773µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:19:51Z" - latency: 944.634µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:18:51Z" - latency: 814.473µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:17:51Z" - latency: 1.427984ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:16:51Z" - latency: 929.863µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:15:51Z" - latency: 1.069197ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:14:51Z" - latency: 1.069699ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:13:51Z" - latency: 1.066645ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:12:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T16:46:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-239-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-239.ec2.internal uid: 3d6a509d-6471-4b11-aba2-b20b99c56998 resourceVersion: "49877" uid: c1906e97-7f07-46b3-9b12-84696a3116b8 spec: sourcePod: network-check-source-989f8b8dc-x5z8s targetEndpoint: a63e3a650d7d6496d8a9d7a34922820d-ee5eddcae3b91cb3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T16:52:51Z" message: 'load-balancer-api-external: tcp connection to a63e3a650d7d6496d8a9d7a34922820d-ee5eddcae3b91cb3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.499059ms message: 'load-balancer-api-external: tcp connection to a63e3a650d7d6496d8a9d7a34922820d-ee5eddcae3b91cb3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:22:51Z" - latency: 6.660183ms message: 'load-balancer-api-external: resolved host name a63e3a650d7d6496d8a9d7a34922820d-ee5eddcae3b91cb3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T17:22:51Z" - latency: 5.962554ms message: 'load-balancer-api-external: tcp connection to a63e3a650d7d6496d8a9d7a34922820d-ee5eddcae3b91cb3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:21:51Z" - latency: 7.332984ms message: 'load-balancer-api-external: resolved host name a63e3a650d7d6496d8a9d7a34922820d-ee5eddcae3b91cb3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T17:21:51Z" - latency: 4.082636ms message: 'load-balancer-api-external: tcp connection to a63e3a650d7d6496d8a9d7a34922820d-ee5eddcae3b91cb3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:20:51Z" - latency: 7.166613ms message: 'load-balancer-api-external: resolved host name a63e3a650d7d6496d8a9d7a34922820d-ee5eddcae3b91cb3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T17:20:51Z" - latency: 5.418442ms message: 'load-balancer-api-external: tcp connection to a63e3a650d7d6496d8a9d7a34922820d-ee5eddcae3b91cb3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:19:51Z" - latency: 6.702502ms message: 'load-balancer-api-external: resolved host name a63e3a650d7d6496d8a9d7a34922820d-ee5eddcae3b91cb3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T17:19:51Z" - latency: 4.616483ms message: 'load-balancer-api-external: tcp connection to a63e3a650d7d6496d8a9d7a34922820d-ee5eddcae3b91cb3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:18:51Z" - latency: 5.533999ms message: 'load-balancer-api-external: resolved host name a63e3a650d7d6496d8a9d7a34922820d-ee5eddcae3b91cb3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T17:18:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T16:46:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-239-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-239.ec2.internal uid: 3d6a509d-6471-4b11-aba2-b20b99c56998 resourceVersion: "49878" uid: b8426f8b-6e55-427d-9338-7cec091c2039 spec: sourcePod: network-check-source-989f8b8dc-x5z8s targetEndpoint: a63e3a650d7d6496d8a9d7a34922820d-ee5eddcae3b91cb3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T16:52:51Z" message: 'load-balancer-api-internal: tcp connection to a63e3a650d7d6496d8a9d7a34922820d-ee5eddcae3b91cb3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.750417ms message: 'load-balancer-api-internal: tcp connection to a63e3a650d7d6496d8a9d7a34922820d-ee5eddcae3b91cb3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:22:51Z" - latency: 6.61678ms message: 'load-balancer-api-internal: resolved host name a63e3a650d7d6496d8a9d7a34922820d-ee5eddcae3b91cb3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T17:22:51Z" - latency: 5.955955ms message: 'load-balancer-api-internal: tcp connection to a63e3a650d7d6496d8a9d7a34922820d-ee5eddcae3b91cb3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:21:51Z" - latency: 7.425774ms message: 'load-balancer-api-internal: resolved host name a63e3a650d7d6496d8a9d7a34922820d-ee5eddcae3b91cb3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T17:21:51Z" - latency: 5.431317ms message: 'load-balancer-api-internal: tcp connection to a63e3a650d7d6496d8a9d7a34922820d-ee5eddcae3b91cb3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:20:51Z" - latency: 7.244915ms message: 'load-balancer-api-internal: resolved host name a63e3a650d7d6496d8a9d7a34922820d-ee5eddcae3b91cb3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T17:20:51Z" - latency: 4.739551ms message: 'load-balancer-api-internal: tcp connection to a63e3a650d7d6496d8a9d7a34922820d-ee5eddcae3b91cb3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:19:51Z" - latency: 6.81363ms message: 'load-balancer-api-internal: resolved host name a63e3a650d7d6496d8a9d7a34922820d-ee5eddcae3b91cb3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T17:19:51Z" - latency: 4.5048ms message: 'load-balancer-api-internal: tcp connection to a63e3a650d7d6496d8a9d7a34922820d-ee5eddcae3b91cb3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:18:51Z" - latency: 5.484065ms message: 'load-balancer-api-internal: resolved host name a63e3a650d7d6496d8a9d7a34922820d-ee5eddcae3b91cb3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T17:18:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T16:46:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-239-to-network-check-target-ip-10-0-130-239 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-239.ec2.internal uid: 3d6a509d-6471-4b11-aba2-b20b99c56998 resourceVersion: "49084" uid: fea1518c-1b17-46b5-a984-db70ffb48f55 spec: sourcePod: network-check-source-989f8b8dc-x5z8s targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T16:53:51Z" message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.82734ms message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:21:51Z" - latency: 722.167µs message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:20:51Z" - latency: 1.708723ms message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:19:51Z" - latency: 988.236µs message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:18:51Z" - latency: 913.867µs message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:17:51Z" - latency: 789.125µs message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:16:51Z" - latency: 970.822µs message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:15:51Z" - latency: 879.767µs message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:14:51Z" - latency: 897.42µs message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:13:51Z" - latency: 1.496373ms message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:12:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T16:46:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-239-to-network-check-target-ip-10-0-131-71 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-239.ec2.internal uid: 3d6a509d-6471-4b11-aba2-b20b99c56998 resourceVersion: "49082" uid: d95c4be0-3900-4d71-990b-bd7a1af4338d spec: sourcePod: network-check-source-989f8b8dc-x5z8s targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T16:53:51Z" message: 'network-check-target-ip-10-0-131-71: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.926786ms message: 'network-check-target-ip-10-0-131-71: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:21:51Z" - latency: 2.011948ms message: 'network-check-target-ip-10-0-131-71: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:20:51Z" - latency: 2.294905ms message: 'network-check-target-ip-10-0-131-71: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:19:51Z" - latency: 2.181547ms message: 'network-check-target-ip-10-0-131-71: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:18:51Z" - latency: 2.544924ms message: 'network-check-target-ip-10-0-131-71: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:17:51Z" - latency: 2.019351ms message: 'network-check-target-ip-10-0-131-71: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:16:51Z" - latency: 2.290245ms message: 'network-check-target-ip-10-0-131-71: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:15:51Z" - latency: 2.169415ms message: 'network-check-target-ip-10-0-131-71: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:14:51Z" - latency: 2.034093ms message: 'network-check-target-ip-10-0-131-71: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:13:51Z" - latency: 2.775709ms message: 'network-check-target-ip-10-0-131-71: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:12:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T16:46:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-239-to-network-check-target-ip-10-0-135-40 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-239.ec2.internal uid: 3d6a509d-6471-4b11-aba2-b20b99c56998 resourceVersion: "49083" uid: 4d911fe7-c6f1-4c3d-9612-e0b87772739e spec: sourcePod: network-check-source-989f8b8dc-x5z8s targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-06T16:53:51Z" message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.440203ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:21:51Z" - latency: 2.048478ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:20:51Z" - latency: 2.753924ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:19:51Z" - latency: 2.242843ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:18:51Z" - latency: 2.058743ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:17:51Z" - latency: 2.241799ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:16:51Z" - latency: 2.408639ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:15:51Z" - latency: 2.349338ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:14:51Z" - latency: 2.438599ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:13:51Z" - latency: 3.242457ms message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:12:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T16:46:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-239-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-239.ec2.internal uid: 3d6a509d-6471-4b11-aba2-b20b99c56998 resourceVersion: "49876" uid: 1688d5d4-f8f9-4a1f-b7fa-5fc7ab6ff1cd spec: sourcePod: network-check-source-989f8b8dc-x5z8s targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T16:52:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.212464ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:22:51Z" - latency: 1.717138ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T17:22:51Z" - latency: 1.226149ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:21:51Z" - latency: 1.96072ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T17:21:51Z" - latency: 916.828µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:20:51Z" - latency: 1.771635ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T17:20:51Z" - latency: 987.611µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:19:51Z" - latency: 1.694354ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T17:19:51Z" - latency: 726.016µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T17:18:51Z" - latency: 1.710513ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T17:18:51Z" kind: List metadata: resourceVersion: ""