apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T03:17:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-132-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-132.us-east-2.compute.internal uid: f403c457-dc44-42f1-9e1c-450f98c73971 resourceVersion: "167573" uid: a693c81f-6e09-47db-b963-a50ff88ac017 spec: sourcePod: network-check-source-6f78d59f99-29k8x targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-31T03:24: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.626607ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:13:51Z" - latency: 1.284698ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:12:51Z" - latency: 1.989066ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:11:51Z" - latency: 1.309521ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:10:51Z" - latency: 1.301235ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:09:51Z" - latency: 1.088565ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:08:51Z" - latency: 1.402461ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:07:51Z" - latency: 1.129662ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:06:51Z" - latency: 1.324368ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:05:51Z" - latency: 1.073604ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:04:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T03:17:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-132-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-132.us-east-2.compute.internal uid: f403c457-dc44-42f1-9e1c-450f98c73971 resourceVersion: "171504" uid: fb0cb12d-275c-45a6-9e87-93821538928d spec: sourcePod: network-check-source-6f78d59f99-29k8x targetEndpoint: af6a7ad6ee13349fbab82a958e87be0e-08cdb37e7c2eef84.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T03:23:51Z" message: 'load-balancer-api-external: tcp connection to af6a7ad6ee13349fbab82a958e87be0e-08cdb37e7c2eef84.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.14643ms message: 'load-balancer-api-external: tcp connection to af6a7ad6ee13349fbab82a958e87be0e-08cdb37e7c2eef84.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:17:51Z" - latency: 7.573705ms message: 'load-balancer-api-external: resolved host name af6a7ad6ee13349fbab82a958e87be0e-08cdb37e7c2eef84.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:17:51Z" - latency: 5.846275ms message: 'load-balancer-api-external: tcp connection to af6a7ad6ee13349fbab82a958e87be0e-08cdb37e7c2eef84.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:16:51Z" - latency: 6.792983ms message: 'load-balancer-api-external: resolved host name af6a7ad6ee13349fbab82a958e87be0e-08cdb37e7c2eef84.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:16:51Z" - latency: 6.178339ms message: 'load-balancer-api-external: tcp connection to af6a7ad6ee13349fbab82a958e87be0e-08cdb37e7c2eef84.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:15:51Z" - latency: 7.067674ms message: 'load-balancer-api-external: resolved host name af6a7ad6ee13349fbab82a958e87be0e-08cdb37e7c2eef84.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:15:51Z" - latency: 6.462509ms message: 'load-balancer-api-external: tcp connection to af6a7ad6ee13349fbab82a958e87be0e-08cdb37e7c2eef84.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:14:51Z" - latency: 7.71251ms message: 'load-balancer-api-external: resolved host name af6a7ad6ee13349fbab82a958e87be0e-08cdb37e7c2eef84.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:14:51Z" - latency: 5.322104ms message: 'load-balancer-api-external: tcp connection to af6a7ad6ee13349fbab82a958e87be0e-08cdb37e7c2eef84.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:13:51Z" - latency: 7.760333ms message: 'load-balancer-api-external: resolved host name af6a7ad6ee13349fbab82a958e87be0e-08cdb37e7c2eef84.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:13:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T03:17:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-132-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-132.us-east-2.compute.internal uid: f403c457-dc44-42f1-9e1c-450f98c73971 resourceVersion: "171503" uid: 5201e1bc-25c1-4c48-b721-0805587a906b spec: sourcePod: network-check-source-6f78d59f99-29k8x targetEndpoint: af6a7ad6ee13349fbab82a958e87be0e-08cdb37e7c2eef84.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T03:23:51Z" message: 'load-balancer-api-internal: tcp connection to af6a7ad6ee13349fbab82a958e87be0e-08cdb37e7c2eef84.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.887167ms message: 'load-balancer-api-internal: tcp connection to af6a7ad6ee13349fbab82a958e87be0e-08cdb37e7c2eef84.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:17:51Z" - latency: 7.657104ms message: 'load-balancer-api-internal: resolved host name af6a7ad6ee13349fbab82a958e87be0e-08cdb37e7c2eef84.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:17:51Z" - latency: 5.879121ms message: 'load-balancer-api-internal: tcp connection to af6a7ad6ee13349fbab82a958e87be0e-08cdb37e7c2eef84.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:16:51Z" - latency: 6.888337ms message: 'load-balancer-api-internal: resolved host name af6a7ad6ee13349fbab82a958e87be0e-08cdb37e7c2eef84.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:16:51Z" - latency: 5.299764ms message: 'load-balancer-api-internal: tcp connection to af6a7ad6ee13349fbab82a958e87be0e-08cdb37e7c2eef84.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:15:51Z" - latency: 7.036052ms message: 'load-balancer-api-internal: resolved host name af6a7ad6ee13349fbab82a958e87be0e-08cdb37e7c2eef84.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:15:51Z" - latency: 6.375507ms message: 'load-balancer-api-internal: tcp connection to af6a7ad6ee13349fbab82a958e87be0e-08cdb37e7c2eef84.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:14:51Z" - latency: 7.762398ms message: 'load-balancer-api-internal: resolved host name af6a7ad6ee13349fbab82a958e87be0e-08cdb37e7c2eef84.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:14:51Z" - latency: 5.336067ms message: 'load-balancer-api-internal: tcp connection to af6a7ad6ee13349fbab82a958e87be0e-08cdb37e7c2eef84.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:13:51Z" - latency: 7.712003ms message: 'load-balancer-api-internal: resolved host name af6a7ad6ee13349fbab82a958e87be0e-08cdb37e7c2eef84.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:13:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T03:17:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-132-to-network-check-target-ip-10-0-129-132 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-132.us-east-2.compute.internal uid: f403c457-dc44-42f1-9e1c-450f98c73971 resourceVersion: "167570" uid: 1246240c-17c7-478f-ade4-fac8fc1c62e7 spec: sourcePod: network-check-source-6f78d59f99-29k8x targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-31T03:24:51Z" message: 'network-check-target-ip-10-0-129-132: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.91211ms message: 'network-check-target-ip-10-0-129-132: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:13:51Z" - latency: 1.106004ms message: 'network-check-target-ip-10-0-129-132: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:12:51Z" - latency: 1.902523ms message: 'network-check-target-ip-10-0-129-132: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:11:51Z" - latency: 1.203498ms message: 'network-check-target-ip-10-0-129-132: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:10:51Z" - latency: 954.854µs message: 'network-check-target-ip-10-0-129-132: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:09:51Z" - latency: 936.451µs message: 'network-check-target-ip-10-0-129-132: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:08:51Z" - latency: 993.991µs message: 'network-check-target-ip-10-0-129-132: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:07:51Z" - latency: 1.70811ms message: 'network-check-target-ip-10-0-129-132: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:06:51Z" - latency: 1.108779ms message: 'network-check-target-ip-10-0-129-132: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:05:51Z" - latency: 1.346867ms message: 'network-check-target-ip-10-0-129-132: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:04:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T03:17:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-132-to-network-check-target-ip-10-0-141-153 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-132.us-east-2.compute.internal uid: f403c457-dc44-42f1-9e1c-450f98c73971 resourceVersion: "167571" uid: 762c9005-31ea-45a7-b3df-81cfec1f7ae3 spec: sourcePod: network-check-source-6f78d59f99-29k8x targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-31T03:24:51Z" message: 'network-check-target-ip-10-0-141-153: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.532375ms message: 'network-check-target-ip-10-0-141-153: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:13:51Z" - latency: 3.003505ms message: 'network-check-target-ip-10-0-141-153: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:12:51Z" - latency: 3.145911ms message: 'network-check-target-ip-10-0-141-153: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:11:51Z" - latency: 3.017497ms message: 'network-check-target-ip-10-0-141-153: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:10:51Z" - latency: 2.629525ms message: 'network-check-target-ip-10-0-141-153: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:09:51Z" - latency: 2.654033ms message: 'network-check-target-ip-10-0-141-153: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:08:51Z" - latency: 2.427166ms message: 'network-check-target-ip-10-0-141-153: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:07:51Z" - latency: 2.765157ms message: 'network-check-target-ip-10-0-141-153: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:06:51Z" - latency: 2.831692ms message: 'network-check-target-ip-10-0-141-153: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:05:51Z" - latency: 2.554064ms message: 'network-check-target-ip-10-0-141-153: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:04:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T03:53:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-132-to-network-check-target-ip-10-0-142-76 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-132.us-east-2.compute.internal uid: f403c457-dc44-42f1-9e1c-450f98c73971 resourceVersion: "169267" uid: cc76da5a-ad43-46ce-a8d9-64cc50e43683 spec: sourcePod: network-check-source-6f78d59f99-29k8x targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-31T04:00:36Z" message: 'network-check-target-ip-10-0-142-76: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.876511ms message: 'network-check-target-ip-10-0-142-76: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:14:36Z" - latency: 2.395999ms message: 'network-check-target-ip-10-0-142-76: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:13:36Z" - latency: 2.989198ms message: 'network-check-target-ip-10-0-142-76: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:12:36Z" - latency: 3.061796ms message: 'network-check-target-ip-10-0-142-76: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:11:36Z" - latency: 2.802986ms message: 'network-check-target-ip-10-0-142-76: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:10:36Z" - latency: 2.845531ms message: 'network-check-target-ip-10-0-142-76: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:09:36Z" - latency: 2.893859ms message: 'network-check-target-ip-10-0-142-76: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:08:36Z" - latency: 2.397018ms message: 'network-check-target-ip-10-0-142-76: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:07:36Z" - latency: 2.3315ms message: 'network-check-target-ip-10-0-142-76: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:06:36Z" - latency: 2.574663ms message: 'network-check-target-ip-10-0-142-76: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:05:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T03:17:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-132-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-132.us-east-2.compute.internal uid: f403c457-dc44-42f1-9e1c-450f98c73971 resourceVersion: "171502" uid: 66a4ddb7-9ec3-436c-bc91-4798d99603e9 spec: sourcePod: network-check-source-6f78d59f99-29k8x targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-31T03:23:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.5679ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:17:51Z" - latency: 2.116812ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T04:17:51Z" - latency: 2.302441ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:16:51Z" - latency: 1.907831ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T04:16:51Z" - latency: 1.110166ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:15:51Z" - latency: 1.948059ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T04:15:51Z" - latency: 2.89657ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:14:51Z" - latency: 2.623588ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T04:14:51Z" - latency: 2.431023ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:13:51Z" - latency: 2.19919ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T04:13:51Z" kind: List metadata: resourceVersion: ""