apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:34:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-92-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-92.us-west-1.compute.internal uid: bcbdf223-7cb5-4505-9678-acb5535d3e3b resourceVersion: "107982" uid: f051aa40-7f01-4bea-b3da-826b49d27fb2 spec: sourcePod: network-check-source-6f78d59f99-64b9m targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T21:41:44Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.69333ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:44:44Z" - latency: 1.225854ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:43:44Z" - latency: 1.179583ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:42:44Z" - latency: 983.196µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:41:44Z" - latency: 1.286299ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:40:44Z" - latency: 1.19171ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:39:44Z" - latency: 1.31757ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:38:44Z" - latency: 1.166697ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:37:44Z" - latency: 1.395121ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:36:44Z" - latency: 996.671µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:35:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:34:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-92-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-92.us-west-1.compute.internal uid: bcbdf223-7cb5-4505-9678-acb5535d3e3b resourceVersion: "109164" uid: 803b615a-ebb9-4e2f-9e5a-637c38c55a95 spec: sourcePod: network-check-source-6f78d59f99-64b9m targetEndpoint: a87acbcee0c914c0587855f827b89858-cda6e39977984c9a.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:40:44Z" message: 'load-balancer-api-external: tcp connection to a87acbcee0c914c0587855f827b89858-cda6e39977984c9a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.735538ms message: 'load-balancer-api-external: tcp connection to a87acbcee0c914c0587855f827b89858-cda6e39977984c9a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:46:44Z" - latency: 7.755835ms message: 'load-balancer-api-external: resolved host name a87acbcee0c914c0587855f827b89858-cda6e39977984c9a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:46:44Z" - latency: 3.387656018s message: 'load-balancer-api-external: tcp connection to a87acbcee0c914c0587855f827b89858-cda6e39977984c9a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:45:44Z" - latency: 6.452184ms message: 'load-balancer-api-external: resolved host name a87acbcee0c914c0587855f827b89858-cda6e39977984c9a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:45:44Z" - latency: 56.276917ms message: 'load-balancer-api-external: tcp connection to a87acbcee0c914c0587855f827b89858-cda6e39977984c9a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:44:44Z" - latency: 39.09456ms message: 'load-balancer-api-external: resolved host name a87acbcee0c914c0587855f827b89858-cda6e39977984c9a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:44:44Z" - latency: 56.090707ms message: 'load-balancer-api-external: tcp connection to a87acbcee0c914c0587855f827b89858-cda6e39977984c9a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:43:44Z" - latency: 5.939524ms message: 'load-balancer-api-external: resolved host name a87acbcee0c914c0587855f827b89858-cda6e39977984c9a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:43:44Z" - latency: 55.665828ms message: 'load-balancer-api-external: tcp connection to a87acbcee0c914c0587855f827b89858-cda6e39977984c9a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:42:44Z" - latency: 6.434216ms message: 'load-balancer-api-external: resolved host name a87acbcee0c914c0587855f827b89858-cda6e39977984c9a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:42:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:34:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-92-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-92.us-west-1.compute.internal uid: bcbdf223-7cb5-4505-9678-acb5535d3e3b resourceVersion: "109165" uid: 5876b58a-2ed2-4600-a762-88797c102e4f spec: sourcePod: network-check-source-6f78d59f99-64b9m targetEndpoint: a87acbcee0c914c0587855f827b89858-cda6e39977984c9a.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:40:44Z" message: 'load-balancer-api-internal: tcp connection to a87acbcee0c914c0587855f827b89858-cda6e39977984c9a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.704306ms message: 'load-balancer-api-internal: tcp connection to a87acbcee0c914c0587855f827b89858-cda6e39977984c9a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:46:44Z" - latency: 7.724835ms message: 'load-balancer-api-internal: resolved host name a87acbcee0c914c0587855f827b89858-cda6e39977984c9a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:46:44Z" - latency: 54.631096ms message: 'load-balancer-api-internal: tcp connection to a87acbcee0c914c0587855f827b89858-cda6e39977984c9a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:45:44Z" - latency: 6.441222ms message: 'load-balancer-api-internal: resolved host name a87acbcee0c914c0587855f827b89858-cda6e39977984c9a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:45:44Z" - latency: 56.870965ms message: 'load-balancer-api-internal: tcp connection to a87acbcee0c914c0587855f827b89858-cda6e39977984c9a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:44:44Z" - latency: 37.839063ms message: 'load-balancer-api-internal: resolved host name a87acbcee0c914c0587855f827b89858-cda6e39977984c9a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:44:44Z" - latency: 54.482215ms message: 'load-balancer-api-internal: tcp connection to a87acbcee0c914c0587855f827b89858-cda6e39977984c9a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:43:44Z" - latency: 5.882067ms message: 'load-balancer-api-internal: resolved host name a87acbcee0c914c0587855f827b89858-cda6e39977984c9a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:43:44Z" - latency: 55.986513ms message: 'load-balancer-api-internal: tcp connection to a87acbcee0c914c0587855f827b89858-cda6e39977984c9a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:42:44Z" - latency: 6.37196ms message: 'load-balancer-api-internal: resolved host name a87acbcee0c914c0587855f827b89858-cda6e39977984c9a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:42:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:34:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-92-to-network-check-target-ip-10-0-130-104 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-92.us-west-1.compute.internal uid: bcbdf223-7cb5-4505-9678-acb5535d3e3b resourceVersion: "108073" uid: 40779d2e-f83c-446a-8506-f329641f4ba5 spec: sourcePod: network-check-source-6f78d59f99-64b9m targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:41:52Z" message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.050881ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:44:52Z" - latency: 2.126007ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:43:52Z" - latency: 1.445006ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:42:52Z" - latency: 1.043428ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:41:52Z" - latency: 2.132053ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:40:52Z" - latency: 1.032202ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:39:52Z" - latency: 821.731µs message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:38:52Z" - latency: 2.097869ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:37:52Z" - latency: 2.204109ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:36:52Z" - latency: 2.208153ms message: 'network-check-target-ip-10-0-130-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:35:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:34:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-92-to-network-check-target-ip-10-0-132-92 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-92.us-west-1.compute.internal uid: bcbdf223-7cb5-4505-9678-acb5535d3e3b resourceVersion: "107980" uid: 5d84575a-50ca-433d-85c3-acef74269cf0 spec: sourcePod: network-check-source-6f78d59f99-64b9m targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:41:44Z" message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.857022ms message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:44:44Z" - latency: 1.343745ms message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:43:44Z" - latency: 1.077968ms message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:42:44Z" - latency: 1.169887ms message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:41:44Z" - latency: 1.58347ms message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:40:44Z" - latency: 1.35915ms message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:39:44Z" - latency: 950.078µs message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:38:44Z" - latency: 1.487664ms message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:37:44Z" - latency: 914.808µs message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:36:44Z" - latency: 1.227599ms message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:35:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:34:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-92-to-network-check-target-ip-10-0-135-39 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-92.us-west-1.compute.internal uid: bcbdf223-7cb5-4505-9678-acb5535d3e3b resourceVersion: "108051" uid: 220716f7-a515-454e-b760-f64e9d2368dc spec: sourcePod: network-check-source-6f78d59f99-64b9m targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:41:49Z" message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.79395ms message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:44:49Z" - latency: 2.191669ms message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:43:49Z" - latency: 970.463µs message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:42:49Z" - latency: 2.46511ms message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:41:49Z" - latency: 2.5745ms message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:40:49Z" - latency: 2.354573ms message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:39:49Z" - latency: 3.828559ms message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:38:49Z" - latency: 2.535566ms message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:37:49Z" - latency: 1.053411ms message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:36:49Z" - latency: 846.842µs message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:35:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:34:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-92-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-92.us-west-1.compute.internal uid: bcbdf223-7cb5-4505-9678-acb5535d3e3b resourceVersion: "109161" uid: 031043cb-028b-49c8-b559-6d727b87d314 spec: sourcePod: network-check-source-6f78d59f99-64b9m targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T21:40:44Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.000368ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:46:44Z" - latency: 1.920031ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:46:44Z" - latency: 2.149951ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:45:44Z" - latency: 1.986814ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:45:44Z" - latency: 10.811952ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:44:44Z" - latency: 12.352101ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:44:44Z" - latency: 784.084µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:43:44Z" - latency: 1.985245ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:43:44Z" - latency: 2.282387ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:42:44Z" - latency: 1.712159ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:42:44Z" kind: List metadata: resourceVersion: ""