apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:30:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-237-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-237.ec2.internal uid: 451e43e3-8c54-40d4-aaee-e12cd451543a resourceVersion: "42484" uid: e4e1808b-58ec-498a-b7ad-b075e3ea2b71 spec: sourcePod: network-check-source-8894fc9bd-lks6f targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-24T21:37:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 754.937µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:19Z" - latency: 935.571µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:19Z" - latency: 859.274µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:19Z" - latency: 870.589µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:19Z" - latency: 1.475075ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:19Z" - latency: 1.097477ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:07:19Z" - latency: 909.529µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:06:19Z" - latency: 998.624µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:05:19Z" - latency: 1.220199ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:04:19Z" - latency: 732.582µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:03:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:30:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-237-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-237.ec2.internal uid: 451e43e3-8c54-40d4-aaee-e12cd451543a resourceVersion: "42486" uid: 9820fd06-b258-42df-b92a-42e3df7236e8 spec: sourcePod: network-check-source-8894fc9bd-lks6f targetEndpoint: a769b186e06034fedb5bd66e20fe3ec8-130367e137cccdba.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T21:36:19Z" message: 'load-balancer-api-external: tcp connection to a769b186e06034fedb5bd66e20fe3ec8-130367e137cccdba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.314429ms message: 'load-balancer-api-external: tcp connection to a769b186e06034fedb5bd66e20fe3ec8-130367e137cccdba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:19Z" - latency: 8.882678ms message: 'load-balancer-api-external: resolved host name a769b186e06034fedb5bd66e20fe3ec8-130367e137cccdba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:12:19Z" - latency: 4.507485ms message: 'load-balancer-api-external: tcp connection to a769b186e06034fedb5bd66e20fe3ec8-130367e137cccdba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:19Z" - latency: 8.600567ms message: 'load-balancer-api-external: resolved host name a769b186e06034fedb5bd66e20fe3ec8-130367e137cccdba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:11:19Z" - latency: 4.786884ms message: 'load-balancer-api-external: tcp connection to a769b186e06034fedb5bd66e20fe3ec8-130367e137cccdba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:19Z" - latency: 6.685883ms message: 'load-balancer-api-external: resolved host name a769b186e06034fedb5bd66e20fe3ec8-130367e137cccdba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:10:19Z" - latency: 4.388641ms message: 'load-balancer-api-external: tcp connection to a769b186e06034fedb5bd66e20fe3ec8-130367e137cccdba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:19Z" - latency: 9.314493ms message: 'load-balancer-api-external: resolved host name a769b186e06034fedb5bd66e20fe3ec8-130367e137cccdba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:09:19Z" - latency: 4.849152ms message: 'load-balancer-api-external: tcp connection to a769b186e06034fedb5bd66e20fe3ec8-130367e137cccdba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:19Z" - latency: 7.06449ms message: 'load-balancer-api-external: resolved host name a769b186e06034fedb5bd66e20fe3ec8-130367e137cccdba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:08:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:30:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-237-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-237.ec2.internal uid: 451e43e3-8c54-40d4-aaee-e12cd451543a resourceVersion: "42485" uid: 80e13d39-b4ca-4f8c-97e0-6c7cfe57e964 spec: sourcePod: network-check-source-8894fc9bd-lks6f targetEndpoint: a769b186e06034fedb5bd66e20fe3ec8-130367e137cccdba.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T21:36:19Z" message: 'load-balancer-api-internal: tcp connection to a769b186e06034fedb5bd66e20fe3ec8-130367e137cccdba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.368027ms message: 'load-balancer-api-internal: tcp connection to a769b186e06034fedb5bd66e20fe3ec8-130367e137cccdba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:19Z" - latency: 8.926832ms message: 'load-balancer-api-internal: resolved host name a769b186e06034fedb5bd66e20fe3ec8-130367e137cccdba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:12:19Z" - latency: 4.468687ms message: 'load-balancer-api-internal: tcp connection to a769b186e06034fedb5bd66e20fe3ec8-130367e137cccdba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:19Z" - latency: 8.623992ms message: 'load-balancer-api-internal: resolved host name a769b186e06034fedb5bd66e20fe3ec8-130367e137cccdba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:11:19Z" - latency: 4.857043ms message: 'load-balancer-api-internal: tcp connection to a769b186e06034fedb5bd66e20fe3ec8-130367e137cccdba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:19Z" - latency: 6.624631ms message: 'load-balancer-api-internal: resolved host name a769b186e06034fedb5bd66e20fe3ec8-130367e137cccdba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:10:19Z" - latency: 4.912658ms message: 'load-balancer-api-internal: tcp connection to a769b186e06034fedb5bd66e20fe3ec8-130367e137cccdba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:19Z" - latency: 9.261619ms message: 'load-balancer-api-internal: resolved host name a769b186e06034fedb5bd66e20fe3ec8-130367e137cccdba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:09:19Z" - latency: 4.849963ms message: 'load-balancer-api-internal: tcp connection to a769b186e06034fedb5bd66e20fe3ec8-130367e137cccdba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:19Z" - latency: 6.993602ms message: 'load-balancer-api-internal: resolved host name a769b186e06034fedb5bd66e20fe3ec8-130367e137cccdba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:08:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:30:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-237-to-network-check-target-ip-10-0-129-204 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-237.ec2.internal uid: 451e43e3-8c54-40d4-aaee-e12cd451543a resourceVersion: "42481" uid: 05a0e776-d6af-4ce3-88de-3ff42a98122f spec: sourcePod: network-check-source-8894fc9bd-lks6f targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:37:19Z" message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.923122ms message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:19Z" - latency: 1.873751ms message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:19Z" - latency: 1.731566ms message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:19Z" - latency: 2.033463ms message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:19Z" - latency: 1.775665ms message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:19Z" - latency: 1.845338ms message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:07:19Z" - latency: 1.607725ms message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:06:19Z" - latency: 1.789743ms message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:05:19Z" - latency: 1.910129ms message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:04:19Z" - latency: 1.864711ms message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:03:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:30:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-237-to-network-check-target-ip-10-0-131-237 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-237.ec2.internal uid: 451e43e3-8c54-40d4-aaee-e12cd451543a resourceVersion: "42480" uid: 252b0f66-aef7-418a-a188-4b54605ccad6 spec: sourcePod: network-check-source-8894fc9bd-lks6f targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:37:19Z" message: 'network-check-target-ip-10-0-131-237: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 901.557µs message: 'network-check-target-ip-10-0-131-237: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:19Z" - latency: 856.219µs message: 'network-check-target-ip-10-0-131-237: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:19Z" - latency: 772.581µs message: 'network-check-target-ip-10-0-131-237: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:19Z" - latency: 1.008397ms message: 'network-check-target-ip-10-0-131-237: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:19Z" - latency: 844.806µs message: 'network-check-target-ip-10-0-131-237: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:19Z" - latency: 1.288558ms message: 'network-check-target-ip-10-0-131-237: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:07:19Z" - latency: 991.018µs message: 'network-check-target-ip-10-0-131-237: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:06:19Z" - latency: 920.351µs message: 'network-check-target-ip-10-0-131-237: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:05:19Z" - latency: 1.461843ms message: 'network-check-target-ip-10-0-131-237: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:04:19Z" - latency: 778.392µs message: 'network-check-target-ip-10-0-131-237: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:03:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:30:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-237-to-network-check-target-ip-10-0-133-73 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-237.ec2.internal uid: 451e43e3-8c54-40d4-aaee-e12cd451543a resourceVersion: "42482" uid: aa81fd08-60e1-4d6d-b086-7ac898940413 spec: sourcePod: network-check-source-8894fc9bd-lks6f targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:37:19Z" message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.502882ms message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:19Z" - latency: 2.144239ms message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:19Z" - latency: 2.235059ms message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:19Z" - latency: 2.133035ms message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:19Z" - latency: 2.269595ms message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:19Z" - latency: 2.076989ms message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:07:19Z" - latency: 2.08272ms message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:06:19Z" - latency: 2.269654ms message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:05:19Z" - latency: 2.175483ms message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:04:19Z" - latency: 2.008567ms message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:03:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:30:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-237-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-237.ec2.internal uid: 451e43e3-8c54-40d4-aaee-e12cd451543a resourceVersion: "42483" uid: b7b286b2-3129-4d5b-8176-3c8529c49da9 spec: sourcePod: network-check-source-8894fc9bd-lks6f targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-24T21:36:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 802.051µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:19Z" - latency: 2.530007ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:12:19Z" - latency: 774.889µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:19Z" - latency: 2.210039ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:11:19Z" - latency: 938.112µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:19Z" - latency: 1.725963ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:10:19Z" - latency: 973.385µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:19Z" - latency: 2.066018ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:09:19Z" - latency: 839.459µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:19Z" - latency: 1.665812ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:08:19Z" kind: List metadata: resourceVersion: ""