apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T22:03:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-125-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-125.us-west-2.compute.internal uid: 24c56479-cd28-4dd6-9d55-b3d4f3c35845 resourceVersion: "111588" uid: 01413720-0934-4b9c-9ca3-731cb8f15c3a spec: sourcePod: network-check-source-6f78d59f99-zl5rs targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T22:10:18Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.426167ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:13:18Z" - latency: 1.177388ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:12:18Z" - latency: 1.546697ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:11:18Z" - latency: 1.235681ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:10:18Z" - latency: 1.478106ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:09:18Z" - latency: 1.011323ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:08:18Z" - latency: 1.42976ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:07:18Z" - latency: 1.369731ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:06:18Z" - latency: 1.330767ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:05:18Z" - latency: 1.503883ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:04:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T22:03:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-125-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-125.us-west-2.compute.internal uid: 24c56479-cd28-4dd6-9d55-b3d4f3c35845 resourceVersion: "108934" uid: 0256e779-bf50-406f-b0ab-79420696c61e spec: sourcePod: network-check-source-6f78d59f99-zl5rs targetEndpoint: a56facd814ea6491ea434b7fb55cee90-852268fd564bd9ac.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T22:09:18Z" message: 'load-balancer-api-external: tcp connection to a56facd814ea6491ea434b7fb55cee90-852268fd564bd9ac.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 51.311615ms message: 'load-balancer-api-external: tcp connection to a56facd814ea6491ea434b7fb55cee90-852268fd564bd9ac.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:09:18Z" - latency: 7.300468ms message: 'load-balancer-api-external: resolved host name a56facd814ea6491ea434b7fb55cee90-852268fd564bd9ac.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T23:09:18Z" - latency: 54.731629ms message: 'load-balancer-api-external: tcp connection to a56facd814ea6491ea434b7fb55cee90-852268fd564bd9ac.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:08:18Z" - latency: 13.603702ms message: 'load-balancer-api-external: resolved host name a56facd814ea6491ea434b7fb55cee90-852268fd564bd9ac.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T23:08:18Z" - latency: 53.650848ms message: 'load-balancer-api-external: tcp connection to a56facd814ea6491ea434b7fb55cee90-852268fd564bd9ac.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:07:18Z" - latency: 9.134314ms message: 'load-balancer-api-external: resolved host name a56facd814ea6491ea434b7fb55cee90-852268fd564bd9ac.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T23:07:18Z" - latency: 50.757324ms message: 'load-balancer-api-external: tcp connection to a56facd814ea6491ea434b7fb55cee90-852268fd564bd9ac.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:06:18Z" - latency: 8.985545ms message: 'load-balancer-api-external: resolved host name a56facd814ea6491ea434b7fb55cee90-852268fd564bd9ac.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T23:06:18Z" - latency: 56.373135ms message: 'load-balancer-api-external: tcp connection to a56facd814ea6491ea434b7fb55cee90-852268fd564bd9ac.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:05:18Z" - latency: 10.864224ms message: 'load-balancer-api-external: resolved host name a56facd814ea6491ea434b7fb55cee90-852268fd564bd9ac.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T23:05:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T22:03:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-125-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-125.us-west-2.compute.internal uid: 24c56479-cd28-4dd6-9d55-b3d4f3c35845 resourceVersion: "108933" uid: 731c080f-e07d-4194-b0e7-2cfcd78ab84a spec: sourcePod: network-check-source-6f78d59f99-zl5rs targetEndpoint: a56facd814ea6491ea434b7fb55cee90-852268fd564bd9ac.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T22:09:18Z" message: 'load-balancer-api-internal: tcp connection to a56facd814ea6491ea434b7fb55cee90-852268fd564bd9ac.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 51.065526ms message: 'load-balancer-api-internal: tcp connection to a56facd814ea6491ea434b7fb55cee90-852268fd564bd9ac.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:09:18Z" - latency: 7.24388ms message: 'load-balancer-api-internal: resolved host name a56facd814ea6491ea434b7fb55cee90-852268fd564bd9ac.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T23:09:18Z" - latency: 56.427923ms message: 'load-balancer-api-internal: tcp connection to a56facd814ea6491ea434b7fb55cee90-852268fd564bd9ac.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:08:18Z" - latency: 13.552335ms message: 'load-balancer-api-internal: resolved host name a56facd814ea6491ea434b7fb55cee90-852268fd564bd9ac.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T23:08:18Z" - latency: 50.534848ms message: 'load-balancer-api-internal: tcp connection to a56facd814ea6491ea434b7fb55cee90-852268fd564bd9ac.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:07:18Z" - latency: 9.073929ms message: 'load-balancer-api-internal: resolved host name a56facd814ea6491ea434b7fb55cee90-852268fd564bd9ac.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T23:07:18Z" - latency: 53.831893ms message: 'load-balancer-api-internal: tcp connection to a56facd814ea6491ea434b7fb55cee90-852268fd564bd9ac.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:06:18Z" - latency: 8.788941ms message: 'load-balancer-api-internal: resolved host name a56facd814ea6491ea434b7fb55cee90-852268fd564bd9ac.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T23:06:18Z" - latency: 56.391222ms message: 'load-balancer-api-internal: tcp connection to a56facd814ea6491ea434b7fb55cee90-852268fd564bd9ac.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:05:18Z" - latency: 10.749086ms message: 'load-balancer-api-internal: resolved host name a56facd814ea6491ea434b7fb55cee90-852268fd564bd9ac.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T23:05:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T22:03:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-125-to-network-check-target-ip-10-0-129-125 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-125.us-west-2.compute.internal uid: 24c56479-cd28-4dd6-9d55-b3d4f3c35845 resourceVersion: "111584" uid: 0c6e43cb-0411-4031-af46-79af9b0a1650 spec: sourcePod: network-check-source-6f78d59f99-zl5rs targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T22:10:18Z" message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.013493ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:13:18Z" - latency: 987.994µs message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:12:18Z" - latency: 1.79894ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:11:18Z" - latency: 873.785µs message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:10:18Z" - latency: 1.006244ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:09:18Z" - latency: 1.299515ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:08:18Z" - latency: 938.792µs message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:07:18Z" - latency: 1.483927ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:06:18Z" - latency: 1.435576ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:05:18Z" - latency: 1.817617ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:04:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T22:03:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-125-to-network-check-target-ip-10-0-134-125 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-125.us-west-2.compute.internal uid: 24c56479-cd28-4dd6-9d55-b3d4f3c35845 resourceVersion: "111585" uid: 0a0f26c6-e0b1-4996-b6dc-b7b8c2755f15 spec: sourcePod: network-check-source-6f78d59f99-zl5rs targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T22:10:18Z" message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.164245ms message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:13:18Z" - latency: 2.135969ms message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:12:18Z" - latency: 2.417157ms message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:11:18Z" - latency: 2.526049ms message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:10:18Z" - latency: 1.998331ms message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:09:18Z" - latency: 2.596708ms message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:08:18Z" - latency: 2.245886ms message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:07:18Z" - latency: 2.361197ms message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:06:18Z" - latency: 2.290234ms message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:05:18Z" - latency: 2.146255ms message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:04:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T22:03:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-125-to-network-check-target-ip-10-0-141-194 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-125.us-west-2.compute.internal uid: 24c56479-cd28-4dd6-9d55-b3d4f3c35845 resourceVersion: "111586" uid: 5dda5f06-db33-41d4-a291-55dd396874ba spec: sourcePod: network-check-source-6f78d59f99-zl5rs targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T22:10:18Z" message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.529924ms message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:13:18Z" - latency: 2.337437ms message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:12:18Z" - latency: 3.032354ms message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:11:18Z" - latency: 2.532646ms message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:10:18Z" - latency: 2.581339ms message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:09:18Z" - latency: 2.148853ms message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:08:18Z" - latency: 2.54503ms message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:07:18Z" - latency: 2.674734ms message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:06:18Z" - latency: 2.200163ms message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:05:18Z" - latency: 2.692359ms message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:04:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T22:03:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-125-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-125.us-west-2.compute.internal uid: 24c56479-cd28-4dd6-9d55-b3d4f3c35845 resourceVersion: "108930" uid: 27c50042-70ea-4fd6-8e01-b98aa3ead305 spec: sourcePod: network-check-source-6f78d59f99-zl5rs targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T22:09:18Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.245656ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:09:18Z" - latency: 1.959262ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T23:09:18Z" - latency: 1.152861ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:08:18Z" - latency: 2.510516ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T23:08:18Z" - latency: 884.922µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:07:18Z" - latency: 1.894097ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T23:07:18Z" - latency: 1.048459ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:06:18Z" - latency: 2.314486ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T23:06:18Z" - latency: 1.3924ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:05:18Z" - latency: 1.834772ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T23:05:18Z" kind: List metadata: resourceVersion: ""