apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:31:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-49-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-49.us-west-2.compute.internal uid: 2da8d096-ad06-4ce2-ab13-0687e529814b resourceVersion: "109892" uid: 0aef116d-c58f-4d55-81b7-d343d8771a16 spec: sourcePod: network-check-source-6f78d59f99-hpm76 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T20:38:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.772831ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:41:29Z" - latency: 1.013959ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:40:29Z" - latency: 1.384531ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:39:29Z" - latency: 5.196451ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:38:29Z" - latency: 1.229084ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:37:29Z" - latency: 1.571867ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:36:29Z" - latency: 1.095457ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:35:29Z" - latency: 930.032µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:34:29Z" - latency: 3.088595ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:33:29Z" - latency: 997.966µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:32:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:31:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-49-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-49.us-west-2.compute.internal uid: 2da8d096-ad06-4ce2-ab13-0687e529814b resourceVersion: "107216" uid: a593fad5-f8c2-41b5-b2f7-42a7a1dcc6b5 spec: sourcePod: network-check-source-6f78d59f99-hpm76 targetEndpoint: a6eb617b3f8214fa495946204f12b38d-1c21b587483bc72e.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T20:37:29Z" message: 'load-balancer-api-external: tcp connection to a6eb617b3f8214fa495946204f12b38d-1c21b587483bc72e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 50.552701ms message: 'load-balancer-api-external: tcp connection to a6eb617b3f8214fa495946204f12b38d-1c21b587483bc72e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:37:29Z" - latency: 7.015264ms message: 'load-balancer-api-external: resolved host name a6eb617b3f8214fa495946204f12b38d-1c21b587483bc72e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:37:29Z" - latency: 50.656394ms message: 'load-balancer-api-external: tcp connection to a6eb617b3f8214fa495946204f12b38d-1c21b587483bc72e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:36:29Z" - latency: 9.435029ms message: 'load-balancer-api-external: resolved host name a6eb617b3f8214fa495946204f12b38d-1c21b587483bc72e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:36:29Z" - latency: 55.241276ms message: 'load-balancer-api-external: tcp connection to a6eb617b3f8214fa495946204f12b38d-1c21b587483bc72e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:35:29Z" - latency: 7.425506ms message: 'load-balancer-api-external: resolved host name a6eb617b3f8214fa495946204f12b38d-1c21b587483bc72e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:35:29Z" - latency: 57.800618ms message: 'load-balancer-api-external: tcp connection to a6eb617b3f8214fa495946204f12b38d-1c21b587483bc72e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:34:29Z" - latency: 8.400582ms message: 'load-balancer-api-external: resolved host name a6eb617b3f8214fa495946204f12b38d-1c21b587483bc72e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:34:29Z" - latency: 55.286951ms message: 'load-balancer-api-external: tcp connection to a6eb617b3f8214fa495946204f12b38d-1c21b587483bc72e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:33:29Z" - latency: 8.787767ms message: 'load-balancer-api-external: resolved host name a6eb617b3f8214fa495946204f12b38d-1c21b587483bc72e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:33:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:31:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-49-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-49.us-west-2.compute.internal uid: 2da8d096-ad06-4ce2-ab13-0687e529814b resourceVersion: "107217" uid: 0a73e07a-a9eb-407c-8b08-d9990b8bac36 spec: sourcePod: network-check-source-6f78d59f99-hpm76 targetEndpoint: a6eb617b3f8214fa495946204f12b38d-1c21b587483bc72e.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T20:37:29Z" message: 'load-balancer-api-internal: tcp connection to a6eb617b3f8214fa495946204f12b38d-1c21b587483bc72e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.134353ms message: 'load-balancer-api-internal: tcp connection to a6eb617b3f8214fa495946204f12b38d-1c21b587483bc72e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:37:29Z" - latency: 6.893834ms message: 'load-balancer-api-internal: resolved host name a6eb617b3f8214fa495946204f12b38d-1c21b587483bc72e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:37:29Z" - latency: 52.7731ms message: 'load-balancer-api-internal: tcp connection to a6eb617b3f8214fa495946204f12b38d-1c21b587483bc72e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:36:29Z" - latency: 9.489198ms message: 'load-balancer-api-internal: resolved host name a6eb617b3f8214fa495946204f12b38d-1c21b587483bc72e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:36:29Z" - latency: 51.087364ms message: 'load-balancer-api-internal: tcp connection to a6eb617b3f8214fa495946204f12b38d-1c21b587483bc72e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:35:29Z" - latency: 7.454871ms message: 'load-balancer-api-internal: resolved host name a6eb617b3f8214fa495946204f12b38d-1c21b587483bc72e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:35:29Z" - latency: 57.78351ms message: 'load-balancer-api-internal: tcp connection to a6eb617b3f8214fa495946204f12b38d-1c21b587483bc72e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:34:29Z" - latency: 8.463202ms message: 'load-balancer-api-internal: resolved host name a6eb617b3f8214fa495946204f12b38d-1c21b587483bc72e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:34:29Z" - latency: 57.157999ms message: 'load-balancer-api-internal: tcp connection to a6eb617b3f8214fa495946204f12b38d-1c21b587483bc72e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:33:29Z" - latency: 8.398047ms message: 'load-balancer-api-internal: resolved host name a6eb617b3f8214fa495946204f12b38d-1c21b587483bc72e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:33:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:31:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-49-to-network-check-target-ip-10-0-128-49 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-49.us-west-2.compute.internal uid: 2da8d096-ad06-4ce2-ab13-0687e529814b resourceVersion: "109888" uid: 23350cde-680e-4645-85c9-e7f3267ea556 spec: sourcePod: network-check-source-6f78d59f99-hpm76 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:38:29Z" message: 'network-check-target-ip-10-0-128-49: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.45998ms message: 'network-check-target-ip-10-0-128-49: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:41:29Z" - latency: 1.682683ms message: 'network-check-target-ip-10-0-128-49: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:40:29Z" - latency: 1.224043ms message: 'network-check-target-ip-10-0-128-49: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:39:29Z" - latency: 5.012478ms message: 'network-check-target-ip-10-0-128-49: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:38:29Z" - latency: 1.188869ms message: 'network-check-target-ip-10-0-128-49: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:37:29Z" - latency: 1.730106ms message: 'network-check-target-ip-10-0-128-49: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:36:29Z" - latency: 1.414863ms message: 'network-check-target-ip-10-0-128-49: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:35:29Z" - latency: 1.324059ms message: 'network-check-target-ip-10-0-128-49: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:34:29Z" - latency: 1.965519ms message: 'network-check-target-ip-10-0-128-49: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:33:29Z" - latency: 1.645827ms message: 'network-check-target-ip-10-0-128-49: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:32:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:31:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-49-to-network-check-target-ip-10-0-134-71 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-49.us-west-2.compute.internal uid: 2da8d096-ad06-4ce2-ab13-0687e529814b resourceVersion: "109889" uid: 05fc548a-4aa9-4b7a-8a7a-b805da6e4822 spec: sourcePod: network-check-source-6f78d59f99-hpm76 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:38:29Z" message: 'network-check-target-ip-10-0-134-71: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.356914ms message: 'network-check-target-ip-10-0-134-71: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:41:29Z" - latency: 2.5679ms message: 'network-check-target-ip-10-0-134-71: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:40:29Z" - latency: 2.516454ms message: 'network-check-target-ip-10-0-134-71: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:39:29Z" - latency: 4.948587ms message: 'network-check-target-ip-10-0-134-71: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:38:29Z" - latency: 2.476948ms message: 'network-check-target-ip-10-0-134-71: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:37:29Z" - latency: 2.093835ms message: 'network-check-target-ip-10-0-134-71: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:36:29Z" - latency: 2.363229ms message: 'network-check-target-ip-10-0-134-71: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:35:29Z" - latency: 2.292983ms message: 'network-check-target-ip-10-0-134-71: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:34:29Z" - latency: 4.501419ms message: 'network-check-target-ip-10-0-134-71: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:33:29Z" - latency: 2.376698ms message: 'network-check-target-ip-10-0-134-71: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:32:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:31:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-49-to-network-check-target-ip-10-0-138-26 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-49.us-west-2.compute.internal uid: 2da8d096-ad06-4ce2-ab13-0687e529814b resourceVersion: "109890" uid: e7b1b66b-21cc-46e7-9180-a3f851f1df35 spec: sourcePod: network-check-source-6f78d59f99-hpm76 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:38:29Z" message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.350347ms message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:41:29Z" - latency: 2.688408ms message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:40:29Z" - latency: 2.96773ms message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:39:29Z" - latency: 4.977505ms message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:38:29Z" - latency: 2.517932ms message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:37:29Z" - latency: 2.517765ms message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:36:29Z" - latency: 2.51026ms message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:35:29Z" - latency: 2.289234ms message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:34:29Z" - latency: 4.176592ms message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:33:29Z" - latency: 2.451951ms message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:32:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:31:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-49-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-49.us-west-2.compute.internal uid: 2da8d096-ad06-4ce2-ab13-0687e529814b resourceVersion: "107214" uid: 6f7c5e96-0c5e-4562-9eee-9323eb6ed141 spec: sourcePod: network-check-source-6f78d59f99-hpm76 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T20:37:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.10018ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:37:29Z" - latency: 1.91454ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:37:29Z" - latency: 1.164929ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:36:29Z" - latency: 2.129505ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:36:29Z" - latency: 1.625216ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:35:29Z" - latency: 2.209606ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:35:29Z" - latency: 970.184µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:34:29Z" - latency: 2.424021ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:34:29Z" - latency: 1.263068ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:33:29Z" - latency: 2.707088ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:33:29Z" kind: List metadata: resourceVersion: ""