apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T14:45:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-116-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-116.ec2.internal uid: 6cbfd782-55e7-463a-a3f7-7325998cafc5 resourceVersion: "45669" uid: a1623e1d-d66c-4e42-8cce-19ad412e864f spec: sourcePod: network-check-source-6947749cfc-w62qp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-14T14:52:20Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 974.607µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:13:20Z" - latency: 1.006327ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:12:20Z" - latency: 1.001013ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:11:20Z" - latency: 852.882µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:10:20Z" - latency: 997.641µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:09:20Z" - latency: 1.186498ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:08:20Z" - latency: 1.019785ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:07:20Z" - latency: 926.617µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:06:20Z" - latency: 935.173µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:05:20Z" - latency: 933.42µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:04:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T14:45:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-116-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-116.ec2.internal uid: 6cbfd782-55e7-463a-a3f7-7325998cafc5 resourceVersion: "47820" uid: 419c81ea-0cec-4121-8322-aa0482764f34 spec: sourcePod: network-check-source-6947749cfc-w62qp targetEndpoint: af9f2a49ce06b4cfca6f5b294f908a3f-7683f53c76753a83.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-14T14:51:20Z" message: 'load-balancer-api-external: tcp connection to af9f2a49ce06b4cfca6f5b294f908a3f-7683f53c76753a83.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.207081ms message: 'load-balancer-api-external: tcp connection to af9f2a49ce06b4cfca6f5b294f908a3f-7683f53c76753a83.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:15:20Z" - latency: 8.750737ms message: 'load-balancer-api-external: resolved host name af9f2a49ce06b4cfca6f5b294f908a3f-7683f53c76753a83.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:15:20Z" - latency: 3.359369ms message: 'load-balancer-api-external: tcp connection to af9f2a49ce06b4cfca6f5b294f908a3f-7683f53c76753a83.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:14:20Z" - latency: 8.251807ms message: 'load-balancer-api-external: resolved host name af9f2a49ce06b4cfca6f5b294f908a3f-7683f53c76753a83.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:14:20Z" - latency: 7.229786ms message: 'load-balancer-api-external: tcp connection to af9f2a49ce06b4cfca6f5b294f908a3f-7683f53c76753a83.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:13:20Z" - latency: 9.324566ms message: 'load-balancer-api-external: resolved host name af9f2a49ce06b4cfca6f5b294f908a3f-7683f53c76753a83.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:13:20Z" - latency: 3.658992ms message: 'load-balancer-api-external: tcp connection to af9f2a49ce06b4cfca6f5b294f908a3f-7683f53c76753a83.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:12:20Z" - latency: 7.202648ms message: 'load-balancer-api-external: resolved host name af9f2a49ce06b4cfca6f5b294f908a3f-7683f53c76753a83.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:12:20Z" - latency: 3.451706ms message: 'load-balancer-api-external: tcp connection to af9f2a49ce06b4cfca6f5b294f908a3f-7683f53c76753a83.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:11:20Z" - latency: 8.316046ms message: 'load-balancer-api-external: resolved host name af9f2a49ce06b4cfca6f5b294f908a3f-7683f53c76753a83.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:11:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T14:45:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-116-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-116.ec2.internal uid: 6cbfd782-55e7-463a-a3f7-7325998cafc5 resourceVersion: "47819" uid: 18ef1d9a-f8ba-4ead-9ea4-8ffe2ad780c9 spec: sourcePod: network-check-source-6947749cfc-w62qp targetEndpoint: af9f2a49ce06b4cfca6f5b294f908a3f-7683f53c76753a83.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-14T14:51:20Z" message: 'load-balancer-api-internal: tcp connection to af9f2a49ce06b4cfca6f5b294f908a3f-7683f53c76753a83.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.238031ms message: 'load-balancer-api-internal: tcp connection to af9f2a49ce06b4cfca6f5b294f908a3f-7683f53c76753a83.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:15:20Z" - latency: 8.72464ms message: 'load-balancer-api-internal: resolved host name af9f2a49ce06b4cfca6f5b294f908a3f-7683f53c76753a83.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:15:20Z" - latency: 4.73598ms message: 'load-balancer-api-internal: tcp connection to af9f2a49ce06b4cfca6f5b294f908a3f-7683f53c76753a83.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:14:20Z" - latency: 8.156737ms message: 'load-balancer-api-internal: resolved host name af9f2a49ce06b4cfca6f5b294f908a3f-7683f53c76753a83.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:14:20Z" - latency: 5.702692ms message: 'load-balancer-api-internal: tcp connection to af9f2a49ce06b4cfca6f5b294f908a3f-7683f53c76753a83.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:13:20Z" - latency: 9.305316ms message: 'load-balancer-api-internal: resolved host name af9f2a49ce06b4cfca6f5b294f908a3f-7683f53c76753a83.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:13:20Z" - latency: 3.025517ms message: 'load-balancer-api-internal: tcp connection to af9f2a49ce06b4cfca6f5b294f908a3f-7683f53c76753a83.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:12:20Z" - latency: 7.253156ms message: 'load-balancer-api-internal: resolved host name af9f2a49ce06b4cfca6f5b294f908a3f-7683f53c76753a83.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:12:20Z" - latency: 3.349296ms message: 'load-balancer-api-internal: tcp connection to af9f2a49ce06b4cfca6f5b294f908a3f-7683f53c76753a83.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:11:20Z" - latency: 8.480011ms message: 'load-balancer-api-internal: resolved host name af9f2a49ce06b4cfca6f5b294f908a3f-7683f53c76753a83.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:11:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T14:45:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-116-to-network-check-target-ip-10-0-129-116 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-116.ec2.internal uid: 6cbfd782-55e7-463a-a3f7-7325998cafc5 resourceVersion: "45666" uid: b87adf33-fecc-4774-ba4e-f2d51225d73b spec: sourcePod: network-check-source-6947749cfc-w62qp targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-14T14:52:20Z" message: 'network-check-target-ip-10-0-129-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 990.388µs message: 'network-check-target-ip-10-0-129-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:13:20Z" - latency: 901.064µs message: 'network-check-target-ip-10-0-129-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:12:20Z" - latency: 1.162693ms message: 'network-check-target-ip-10-0-129-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:11:20Z" - latency: 1.265684ms message: 'network-check-target-ip-10-0-129-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:10:20Z" - latency: 1.038327ms message: 'network-check-target-ip-10-0-129-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:09:20Z" - latency: 872.423µs message: 'network-check-target-ip-10-0-129-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:08:20Z" - latency: 1.243487ms message: 'network-check-target-ip-10-0-129-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:07:20Z" - latency: 975.351µs message: 'network-check-target-ip-10-0-129-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:06:20Z" - latency: 733.051µs message: 'network-check-target-ip-10-0-129-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:05:20Z" - latency: 891.283µs message: 'network-check-target-ip-10-0-129-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:04:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T14:45:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-116-to-network-check-target-ip-10-0-135-57 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-116.ec2.internal uid: 6cbfd782-55e7-463a-a3f7-7325998cafc5 resourceVersion: "45668" uid: accb87fb-afa5-4324-8136-6ec64332e36a spec: sourcePod: network-check-source-6947749cfc-w62qp targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-14T14:52:20Z" message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.255576ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:13:20Z" - latency: 2.085616ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:12:20Z" - latency: 1.8522ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:11:20Z" - latency: 2.564962ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:10:20Z" - latency: 2.146208ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:09:20Z" - latency: 1.992307ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:08:20Z" - latency: 2.177952ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:07:20Z" - latency: 2.379843ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:06:20Z" - latency: 2.275051ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:05:20Z" - latency: 1.899685ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:04:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T14:45:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-116-to-network-check-target-ip-10-0-136-235 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-116.ec2.internal uid: 6cbfd782-55e7-463a-a3f7-7325998cafc5 resourceVersion: "45667" uid: 5eecdd75-a1f5-441c-9a2c-f14bd0e47280 spec: sourcePod: network-check-source-6947749cfc-w62qp targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-14T14:52:20Z" message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.005152ms message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:13:20Z" - latency: 1.700677ms message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:12:20Z" - latency: 2.110074ms message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:11:20Z" - latency: 2.028779ms message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:10:20Z" - latency: 2.425504ms message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:09:20Z" - latency: 2.240024ms message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:08:20Z" - latency: 2.59437ms message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:07:20Z" - latency: 2.560242ms message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:06:20Z" - latency: 1.965332ms message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:05:20Z" - latency: 1.779951ms message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:04:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T14:45:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-116-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-116.ec2.internal uid: 6cbfd782-55e7-463a-a3f7-7325998cafc5 resourceVersion: "47818" uid: 0ab5c4e2-baef-492c-9f8c-17eb0b515b17 spec: sourcePod: network-check-source-6947749cfc-w62qp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-14T14:51:20Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 851.29µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:15:20Z" - latency: 1.856373ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T15:15:20Z" - latency: 1.177539ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:14:20Z" - latency: 1.722391ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T15:14:20Z" - latency: 844.756µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:13:20Z" - latency: 2.34338ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T15:13:20Z" - latency: 1.124693ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:12:20Z" - latency: 1.708142ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T15:12:20Z" - latency: 886.33µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:11:20Z" - latency: 2.171826ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T15:11:20Z" kind: List metadata: resourceVersion: ""