apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T12:35:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-250-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-250.ec2.internal uid: 7ac66b63-df83-4dd2-8552-f6812b67a1f0 resourceVersion: "19552" uid: ab63998b-9aa1-46fd-912d-921fd3b2a72e spec: sourcePod: network-check-source-685456655f-bvfvx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-10T12:42:13Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 990.569µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:56:13Z" - latency: 843.98µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:55:13Z" - latency: 1.061955ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:54:13Z" - latency: 1.236423ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:53:13Z" - latency: 964.272µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:52:13Z" - latency: 899.771µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:51:13Z" - latency: 1.00149ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:50:13Z" - latency: 993.343µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:49:13Z" - latency: 981.519µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:48:13Z" - latency: 943.373µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:47:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T12:35:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-250-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-250.ec2.internal uid: 7ac66b63-df83-4dd2-8552-f6812b67a1f0 resourceVersion: "20898" uid: 3d922488-cb0f-493e-b63b-dc6105026dfc spec: sourcePod: network-check-source-685456655f-bvfvx targetEndpoint: aee2ef19778f74b31879244f3fe4ca62-527ef3e29452b6c7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-10T12:41:13Z" message: 'load-balancer-api-external: tcp connection to aee2ef19778f74b31879244f3fe4ca62-527ef3e29452b6c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.498192ms message: 'load-balancer-api-external: tcp connection to aee2ef19778f74b31879244f3fe4ca62-527ef3e29452b6c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:59:13Z" - latency: 10.109643ms message: 'load-balancer-api-external: resolved host name aee2ef19778f74b31879244f3fe4ca62-527ef3e29452b6c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:59:13Z" - latency: 5.297543ms message: 'load-balancer-api-external: tcp connection to aee2ef19778f74b31879244f3fe4ca62-527ef3e29452b6c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:58:13Z" - latency: 7.496323ms message: 'load-balancer-api-external: resolved host name aee2ef19778f74b31879244f3fe4ca62-527ef3e29452b6c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:58:13Z" - latency: 4.644601ms message: 'load-balancer-api-external: tcp connection to aee2ef19778f74b31879244f3fe4ca62-527ef3e29452b6c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:57:13Z" - latency: 11.776355ms message: 'load-balancer-api-external: resolved host name aee2ef19778f74b31879244f3fe4ca62-527ef3e29452b6c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:57:13Z" - latency: 5.562252ms message: 'load-balancer-api-external: tcp connection to aee2ef19778f74b31879244f3fe4ca62-527ef3e29452b6c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:56:13Z" - latency: 8.055453ms message: 'load-balancer-api-external: resolved host name aee2ef19778f74b31879244f3fe4ca62-527ef3e29452b6c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:56:13Z" - latency: 5.088533ms message: 'load-balancer-api-external: tcp connection to aee2ef19778f74b31879244f3fe4ca62-527ef3e29452b6c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:55:13Z" - latency: 8.470328ms message: 'load-balancer-api-external: resolved host name aee2ef19778f74b31879244f3fe4ca62-527ef3e29452b6c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:55:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T12:35:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-250-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-250.ec2.internal uid: 7ac66b63-df83-4dd2-8552-f6812b67a1f0 resourceVersion: "20899" uid: 05895ad3-35d5-4ce8-a1b4-efbb6150c8fd spec: sourcePod: network-check-source-685456655f-bvfvx targetEndpoint: aee2ef19778f74b31879244f3fe4ca62-527ef3e29452b6c7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-10T12:41:13Z" message: 'load-balancer-api-internal: tcp connection to aee2ef19778f74b31879244f3fe4ca62-527ef3e29452b6c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.609217ms message: 'load-balancer-api-internal: tcp connection to aee2ef19778f74b31879244f3fe4ca62-527ef3e29452b6c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:59:13Z" - latency: 10.191507ms message: 'load-balancer-api-internal: resolved host name aee2ef19778f74b31879244f3fe4ca62-527ef3e29452b6c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:59:13Z" - latency: 4.678695ms message: 'load-balancer-api-internal: tcp connection to aee2ef19778f74b31879244f3fe4ca62-527ef3e29452b6c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:58:13Z" - latency: 7.59315ms message: 'load-balancer-api-internal: resolved host name aee2ef19778f74b31879244f3fe4ca62-527ef3e29452b6c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:58:13Z" - latency: 4.266278ms message: 'load-balancer-api-internal: tcp connection to aee2ef19778f74b31879244f3fe4ca62-527ef3e29452b6c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:57:13Z" - latency: 11.853207ms message: 'load-balancer-api-internal: resolved host name aee2ef19778f74b31879244f3fe4ca62-527ef3e29452b6c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:57:13Z" - latency: 5.550773ms message: 'load-balancer-api-internal: tcp connection to aee2ef19778f74b31879244f3fe4ca62-527ef3e29452b6c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:56:13Z" - latency: 8.124242ms message: 'load-balancer-api-internal: resolved host name aee2ef19778f74b31879244f3fe4ca62-527ef3e29452b6c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:56:13Z" - latency: 5.07208ms message: 'load-balancer-api-internal: tcp connection to aee2ef19778f74b31879244f3fe4ca62-527ef3e29452b6c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:55:13Z" - latency: 8.519425ms message: 'load-balancer-api-internal: resolved host name aee2ef19778f74b31879244f3fe4ca62-527ef3e29452b6c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:55:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T12:35:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-250-to-network-check-target-ip-10-0-135-250 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-250.ec2.internal uid: 7ac66b63-df83-4dd2-8552-f6812b67a1f0 resourceVersion: "19551" uid: 448ad1c2-6cf6-4f08-91b7-e1ae14f1675d spec: sourcePod: network-check-source-685456655f-bvfvx targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-10T12:42:13Z" message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 817.887µs message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:56:13Z" - latency: 836.209µs message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:55:13Z" - latency: 1.115357ms message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:54:13Z" - latency: 1.1098ms message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:53:13Z" - latency: 1.128982ms message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:52:13Z" - latency: 855.311µs message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:51:13Z" - latency: 871.372µs message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:50:13Z" - latency: 922.065µs message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:49:13Z" - latency: 1.069344ms message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:48:13Z" - latency: 844.036µs message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:47:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T12:35:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-250-to-network-check-target-ip-10-0-137-89 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-250.ec2.internal uid: 7ac66b63-df83-4dd2-8552-f6812b67a1f0 resourceVersion: "19549" uid: 5a73c476-cd0c-428f-855e-72a13381e8ac spec: sourcePod: network-check-source-685456655f-bvfvx targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-10T12:42:13Z" message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.94918ms message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:56:13Z" - latency: 2.119151ms message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:55:13Z" - latency: 2.307681ms message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:54:13Z" - latency: 2.534796ms message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:53:13Z" - latency: 2.191337ms message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:52:13Z" - latency: 2.237643ms message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:51:13Z" - latency: 2.156325ms message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:50:13Z" - latency: 2.34407ms message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:49:13Z" - latency: 2.165014ms message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:48:13Z" - latency: 2.107116ms message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:47:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T12:35:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-250-to-network-check-target-ip-10-0-140-13 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-250.ec2.internal uid: 7ac66b63-df83-4dd2-8552-f6812b67a1f0 resourceVersion: "19550" uid: 5e017ea4-91c5-44f4-a48a-8158becc96dd spec: sourcePod: network-check-source-685456655f-bvfvx targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-10T12:42:13Z" message: 'network-check-target-ip-10-0-140-13: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.500682ms message: 'network-check-target-ip-10-0-140-13: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:56:13Z" - latency: 2.027594ms message: 'network-check-target-ip-10-0-140-13: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:55:13Z" - latency: 2.8057ms message: 'network-check-target-ip-10-0-140-13: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:54:13Z" - latency: 2.243348ms message: 'network-check-target-ip-10-0-140-13: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:53:13Z" - latency: 2.265847ms message: 'network-check-target-ip-10-0-140-13: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:52:13Z" - latency: 2.785582ms message: 'network-check-target-ip-10-0-140-13: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:51:13Z" - latency: 2.121097ms message: 'network-check-target-ip-10-0-140-13: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:50:13Z" - latency: 2.346499ms message: 'network-check-target-ip-10-0-140-13: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:49:13Z" - latency: 2.294536ms message: 'network-check-target-ip-10-0-140-13: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:48:13Z" - latency: 2.257153ms message: 'network-check-target-ip-10-0-140-13: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:47:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T12:35:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-250-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-250.ec2.internal uid: 7ac66b63-df83-4dd2-8552-f6812b67a1f0 resourceVersion: "20897" uid: 7209aa8f-a403-4e87-9aea-e66f3faf0199 spec: sourcePod: network-check-source-685456655f-bvfvx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-10T12:41:13Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 815.749µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:59:13Z" - latency: 1.745916ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T12:59:13Z" - latency: 886.168µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:58:13Z" - latency: 1.633524ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T12:58:13Z" - latency: 1.652467ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:57:13Z" - latency: 2.521198ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T12:57:13Z" - latency: 804.951µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:56:13Z" - latency: 1.998632ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T12:56:13Z" - latency: 757.536µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:55:13Z" - latency: 1.627679ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T12:55:13Z" kind: List metadata: resourceVersion: ""