apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T22:51:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-176-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-176.us-west-1.compute.internal uid: 16447942-3c9f-4701-ba78-8260a80c54b7 resourceVersion: "166093" uid: bcae4494-920e-4924-ae6a-ec3a28e4eeec spec: sourcePod: network-check-source-6f78d59f99-nbswd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T22:58:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.276151ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:43:15Z" - latency: 1.108599ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:42:15Z" - latency: 1.536542ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:41:15Z" - latency: 1.36038ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:40:15Z" - latency: 1.071481ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:39:15Z" - latency: 1.048603ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:38:15Z" - latency: 1.11695ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:37:15Z" - latency: 1.260753ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:36:15Z" - latency: 1.331192ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:35:15Z" - latency: 1.050551ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:34:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T22:51:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-176-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-176.us-west-1.compute.internal uid: 16447942-3c9f-4701-ba78-8260a80c54b7 resourceVersion: "167566" uid: 0d56c04f-47d8-451b-a852-2d302727cbdc spec: sourcePod: network-check-source-6f78d59f99-nbswd targetEndpoint: ae6c114d507d041eea76c03a1ba35e05-cac881102500eba0.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T22:57:15Z" message: 'load-balancer-api-external: tcp connection to ae6c114d507d041eea76c03a1ba35e05-cac881102500eba0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 52.650994ms message: 'load-balancer-api-external: tcp connection to ae6c114d507d041eea76c03a1ba35e05-cac881102500eba0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:45:15Z" - latency: 6.928916ms message: 'load-balancer-api-external: resolved host name ae6c114d507d041eea76c03a1ba35e05-cac881102500eba0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T00:45:15Z" - latency: 55.910336ms message: 'load-balancer-api-external: tcp connection to ae6c114d507d041eea76c03a1ba35e05-cac881102500eba0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:44:15Z" - latency: 7.302207ms message: 'load-balancer-api-external: resolved host name ae6c114d507d041eea76c03a1ba35e05-cac881102500eba0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T00:44:15Z" - latency: 55.031728ms message: 'load-balancer-api-external: tcp connection to ae6c114d507d041eea76c03a1ba35e05-cac881102500eba0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:43:15Z" - latency: 6.888613ms message: 'load-balancer-api-external: resolved host name ae6c114d507d041eea76c03a1ba35e05-cac881102500eba0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T00:43:15Z" - latency: 52.340674ms message: 'load-balancer-api-external: tcp connection to ae6c114d507d041eea76c03a1ba35e05-cac881102500eba0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:42:15Z" - latency: 6.832556ms message: 'load-balancer-api-external: resolved host name ae6c114d507d041eea76c03a1ba35e05-cac881102500eba0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T00:42:15Z" - latency: 52.238952ms message: 'load-balancer-api-external: tcp connection to ae6c114d507d041eea76c03a1ba35e05-cac881102500eba0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:41:15Z" - latency: 6.906156ms message: 'load-balancer-api-external: resolved host name ae6c114d507d041eea76c03a1ba35e05-cac881102500eba0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T00:41:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T22:51:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-176-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-176.us-west-1.compute.internal uid: 16447942-3c9f-4701-ba78-8260a80c54b7 resourceVersion: "167565" uid: 71cb97d0-f942-4b8a-add7-f823612f2b8d spec: sourcePod: network-check-source-6f78d59f99-nbswd targetEndpoint: ae6c114d507d041eea76c03a1ba35e05-cac881102500eba0.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T22:57:15Z" message: 'load-balancer-api-internal: tcp connection to ae6c114d507d041eea76c03a1ba35e05-cac881102500eba0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 52.615561ms message: 'load-balancer-api-internal: tcp connection to ae6c114d507d041eea76c03a1ba35e05-cac881102500eba0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:45:15Z" - latency: 6.863821ms message: 'load-balancer-api-internal: resolved host name ae6c114d507d041eea76c03a1ba35e05-cac881102500eba0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T00:45:15Z" - latency: 55.175145ms message: 'load-balancer-api-internal: tcp connection to ae6c114d507d041eea76c03a1ba35e05-cac881102500eba0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:44:15Z" - latency: 7.291847ms message: 'load-balancer-api-internal: resolved host name ae6c114d507d041eea76c03a1ba35e05-cac881102500eba0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T00:44:15Z" - latency: 53.67663ms message: 'load-balancer-api-internal: tcp connection to ae6c114d507d041eea76c03a1ba35e05-cac881102500eba0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:43:15Z" - latency: 6.839132ms message: 'load-balancer-api-internal: resolved host name ae6c114d507d041eea76c03a1ba35e05-cac881102500eba0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T00:43:15Z" - latency: 52.320324ms message: 'load-balancer-api-internal: tcp connection to ae6c114d507d041eea76c03a1ba35e05-cac881102500eba0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:42:15Z" - latency: 6.698266ms message: 'load-balancer-api-internal: resolved host name ae6c114d507d041eea76c03a1ba35e05-cac881102500eba0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T00:42:15Z" - latency: 52.244831ms message: 'load-balancer-api-internal: tcp connection to ae6c114d507d041eea76c03a1ba35e05-cac881102500eba0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:41:15Z" - latency: 6.877596ms message: 'load-balancer-api-internal: resolved host name ae6c114d507d041eea76c03a1ba35e05-cac881102500eba0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T00:41:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T22:51:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-176-to-network-check-target-ip-10-0-135-176 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-176.us-west-1.compute.internal uid: 16447942-3c9f-4701-ba78-8260a80c54b7 resourceVersion: "166088" uid: 2d444754-37a7-4304-9f29-c2f4361e9347 spec: sourcePod: network-check-source-6f78d59f99-nbswd targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T22:58:15Z" message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.083522ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:43:15Z" - latency: 1.156475ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:42:15Z" - latency: 1.084703ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:41:15Z" - latency: 1.138586ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:40:15Z" - latency: 1.675799ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:39:15Z" - latency: 1.122396ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:38:15Z" - latency: 1.019343ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:37:15Z" - latency: 1.863084ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:36:15Z" - latency: 1.411337ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:35:15Z" - latency: 1.856822ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:34:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T22:51:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-176-to-network-check-target-ip-10-0-135-179 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-176.us-west-1.compute.internal uid: 16447942-3c9f-4701-ba78-8260a80c54b7 resourceVersion: "166089" uid: 9e4ee064-a3c0-41d1-8e8a-632d2b67a2bf spec: sourcePod: network-check-source-6f78d59f99-nbswd targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T22:58:15Z" message: 'network-check-target-ip-10-0-135-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.912027ms message: 'network-check-target-ip-10-0-135-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:43:15Z" - latency: 2.308261ms message: 'network-check-target-ip-10-0-135-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:42:15Z" - latency: 2.517838ms message: 'network-check-target-ip-10-0-135-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:41:15Z" - latency: 2.545615ms message: 'network-check-target-ip-10-0-135-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:40:15Z" - latency: 2.498484ms message: 'network-check-target-ip-10-0-135-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:39:15Z" - latency: 2.122433ms message: 'network-check-target-ip-10-0-135-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:38:15Z" - latency: 2.25579ms message: 'network-check-target-ip-10-0-135-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:37:15Z" - latency: 2.860355ms message: 'network-check-target-ip-10-0-135-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:36:15Z" - latency: 2.352619ms message: 'network-check-target-ip-10-0-135-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:35:15Z" - latency: 2.094646ms message: 'network-check-target-ip-10-0-135-179: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:34:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T22:51:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-176-to-network-check-target-ip-10-0-135-250 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-176.us-west-1.compute.internal uid: 16447942-3c9f-4701-ba78-8260a80c54b7 resourceVersion: "166091" uid: fbc4b05f-7694-442a-a959-114d9a5d3cab spec: sourcePod: network-check-source-6f78d59f99-nbswd targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T22:58:15Z" message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.310001ms message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:43:15Z" - latency: 2.49979ms message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:42:15Z" - latency: 2.702447ms message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:41:15Z" - latency: 2.448161ms message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:40:15Z" - latency: 2.576132ms message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:39:15Z" - latency: 2.309168ms message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:38:15Z" - latency: 2.42996ms message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:37:15Z" - latency: 2.95537ms message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:36:15Z" - latency: 2.560496ms message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:35:15Z" - latency: 2.469263ms message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:34:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T22:51:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-176-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-176.us-west-1.compute.internal uid: 16447942-3c9f-4701-ba78-8260a80c54b7 resourceVersion: "167562" uid: 9e31b784-adac-4204-9ed2-4c0ff858eec4 spec: sourcePod: network-check-source-6f78d59f99-nbswd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T22:57:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 937.909µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:45:15Z" - latency: 1.995128ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T00:45:15Z" - latency: 992.433µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:44:15Z" - latency: 2.129062ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T00:44:15Z" - latency: 968.967µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:43:15Z" - latency: 1.993486ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T00:43:15Z" - latency: 1.151339ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:42:15Z" - latency: 2.448296ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T00:42:15Z" - latency: 1.142711ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:41:15Z" - latency: 1.997094ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T00:41:15Z" kind: List metadata: resourceVersion: ""