apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:20:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-66-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-66.ec2.internal uid: 803f4272-cff7-4491-86bc-e441020fc7d8 resourceVersion: "165058" uid: 37193ab2-f29f-475f-af73-79a811f7175e spec: sourcePod: network-check-source-6f78d59f99-fjxrl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-31T00:27:33Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 979.877µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:37:33Z" - latency: 1.164698ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:36:33Z" - latency: 1.253331ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:35:33Z" - latency: 1.334654ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:34:33Z" - latency: 891.623µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:33:33Z" - latency: 1.165967ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:32:33Z" - latency: 931.688µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:31:33Z" - latency: 1.251736ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:30:33Z" - latency: 781.771µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:29:33Z" - latency: 850.965µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:28:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:20:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-66-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-66.ec2.internal uid: 803f4272-cff7-4491-86bc-e441020fc7d8 resourceVersion: "166525" uid: 08a4ec64-0367-4d58-aca5-26ec60d2920a spec: sourcePod: network-check-source-6f78d59f99-fjxrl targetEndpoint: a8b9f89d97ff445a58c24085272709e4-47e4164e70bba09b.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T00:26:33Z" message: 'load-balancer-api-external: tcp connection to a8b9f89d97ff445a58c24085272709e4-47e4164e70bba09b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 16.74718ms message: 'load-balancer-api-external: tcp connection to a8b9f89d97ff445a58c24085272709e4-47e4164e70bba09b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:38:33Z" - latency: 6.906857ms message: 'load-balancer-api-external: resolved host name a8b9f89d97ff445a58c24085272709e4-47e4164e70bba09b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:38:33Z" - latency: 18.902833ms message: 'load-balancer-api-external: tcp connection to a8b9f89d97ff445a58c24085272709e4-47e4164e70bba09b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:37:33Z" - latency: 7.530683ms message: 'load-balancer-api-external: resolved host name a8b9f89d97ff445a58c24085272709e4-47e4164e70bba09b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:37:33Z" - latency: 18.152724ms message: 'load-balancer-api-external: tcp connection to a8b9f89d97ff445a58c24085272709e4-47e4164e70bba09b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:36:33Z" - latency: 7.271881ms message: 'load-balancer-api-external: resolved host name a8b9f89d97ff445a58c24085272709e4-47e4164e70bba09b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:36:33Z" - latency: 14.793483ms message: 'load-balancer-api-external: tcp connection to a8b9f89d97ff445a58c24085272709e4-47e4164e70bba09b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:35:33Z" - latency: 7.416014ms message: 'load-balancer-api-external: resolved host name a8b9f89d97ff445a58c24085272709e4-47e4164e70bba09b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:35:33Z" - latency: 25.623104ms message: 'load-balancer-api-external: tcp connection to a8b9f89d97ff445a58c24085272709e4-47e4164e70bba09b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:34:33Z" - latency: 10.560191ms message: 'load-balancer-api-external: resolved host name a8b9f89d97ff445a58c24085272709e4-47e4164e70bba09b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:34:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:20:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-66-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-66.ec2.internal uid: 803f4272-cff7-4491-86bc-e441020fc7d8 resourceVersion: "166526" uid: db0268f6-d073-4724-990d-6b5d8a8ce1df spec: sourcePod: network-check-source-6f78d59f99-fjxrl targetEndpoint: a8b9f89d97ff445a58c24085272709e4-47e4164e70bba09b.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T00:26:33Z" message: 'load-balancer-api-internal: tcp connection to a8b9f89d97ff445a58c24085272709e4-47e4164e70bba09b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 18.899801ms message: 'load-balancer-api-internal: tcp connection to a8b9f89d97ff445a58c24085272709e4-47e4164e70bba09b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:38:33Z" - latency: 6.865348ms message: 'load-balancer-api-internal: resolved host name a8b9f89d97ff445a58c24085272709e4-47e4164e70bba09b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:38:33Z" - latency: 18.946425ms message: 'load-balancer-api-internal: tcp connection to a8b9f89d97ff445a58c24085272709e4-47e4164e70bba09b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:37:33Z" - latency: 7.467649ms message: 'load-balancer-api-internal: resolved host name a8b9f89d97ff445a58c24085272709e4-47e4164e70bba09b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:37:33Z" - latency: 17.84288ms message: 'load-balancer-api-internal: tcp connection to a8b9f89d97ff445a58c24085272709e4-47e4164e70bba09b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:36:33Z" - latency: 7.233645ms message: 'load-balancer-api-internal: resolved host name a8b9f89d97ff445a58c24085272709e4-47e4164e70bba09b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:36:33Z" - latency: 19.168123ms message: 'load-balancer-api-internal: tcp connection to a8b9f89d97ff445a58c24085272709e4-47e4164e70bba09b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:35:33Z" - latency: 7.166928ms message: 'load-balancer-api-internal: resolved host name a8b9f89d97ff445a58c24085272709e4-47e4164e70bba09b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:35:33Z" - latency: 37.581149ms message: 'load-balancer-api-internal: tcp connection to a8b9f89d97ff445a58c24085272709e4-47e4164e70bba09b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:34:33Z" - latency: 10.575968ms message: 'load-balancer-api-internal: resolved host name a8b9f89d97ff445a58c24085272709e4-47e4164e70bba09b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:34:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:20:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-66-to-network-check-target-ip-10-0-128-253 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-66.ec2.internal uid: 803f4272-cff7-4491-86bc-e441020fc7d8 resourceVersion: "165055" uid: f079d39a-338b-46c7-8087-9e2731e91fed spec: sourcePod: network-check-source-6f78d59f99-fjxrl targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-31T00:27:33Z" message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.266817ms message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:37:33Z" - latency: 2.124052ms message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:36:33Z" - latency: 2.495891ms message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:35:33Z" - latency: 2.330978ms message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:34:33Z" - latency: 2.24128ms message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:33:33Z" - latency: 2.172619ms message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:32:33Z" - latency: 1.909205ms message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:31:33Z" - latency: 2.190975ms message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:30:33Z" - latency: 2.023769ms message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:29:33Z" - latency: 2.098172ms message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:28:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:20:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-66-to-network-check-target-ip-10-0-129-199 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-66.ec2.internal uid: 803f4272-cff7-4491-86bc-e441020fc7d8 resourceVersion: "165056" uid: 00a33672-598c-4416-830f-36ae1dfad3bf spec: sourcePod: network-check-source-6f78d59f99-fjxrl targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-31T00:27:33Z" message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.181713ms message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:37:33Z" - latency: 1.9183ms message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:36:33Z" - latency: 1.941832ms message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:35:33Z" - latency: 2.040627ms message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:34:33Z" - latency: 2.072095ms message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:33:33Z" - latency: 2.110214ms message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:32:33Z" - latency: 2.260247ms message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:31:33Z" - latency: 2.135641ms message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:30:33Z" - latency: 1.671065ms message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:29:33Z" - latency: 1.998077ms message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:28:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:20:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-66-to-network-check-target-ip-10-0-132-66 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-66.ec2.internal uid: 803f4272-cff7-4491-86bc-e441020fc7d8 resourceVersion: "165054" uid: cba82532-8244-4064-8de2-285abc7a6e1f spec: sourcePod: network-check-source-6f78d59f99-fjxrl targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-31T00:27:33Z" message: 'network-check-target-ip-10-0-132-66: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.023992ms message: 'network-check-target-ip-10-0-132-66: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:37:33Z" - latency: 778.46µs message: 'network-check-target-ip-10-0-132-66: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:36:33Z" - latency: 1.507826ms message: 'network-check-target-ip-10-0-132-66: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:35:33Z" - latency: 873.597µs message: 'network-check-target-ip-10-0-132-66: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:34:33Z" - latency: 798.424µs message: 'network-check-target-ip-10-0-132-66: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:33:33Z" - latency: 786.677µs message: 'network-check-target-ip-10-0-132-66: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:32:33Z" - latency: 875.447µs message: 'network-check-target-ip-10-0-132-66: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:31:33Z" - latency: 985.976µs message: 'network-check-target-ip-10-0-132-66: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:30:33Z" - latency: 1.368736ms message: 'network-check-target-ip-10-0-132-66: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:29:33Z" - latency: 903.749µs message: 'network-check-target-ip-10-0-132-66: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:28:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:20:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-66-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-66.ec2.internal uid: 803f4272-cff7-4491-86bc-e441020fc7d8 resourceVersion: "166524" uid: 313b45e5-549f-41b7-a376-65565db226ae spec: sourcePod: network-check-source-6f78d59f99-fjxrl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-31T00:26:33Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 935.386µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:38:33Z" - latency: 1.669895ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T01:38:33Z" - latency: 1.228417ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:37:33Z" - latency: 1.914795ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T01:37:33Z" - latency: 920.358µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:36:33Z" - latency: 2.067516ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T01:36:33Z" - latency: 961.402µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:35:33Z" - latency: 1.479977ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T01:35:33Z" - latency: 1.103608ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:34:33Z" - latency: 1.992975ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T01:34:33Z" kind: List metadata: resourceVersion: ""