apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:36:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-231-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-231.ec2.internal uid: 12c68359-73a7-48cd-af9a-e25b58c4f6f9 resourceVersion: "17856" uid: 1a17453d-84c9-4f7b-a303-2ee1a03b773e spec: sourcePod: network-check-source-8894fc9bd-7rh2n targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-23T16:43:36Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.178001ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:50:36Z" - latency: 1.249207ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:49:36Z" - latency: 923.325µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:48:36Z" - latency: 1.400059ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:47:36Z" - latency: 945.751µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:46:36Z" - latency: 1.06858ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:45:36Z" - latency: 1.03805ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:44:36Z" - latency: 946.022µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:43:36Z" - latency: 902.788µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:42:36Z" - latency: 906.294µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:41:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:36:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-231-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-231.ec2.internal uid: 12c68359-73a7-48cd-af9a-e25b58c4f6f9 resourceVersion: "16923" uid: 329193ab-3027-4bc7-aab8-df6c77559ee9 spec: sourcePod: network-check-source-8894fc9bd-7rh2n targetEndpoint: a81c8615910154b168d66b503666a1de-6c244a29997de293.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T16:42:36Z" message: 'load-balancer-api-external: tcp connection to a81c8615910154b168d66b503666a1de-6c244a29997de293.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.444038ms message: 'load-balancer-api-external: tcp connection to a81c8615910154b168d66b503666a1de-6c244a29997de293.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:48:36Z" - latency: 7.392046ms message: 'load-balancer-api-external: resolved host name a81c8615910154b168d66b503666a1de-6c244a29997de293.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T16:48:36Z" - latency: 4.679367ms message: 'load-balancer-api-external: tcp connection to a81c8615910154b168d66b503666a1de-6c244a29997de293.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:47:36Z" - latency: 10.32943ms message: 'load-balancer-api-external: resolved host name a81c8615910154b168d66b503666a1de-6c244a29997de293.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T16:47:36Z" - latency: 7.928721ms message: 'load-balancer-api-external: tcp connection to a81c8615910154b168d66b503666a1de-6c244a29997de293.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:46:36Z" - latency: 7.61209ms message: 'load-balancer-api-external: resolved host name a81c8615910154b168d66b503666a1de-6c244a29997de293.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T16:46:36Z" - latency: 4.959464ms message: 'load-balancer-api-external: tcp connection to a81c8615910154b168d66b503666a1de-6c244a29997de293.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:45:36Z" - latency: 8.329162ms message: 'load-balancer-api-external: resolved host name a81c8615910154b168d66b503666a1de-6c244a29997de293.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T16:45:36Z" - latency: 5.072557ms message: 'load-balancer-api-external: tcp connection to a81c8615910154b168d66b503666a1de-6c244a29997de293.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:44:36Z" - latency: 7.274883ms message: 'load-balancer-api-external: resolved host name a81c8615910154b168d66b503666a1de-6c244a29997de293.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T16:44:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:36:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-231-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-231.ec2.internal uid: 12c68359-73a7-48cd-af9a-e25b58c4f6f9 resourceVersion: "16922" uid: 3f04499c-4fa8-42bd-98f9-8ad7a8ee4403 spec: sourcePod: network-check-source-8894fc9bd-7rh2n targetEndpoint: a81c8615910154b168d66b503666a1de-6c244a29997de293.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T16:42:36Z" message: 'load-balancer-api-internal: tcp connection to a81c8615910154b168d66b503666a1de-6c244a29997de293.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.417352ms message: 'load-balancer-api-internal: tcp connection to a81c8615910154b168d66b503666a1de-6c244a29997de293.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:48:36Z" - latency: 7.479305ms message: 'load-balancer-api-internal: resolved host name a81c8615910154b168d66b503666a1de-6c244a29997de293.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T16:48:36Z" - latency: 4.943828ms message: 'load-balancer-api-internal: tcp connection to a81c8615910154b168d66b503666a1de-6c244a29997de293.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:47:36Z" - latency: 10.356916ms message: 'load-balancer-api-internal: resolved host name a81c8615910154b168d66b503666a1de-6c244a29997de293.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T16:47:36Z" - latency: 7.895794ms message: 'load-balancer-api-internal: tcp connection to a81c8615910154b168d66b503666a1de-6c244a29997de293.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:46:36Z" - latency: 7.672113ms message: 'load-balancer-api-internal: resolved host name a81c8615910154b168d66b503666a1de-6c244a29997de293.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T16:46:36Z" - latency: 4.928841ms message: 'load-balancer-api-internal: tcp connection to a81c8615910154b168d66b503666a1de-6c244a29997de293.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:45:36Z" - latency: 8.419656ms message: 'load-balancer-api-internal: resolved host name a81c8615910154b168d66b503666a1de-6c244a29997de293.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T16:45:36Z" - latency: 5.134929ms message: 'load-balancer-api-internal: tcp connection to a81c8615910154b168d66b503666a1de-6c244a29997de293.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:44:36Z" - latency: 7.327312ms message: 'load-balancer-api-internal: resolved host name a81c8615910154b168d66b503666a1de-6c244a29997de293.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T16:44:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:36:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-231-to-network-check-target-ip-10-0-133-231 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-231.ec2.internal uid: 12c68359-73a7-48cd-af9a-e25b58c4f6f9 resourceVersion: "17853" uid: 6b22d311-da3e-43aa-be26-f225c6ff9799 spec: sourcePod: network-check-source-8894fc9bd-7rh2n targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-23T16:43:36Z" message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.95524ms message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:50:36Z" - latency: 907.322µs message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:49:36Z" - latency: 1.123529ms message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:48:36Z" - latency: 1.191624ms message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:47:36Z" - latency: 1.467124ms message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:46:36Z" - latency: 788.085µs message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:45:36Z" - latency: 1.297127ms message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:44:36Z" - latency: 878.385µs message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:43:36Z" - latency: 982.987µs message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:42:36Z" - latency: 686.657µs message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:41:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:36:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-231-to-network-check-target-ip-10-0-137-14 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-231.ec2.internal uid: 12c68359-73a7-48cd-af9a-e25b58c4f6f9 resourceVersion: "17855" uid: 507d80c5-04a8-4bfd-b382-e9b3809c41a1 spec: sourcePod: network-check-source-8894fc9bd-7rh2n targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-23T16:43:36Z" message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.888874ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:50:36Z" - latency: 2.619352ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:49:36Z" - latency: 2.193242ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:48:36Z" - latency: 2.317631ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:47:36Z" - latency: 2.149ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:46:36Z" - latency: 2.121029ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:45:36Z" - latency: 2.266844ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:44:36Z" - latency: 2.253293ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:43:36Z" - latency: 2.834333ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:42:36Z" - latency: 2.27033ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:41:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:36:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-231-to-network-check-target-ip-10-0-142-4 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-231.ec2.internal uid: 12c68359-73a7-48cd-af9a-e25b58c4f6f9 resourceVersion: "17854" uid: c8d6a5c7-0f8e-44f0-82a9-896d8117fb6b spec: sourcePod: network-check-source-8894fc9bd-7rh2n targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-23T16:43:36Z" message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.846355ms message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:50:36Z" - latency: 2.438684ms message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:49:36Z" - latency: 1.945551ms message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:48:36Z" - latency: 2.11963ms message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:47:36Z" - latency: 2.270367ms message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:46:36Z" - latency: 1.982078ms message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:45:36Z" - latency: 2.223687ms message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:44:36Z" - latency: 2.352369ms message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:43:36Z" - latency: 2.181808ms message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:42:36Z" - latency: 2.309695ms message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:41:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:36:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-231-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-231.ec2.internal uid: 12c68359-73a7-48cd-af9a-e25b58c4f6f9 resourceVersion: "16920" uid: f7d3b366-ebca-4e53-af7d-48154f513ac8 spec: sourcePod: network-check-source-8894fc9bd-7rh2n targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-23T16:42:36Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 993.539µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:48:36Z" - latency: 1.675723ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T16:48:36Z" - latency: 815.346µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:47:36Z" - latency: 1.887913ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T16:47:36Z" - latency: 830.977µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:46:36Z" - latency: 1.725473ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T16:46:36Z" - latency: 918.575µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:45:36Z" - latency: 2.086977ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T16:45:36Z" - latency: 924.71µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:44:36Z" - latency: 1.52547ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T16:44:36Z" kind: List metadata: resourceVersion: ""