apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T14:00:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-158-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-158.ec2.internal uid: 48984dab-bb86-476e-b080-5815183f95de resourceVersion: "67158" uid: 7edc621a-dc50-4383-8a93-fc19e6384c54 spec: sourcePod: network-check-source-6f8b768455-bshpr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-17T14:07:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 778.135µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:35:57Z" - latency: 1.108982ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:34:57Z" - latency: 1.164969ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:33:57Z" - latency: 952.562µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:32:57Z" - latency: 1.006298ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:31:57Z" - latency: 1.002166ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:30:57Z" - latency: 1.277877ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:29:57Z" - latency: 1.562162ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:28:57Z" - latency: 1.110508ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:27:57Z" - latency: 1.099025ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:26:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T14:00:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-158-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-158.ec2.internal uid: 48984dab-bb86-476e-b080-5815183f95de resourceVersion: "67980" uid: aeeeef2a-bbb5-4a68-95cc-25a50e984561 spec: sourcePod: network-check-source-6f8b768455-bshpr targetEndpoint: a583720877f4e4678ade211759fe14b2-d89cc6a543ba08cb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T14:06:57Z" message: 'load-balancer-api-external: tcp connection to a583720877f4e4678ade211759fe14b2-d89cc6a543ba08cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.457832ms message: 'load-balancer-api-external: tcp connection to a583720877f4e4678ade211759fe14b2-d89cc6a543ba08cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:36:57Z" - latency: 8.199942ms message: 'load-balancer-api-external: resolved host name a583720877f4e4678ade211759fe14b2-d89cc6a543ba08cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T14:36:57Z" - latency: 4.585486ms message: 'load-balancer-api-external: tcp connection to a583720877f4e4678ade211759fe14b2-d89cc6a543ba08cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:35:57Z" - latency: 8.964528ms message: 'load-balancer-api-external: resolved host name a583720877f4e4678ade211759fe14b2-d89cc6a543ba08cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T14:35:57Z" - latency: 5.217338ms message: 'load-balancer-api-external: tcp connection to a583720877f4e4678ade211759fe14b2-d89cc6a543ba08cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:34:57Z" - latency: 7.453344ms message: 'load-balancer-api-external: resolved host name a583720877f4e4678ade211759fe14b2-d89cc6a543ba08cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T14:34:57Z" - latency: 5.230349ms message: 'load-balancer-api-external: tcp connection to a583720877f4e4678ade211759fe14b2-d89cc6a543ba08cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:33:57Z" - latency: 7.533767ms message: 'load-balancer-api-external: resolved host name a583720877f4e4678ade211759fe14b2-d89cc6a543ba08cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T14:33:57Z" - latency: 6.136932ms message: 'load-balancer-api-external: tcp connection to a583720877f4e4678ade211759fe14b2-d89cc6a543ba08cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:32:57Z" - latency: 7.064365ms message: 'load-balancer-api-external: resolved host name a583720877f4e4678ade211759fe14b2-d89cc6a543ba08cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T14:32:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T14:00:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-158-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-158.ec2.internal uid: 48984dab-bb86-476e-b080-5815183f95de resourceVersion: "67981" uid: 55fc3334-8f7c-4ccb-b0a9-5e213f0cff9c spec: sourcePod: network-check-source-6f8b768455-bshpr targetEndpoint: a583720877f4e4678ade211759fe14b2-d89cc6a543ba08cb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T14:06:57Z" message: 'load-balancer-api-internal: tcp connection to a583720877f4e4678ade211759fe14b2-d89cc6a543ba08cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.189698ms message: 'load-balancer-api-internal: tcp connection to a583720877f4e4678ade211759fe14b2-d89cc6a543ba08cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:36:57Z" - latency: 8.25029ms message: 'load-balancer-api-internal: resolved host name a583720877f4e4678ade211759fe14b2-d89cc6a543ba08cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T14:36:57Z" - latency: 5.071458ms message: 'load-balancer-api-internal: tcp connection to a583720877f4e4678ade211759fe14b2-d89cc6a543ba08cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:35:57Z" - latency: 9.036554ms message: 'load-balancer-api-internal: resolved host name a583720877f4e4678ade211759fe14b2-d89cc6a543ba08cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T14:35:57Z" - latency: 5.212207ms message: 'load-balancer-api-internal: tcp connection to a583720877f4e4678ade211759fe14b2-d89cc6a543ba08cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:34:57Z" - latency: 7.399227ms message: 'load-balancer-api-internal: resolved host name a583720877f4e4678ade211759fe14b2-d89cc6a543ba08cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T14:34:57Z" - latency: 4.640725ms message: 'load-balancer-api-internal: tcp connection to a583720877f4e4678ade211759fe14b2-d89cc6a543ba08cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:33:57Z" - latency: 7.4401ms message: 'load-balancer-api-internal: resolved host name a583720877f4e4678ade211759fe14b2-d89cc6a543ba08cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T14:33:57Z" - latency: 6.070939ms message: 'load-balancer-api-internal: tcp connection to a583720877f4e4678ade211759fe14b2-d89cc6a543ba08cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:32:57Z" - latency: 7.139011ms message: 'load-balancer-api-internal: resolved host name a583720877f4e4678ade211759fe14b2-d89cc6a543ba08cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T14:32:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T14:00:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-158-to-network-check-target-ip-10-0-129-158 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-158.ec2.internal uid: 48984dab-bb86-476e-b080-5815183f95de resourceVersion: "67155" uid: bde5b500-5f69-4d64-9660-1a11c30a9756 spec: sourcePod: network-check-source-6f8b768455-bshpr targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-17T14:07:57Z" message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 826.498µs message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:35:57Z" - latency: 1.261244ms message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:34:57Z" - latency: 938.295µs message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:33:57Z" - latency: 956.811µs message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:32:57Z" - latency: 1.230389ms message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:31:57Z" - latency: 1.577718ms message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:30:57Z" - latency: 1.165375ms message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:29:57Z" - latency: 1.700857ms message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:28:57Z" - latency: 1.421946ms message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:27:57Z" - latency: 988.715µs message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:26:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T14:00:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-158-to-network-check-target-ip-10-0-130-163 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-158.ec2.internal uid: 48984dab-bb86-476e-b080-5815183f95de resourceVersion: "67157" uid: ab824e70-b5e9-466b-ab60-989bda679c09 spec: sourcePod: network-check-source-6f8b768455-bshpr targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-17T14:07:57Z" message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.154705ms message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:35:57Z" - latency: 2.456463ms message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:34:57Z" - latency: 2.363646ms message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:33:57Z" - latency: 2.505525ms message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:32:57Z" - latency: 2.431641ms message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:31:57Z" - latency: 2.282762ms message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:30:57Z" - latency: 2.425937ms message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:29:57Z" - latency: 1.998305ms message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:28:57Z" - latency: 2.97557ms message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:27:57Z" - latency: 1.822524ms message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:26:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T14:00:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-158-to-network-check-target-ip-10-0-132-81 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-158.ec2.internal uid: 48984dab-bb86-476e-b080-5815183f95de resourceVersion: "67156" uid: 4f7856aa-3b18-4cbf-84ba-0165375379ae spec: sourcePod: network-check-source-6f8b768455-bshpr targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-17T14:07:57Z" message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.832483ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:35:57Z" - latency: 2.38407ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:34:57Z" - latency: 2.333751ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:33:57Z" - latency: 2.079057ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:32:57Z" - latency: 2.338351ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:31:57Z" - latency: 2.428876ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:30:57Z" - latency: 1.978287ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:29:57Z" - latency: 2.430452ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:28:57Z" - latency: 2.625525ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:27:57Z" - latency: 2.276485ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:26:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T14:00:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-158-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-158.ec2.internal uid: 48984dab-bb86-476e-b080-5815183f95de resourceVersion: "67978" uid: 2bee4f6e-deb5-4ebb-af7c-555edd1b35bf spec: sourcePod: network-check-source-6f8b768455-bshpr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-17T14:06:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.462334ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:36:57Z" - latency: 1.62765ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T14:36:57Z" - latency: 965.828µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:35:57Z" - latency: 1.715932ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T14:35:57Z" - latency: 944.223µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:34:57Z" - latency: 1.678753ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T14:34:57Z" - latency: 897.978µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:33:57Z" - latency: 1.781909ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T14:33:57Z" - latency: 1.097992ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T14:32:57Z" - latency: 1.765601ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T14:32:57Z" kind: List metadata: resourceVersion: ""