apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T01:06:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-251-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-251.ec2.internal uid: 0c9056d0-a4d5-47a6-b373-b5b4ecb01733 resourceVersion: "30013" uid: 8aece8c8-fbfc-43f8-a075-299786791b76 spec: sourcePod: network-check-source-869dcfcdcd-4454z targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T01:13:53Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.076049ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:20:53Z" - latency: 910.702µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:19:53Z" - latency: 1.253931ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:18:53Z" - latency: 910.79µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:17:53Z" - latency: 1.43257ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:16:53Z" - latency: 1.11711ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:15:53Z" - latency: 1.143438ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:14:53Z" - latency: 854.879µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:13:53Z" - latency: 1.081558ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:12:53Z" - latency: 966.765µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:11:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T01:06:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-251-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-251.ec2.internal uid: 0c9056d0-a4d5-47a6-b373-b5b4ecb01733 resourceVersion: "33078" uid: d7caffc0-b16d-40fb-badc-808a214cee67 spec: sourcePod: network-check-source-869dcfcdcd-4454z targetEndpoint: a90f9bf95551a4732b488f4792893ea6-4c730420ca543ca8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T01:12:53Z" message: 'load-balancer-api-external: tcp connection to a90f9bf95551a4732b488f4792893ea6-4c730420ca543ca8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.685484ms message: 'load-balancer-api-external: tcp connection to a90f9bf95551a4732b488f4792893ea6-4c730420ca543ca8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:24:53Z" - latency: 6.591093ms message: 'load-balancer-api-external: resolved host name a90f9bf95551a4732b488f4792893ea6-4c730420ca543ca8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T01:24:53Z" - latency: 4.250862ms message: 'load-balancer-api-external: tcp connection to a90f9bf95551a4732b488f4792893ea6-4c730420ca543ca8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:23:53Z" - latency: 8.638969ms message: 'load-balancer-api-external: resolved host name a90f9bf95551a4732b488f4792893ea6-4c730420ca543ca8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T01:23:53Z" - latency: 3.661163ms message: 'load-balancer-api-external: tcp connection to a90f9bf95551a4732b488f4792893ea6-4c730420ca543ca8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:22:53Z" - latency: 7.291422ms message: 'load-balancer-api-external: resolved host name a90f9bf95551a4732b488f4792893ea6-4c730420ca543ca8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T01:22:53Z" - latency: 5.190522ms message: 'load-balancer-api-external: tcp connection to a90f9bf95551a4732b488f4792893ea6-4c730420ca543ca8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:21:53Z" - latency: 10.846231ms message: 'load-balancer-api-external: resolved host name a90f9bf95551a4732b488f4792893ea6-4c730420ca543ca8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T01:21:53Z" - latency: 4.995133ms message: 'load-balancer-api-external: tcp connection to a90f9bf95551a4732b488f4792893ea6-4c730420ca543ca8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:20:53Z" - latency: 6.991734ms message: 'load-balancer-api-external: resolved host name a90f9bf95551a4732b488f4792893ea6-4c730420ca543ca8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T01:20:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T01:06:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-251-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-251.ec2.internal uid: 0c9056d0-a4d5-47a6-b373-b5b4ecb01733 resourceVersion: "33077" uid: cb8b3db7-fe50-4e51-8ead-cb0111279e03 spec: sourcePod: network-check-source-869dcfcdcd-4454z targetEndpoint: a90f9bf95551a4732b488f4792893ea6-4c730420ca543ca8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T01:12:53Z" message: 'load-balancer-api-internal: tcp connection to a90f9bf95551a4732b488f4792893ea6-4c730420ca543ca8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.211243ms message: 'load-balancer-api-internal: tcp connection to a90f9bf95551a4732b488f4792893ea6-4c730420ca543ca8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:24:53Z" - latency: 6.48378ms message: 'load-balancer-api-internal: resolved host name a90f9bf95551a4732b488f4792893ea6-4c730420ca543ca8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T01:24:53Z" - latency: 4.826864ms message: 'load-balancer-api-internal: tcp connection to a90f9bf95551a4732b488f4792893ea6-4c730420ca543ca8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:23:53Z" - latency: 8.522176ms message: 'load-balancer-api-internal: resolved host name a90f9bf95551a4732b488f4792893ea6-4c730420ca543ca8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T01:23:53Z" - latency: 4.437609ms message: 'load-balancer-api-internal: tcp connection to a90f9bf95551a4732b488f4792893ea6-4c730420ca543ca8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:22:53Z" - latency: 7.35665ms message: 'load-balancer-api-internal: resolved host name a90f9bf95551a4732b488f4792893ea6-4c730420ca543ca8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T01:22:53Z" - latency: 5.15625ms message: 'load-balancer-api-internal: tcp connection to a90f9bf95551a4732b488f4792893ea6-4c730420ca543ca8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:21:53Z" - latency: 10.868999ms message: 'load-balancer-api-internal: resolved host name a90f9bf95551a4732b488f4792893ea6-4c730420ca543ca8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T01:21:53Z" - latency: 5.039919ms message: 'load-balancer-api-internal: tcp connection to a90f9bf95551a4732b488f4792893ea6-4c730420ca543ca8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:20:53Z" - latency: 7.010732ms message: 'load-balancer-api-internal: resolved host name a90f9bf95551a4732b488f4792893ea6-4c730420ca543ca8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T01:20:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T01:06:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-251-to-network-check-target-ip-10-0-128-136 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-251.ec2.internal uid: 0c9056d0-a4d5-47a6-b373-b5b4ecb01733 resourceVersion: "30012" uid: 6ecee84c-ac42-4a4d-8733-32db1dc45917 spec: sourcePod: network-check-source-869dcfcdcd-4454z targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T01:13:53Z" message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.556928ms message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:20:53Z" - latency: 2.404282ms message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:19:53Z" - latency: 2.4502ms message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:18:53Z" - latency: 2.450149ms message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:17:53Z" - latency: 2.279911ms message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:16:53Z" - latency: 2.898189ms message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:15:53Z" - latency: 2.219997ms message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:14:53Z" - latency: 2.097742ms message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:13:53Z" - latency: 2.371639ms message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:12:53Z" - latency: 2.317103ms message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:11:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T01:06:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-251-to-network-check-target-ip-10-0-138-251 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-251.ec2.internal uid: 0c9056d0-a4d5-47a6-b373-b5b4ecb01733 resourceVersion: "30010" uid: 22b8f2be-64e8-43a9-af35-e1ed3fdce26d spec: sourcePod: network-check-source-869dcfcdcd-4454z targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T01:13:53Z" message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.39348ms message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:20:53Z" - latency: 920.451µs message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:19:53Z" - latency: 987.639µs message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:18:53Z" - latency: 909.675µs message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:17:53Z" - latency: 789.718µs message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:16:53Z" - latency: 1.466924ms message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:15:53Z" - latency: 1.196874ms message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:14:53Z" - latency: 1.378496ms message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:13:53Z" - latency: 963.686µs message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:12:53Z" - latency: 877.52µs message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:11:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T01:06:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-251-to-network-check-target-ip-10-0-139-171 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-251.ec2.internal uid: 0c9056d0-a4d5-47a6-b373-b5b4ecb01733 resourceVersion: "30011" uid: 8fe3eabd-6b77-44aa-82da-b48aa09c8c87 spec: sourcePod: network-check-source-869dcfcdcd-4454z targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T01:13:53Z" message: 'network-check-target-ip-10-0-139-171: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.398507ms message: 'network-check-target-ip-10-0-139-171: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:20:53Z" - latency: 1.97078ms message: 'network-check-target-ip-10-0-139-171: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:19:53Z" - latency: 1.906248ms message: 'network-check-target-ip-10-0-139-171: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:18:53Z" - latency: 2.042225ms message: 'network-check-target-ip-10-0-139-171: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:17:53Z" - latency: 1.877232ms message: 'network-check-target-ip-10-0-139-171: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:16:53Z" - latency: 2.228186ms message: 'network-check-target-ip-10-0-139-171: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:15:53Z" - latency: 2.189838ms message: 'network-check-target-ip-10-0-139-171: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:14:53Z" - latency: 2.034882ms message: 'network-check-target-ip-10-0-139-171: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:13:53Z" - latency: 2.254393ms message: 'network-check-target-ip-10-0-139-171: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:12:53Z" - latency: 2.17733ms message: 'network-check-target-ip-10-0-139-171: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:11:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T01:06:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-251-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-251.ec2.internal uid: 0c9056d0-a4d5-47a6-b373-b5b4ecb01733 resourceVersion: "33076" uid: 1a42ddeb-4e39-4592-a55d-53d9b5fcd936 spec: sourcePod: network-check-source-869dcfcdcd-4454z targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T01:12:53Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 904.257µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:24:53Z" - latency: 1.568368ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T01:24:53Z" - latency: 723.631µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:23:53Z" - latency: 1.719914ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T01:23:53Z" - latency: 1.179551ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:22:53Z" - latency: 1.682609ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T01:22:53Z" - latency: 818.238µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:21:53Z" - latency: 1.687409ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T01:21:53Z" - latency: 810.695µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T01:20:53Z" - latency: 2.084895ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T01:20:53Z" kind: List metadata: resourceVersion: ""