apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:24:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-178-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-178.ec2.internal uid: 57812c6a-37af-4352-ab45-1cc1801bbfb6 resourceVersion: "48344" uid: bf15cfe0-cc5a-4ee3-9137-f9e349c5fcf3 spec: sourcePod: network-check-source-989f8b8dc-26r5g targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T18:31:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.205317ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:52:51Z" - latency: 812.059µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:51:51Z" - latency: 982.578µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:50:51Z" - latency: 940.803µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:49:51Z" - latency: 1.04667ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:48:51Z" - latency: 1.671804ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:47:51Z" - latency: 1.140876ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:46:51Z" - latency: 1.289569ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:45:51Z" - latency: 1.096396ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:44:51Z" - latency: 827.643µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:43:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:24:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-178-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-178.ec2.internal uid: 57812c6a-37af-4352-ab45-1cc1801bbfb6 resourceVersion: "50444" uid: c0bb4b51-0cc1-47d2-8822-6d87cc4ae0e9 spec: sourcePod: network-check-source-989f8b8dc-26r5g targetEndpoint: a2152f27c292247a99e5a7e2156dd8ac-b7ed1d66e55ca43c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T18:30:51Z" message: 'load-balancer-api-external: tcp connection to a2152f27c292247a99e5a7e2156dd8ac-b7ed1d66e55ca43c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.867765ms message: 'load-balancer-api-external: tcp connection to a2152f27c292247a99e5a7e2156dd8ac-b7ed1d66e55ca43c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:54:51Z" - latency: 7.711587ms message: 'load-balancer-api-external: resolved host name a2152f27c292247a99e5a7e2156dd8ac-b7ed1d66e55ca43c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:54:51Z" - latency: 4.317587ms message: 'load-balancer-api-external: tcp connection to a2152f27c292247a99e5a7e2156dd8ac-b7ed1d66e55ca43c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:53:51Z" - latency: 7.30368ms message: 'load-balancer-api-external: resolved host name a2152f27c292247a99e5a7e2156dd8ac-b7ed1d66e55ca43c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:53:51Z" - latency: 3.732914ms message: 'load-balancer-api-external: tcp connection to a2152f27c292247a99e5a7e2156dd8ac-b7ed1d66e55ca43c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:52:51Z" - latency: 7.684854ms message: 'load-balancer-api-external: resolved host name a2152f27c292247a99e5a7e2156dd8ac-b7ed1d66e55ca43c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:52:51Z" - latency: 3.586059ms message: 'load-balancer-api-external: tcp connection to a2152f27c292247a99e5a7e2156dd8ac-b7ed1d66e55ca43c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:51:51Z" - latency: 7.096448ms message: 'load-balancer-api-external: resolved host name a2152f27c292247a99e5a7e2156dd8ac-b7ed1d66e55ca43c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:51:51Z" - latency: 6.362697ms message: 'load-balancer-api-external: tcp connection to a2152f27c292247a99e5a7e2156dd8ac-b7ed1d66e55ca43c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:50:51Z" - latency: 6.543858ms message: 'load-balancer-api-external: resolved host name a2152f27c292247a99e5a7e2156dd8ac-b7ed1d66e55ca43c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:50:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:24:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-178-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-178.ec2.internal uid: 57812c6a-37af-4352-ab45-1cc1801bbfb6 resourceVersion: "50445" uid: e416a416-36aa-48c4-bd0a-54faa5ddd13d spec: sourcePod: network-check-source-989f8b8dc-26r5g targetEndpoint: a2152f27c292247a99e5a7e2156dd8ac-b7ed1d66e55ca43c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T18:30:51Z" message: 'load-balancer-api-internal: tcp connection to a2152f27c292247a99e5a7e2156dd8ac-b7ed1d66e55ca43c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.386016ms message: 'load-balancer-api-internal: tcp connection to a2152f27c292247a99e5a7e2156dd8ac-b7ed1d66e55ca43c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:54:51Z" - latency: 7.796983ms message: 'load-balancer-api-internal: resolved host name a2152f27c292247a99e5a7e2156dd8ac-b7ed1d66e55ca43c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:54:51Z" - latency: 4.614692ms message: 'load-balancer-api-internal: tcp connection to a2152f27c292247a99e5a7e2156dd8ac-b7ed1d66e55ca43c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:53:51Z" - latency: 7.411506ms message: 'load-balancer-api-internal: resolved host name a2152f27c292247a99e5a7e2156dd8ac-b7ed1d66e55ca43c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:53:51Z" - latency: 4.269926ms message: 'load-balancer-api-internal: tcp connection to a2152f27c292247a99e5a7e2156dd8ac-b7ed1d66e55ca43c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:52:51Z" - latency: 7.796154ms message: 'load-balancer-api-internal: resolved host name a2152f27c292247a99e5a7e2156dd8ac-b7ed1d66e55ca43c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:52:51Z" - latency: 3.563552ms message: 'load-balancer-api-internal: tcp connection to a2152f27c292247a99e5a7e2156dd8ac-b7ed1d66e55ca43c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:51:51Z" - latency: 7.164882ms message: 'load-balancer-api-internal: resolved host name a2152f27c292247a99e5a7e2156dd8ac-b7ed1d66e55ca43c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:51:51Z" - latency: 5.91886ms message: 'load-balancer-api-internal: tcp connection to a2152f27c292247a99e5a7e2156dd8ac-b7ed1d66e55ca43c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:50:51Z" - latency: 6.593276ms message: 'load-balancer-api-internal: resolved host name a2152f27c292247a99e5a7e2156dd8ac-b7ed1d66e55ca43c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:50:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:24:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-178-to-network-check-target-ip-10-0-131-106 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-178.ec2.internal uid: 57812c6a-37af-4352-ab45-1cc1801bbfb6 resourceVersion: "48343" uid: 579445b1-78ed-4596-ae62-721e6d039eaa spec: sourcePod: network-check-source-989f8b8dc-26r5g targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T18:31:51Z" message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.245809ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:52:51Z" - latency: 1.973273ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:51:51Z" - latency: 2.223682ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:50:51Z" - latency: 2.15495ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:49:51Z" - latency: 2.467832ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:48:51Z" - latency: 2.077709ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:47:51Z" - latency: 2.079646ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:46:51Z" - latency: 2.514319ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:45:51Z" - latency: 2.082895ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:44:51Z" - latency: 1.96848ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:43:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:24:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-178-to-network-check-target-ip-10-0-134-97 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-178.ec2.internal uid: 57812c6a-37af-4352-ab45-1cc1801bbfb6 resourceVersion: "48342" uid: 5aa37258-c56b-4534-9329-18153d402b81 spec: sourcePod: network-check-source-989f8b8dc-26r5g targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T18:31:51Z" message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.032582ms message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:52:51Z" - latency: 1.90962ms message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:51:51Z" - latency: 1.814243ms message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:50:51Z" - latency: 1.772477ms message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:49:51Z" - latency: 2.192821ms message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:48:51Z" - latency: 1.496436ms message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:47:51Z" - latency: 2.258033ms message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:46:51Z" - latency: 1.880261ms message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:45:51Z" - latency: 1.953807ms message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:44:51Z" - latency: 1.602246ms message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:43:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:24:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-178-to-network-check-target-ip-10-0-136-178 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-178.ec2.internal uid: 57812c6a-37af-4352-ab45-1cc1801bbfb6 resourceVersion: "48341" uid: d3ea20c9-66f5-430f-a988-5d73eeccb923 spec: sourcePod: network-check-source-989f8b8dc-26r5g targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T18:31:51Z" message: 'network-check-target-ip-10-0-136-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.009359ms message: 'network-check-target-ip-10-0-136-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:52:51Z" - latency: 1.039304ms message: 'network-check-target-ip-10-0-136-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:51:51Z" - latency: 764.931µs message: 'network-check-target-ip-10-0-136-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:50:51Z" - latency: 1.383248ms message: 'network-check-target-ip-10-0-136-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:49:51Z" - latency: 932.379µs message: 'network-check-target-ip-10-0-136-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:48:51Z" - latency: 907.932µs message: 'network-check-target-ip-10-0-136-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:47:51Z" - latency: 1.481001ms message: 'network-check-target-ip-10-0-136-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:46:51Z" - latency: 811.51µs message: 'network-check-target-ip-10-0-136-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:45:51Z" - latency: 770.689µs message: 'network-check-target-ip-10-0-136-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:44:51Z" - latency: 798.979µs message: 'network-check-target-ip-10-0-136-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:43:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:24:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-178-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-178.ec2.internal uid: 57812c6a-37af-4352-ab45-1cc1801bbfb6 resourceVersion: "50443" uid: 7a9ccb8e-e579-43a3-b58b-3f3c427d6c4c spec: sourcePod: network-check-source-989f8b8dc-26r5g targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T18:30:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 847.558µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:54:51Z" - latency: 1.820207ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T18:54:51Z" - latency: 1.019556ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:53:51Z" - latency: 2.20932ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T18:53:51Z" - latency: 1.348634ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:52:51Z" - latency: 1.903027ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T18:52:51Z" - latency: 991.23µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:51:51Z" - latency: 1.812456ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T18:51:51Z" - latency: 1.078797ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:50:51Z" - latency: 1.7708ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T18:50:51Z" kind: List metadata: resourceVersion: ""