apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T23:42:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-167-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-167.ec2.internal uid: 6c36ac42-d1bb-49c3-9ae3-d9341aa10a41 resourceVersion: "62086" uid: c02bbdd6-9318-4203-80eb-d5c93464b9be spec: sourcePod: network-check-source-869dcfcdcd-68xxd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-13T23:49:04Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 997.765µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:24:04Z" - latency: 1.082516ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:23:04Z" - latency: 1.123818ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:22:04Z" - latency: 1.192834ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:21:04Z" - latency: 969.333µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:20:04Z" - latency: 1.006848ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:19:04Z" - latency: 1.448643ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:18:04Z" - latency: 1.211273ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:17:04Z" - latency: 1.245915ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:16:04Z" - latency: 1.490101ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:15:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T23:42:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-167-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-167.ec2.internal uid: 6c36ac42-d1bb-49c3-9ae3-d9341aa10a41 resourceVersion: "62088" uid: dfd40965-07b0-4d8c-b226-c394450be71b spec: sourcePod: network-check-source-869dcfcdcd-68xxd targetEndpoint: aeb34d65779734456abc71354725fca2-f1d7072a2d4452bb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T23:48:04Z" message: 'load-balancer-api-external: tcp connection to aeb34d65779734456abc71354725fca2-f1d7072a2d4452bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.435673ms message: 'load-balancer-api-external: tcp connection to aeb34d65779734456abc71354725fca2-f1d7072a2d4452bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:24:04Z" - latency: 7.387536ms message: 'load-balancer-api-external: resolved host name aeb34d65779734456abc71354725fca2-f1d7072a2d4452bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T00:24:04Z" - latency: 4.894751ms message: 'load-balancer-api-external: tcp connection to aeb34d65779734456abc71354725fca2-f1d7072a2d4452bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:23:04Z" - latency: 7.022689ms message: 'load-balancer-api-external: resolved host name aeb34d65779734456abc71354725fca2-f1d7072a2d4452bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T00:23:04Z" - latency: 5.178456ms message: 'load-balancer-api-external: tcp connection to aeb34d65779734456abc71354725fca2-f1d7072a2d4452bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:22:04Z" - latency: 6.523221ms message: 'load-balancer-api-external: resolved host name aeb34d65779734456abc71354725fca2-f1d7072a2d4452bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T00:22:04Z" - latency: 4.811123ms message: 'load-balancer-api-external: tcp connection to aeb34d65779734456abc71354725fca2-f1d7072a2d4452bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:21:04Z" - latency: 8.376597ms message: 'load-balancer-api-external: resolved host name aeb34d65779734456abc71354725fca2-f1d7072a2d4452bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T00:21:04Z" - latency: 4.547111ms message: 'load-balancer-api-external: tcp connection to aeb34d65779734456abc71354725fca2-f1d7072a2d4452bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:20:04Z" - latency: 7.96622ms message: 'load-balancer-api-external: resolved host name aeb34d65779734456abc71354725fca2-f1d7072a2d4452bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T00:20:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T23:42:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-167-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-167.ec2.internal uid: 6c36ac42-d1bb-49c3-9ae3-d9341aa10a41 resourceVersion: "62087" uid: e3bcd0ce-9c1b-49bd-a8e7-e62f6c9a8305 spec: sourcePod: network-check-source-869dcfcdcd-68xxd targetEndpoint: aeb34d65779734456abc71354725fca2-f1d7072a2d4452bb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T23:48:04Z" message: 'load-balancer-api-internal: tcp connection to aeb34d65779734456abc71354725fca2-f1d7072a2d4452bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.434874ms message: 'load-balancer-api-internal: tcp connection to aeb34d65779734456abc71354725fca2-f1d7072a2d4452bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:24:04Z" - latency: 7.533868ms message: 'load-balancer-api-internal: resolved host name aeb34d65779734456abc71354725fca2-f1d7072a2d4452bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T00:24:04Z" - latency: 4.908417ms message: 'load-balancer-api-internal: tcp connection to aeb34d65779734456abc71354725fca2-f1d7072a2d4452bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:23:04Z" - latency: 7.082926ms message: 'load-balancer-api-internal: resolved host name aeb34d65779734456abc71354725fca2-f1d7072a2d4452bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T00:23:04Z" - latency: 5.388452ms message: 'load-balancer-api-internal: tcp connection to aeb34d65779734456abc71354725fca2-f1d7072a2d4452bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:22:04Z" - latency: 6.60806ms message: 'load-balancer-api-internal: resolved host name aeb34d65779734456abc71354725fca2-f1d7072a2d4452bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T00:22:04Z" - latency: 5.086943ms message: 'load-balancer-api-internal: tcp connection to aeb34d65779734456abc71354725fca2-f1d7072a2d4452bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:21:04Z" - latency: 8.464623ms message: 'load-balancer-api-internal: resolved host name aeb34d65779734456abc71354725fca2-f1d7072a2d4452bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T00:21:04Z" - latency: 4.597699ms message: 'load-balancer-api-internal: tcp connection to aeb34d65779734456abc71354725fca2-f1d7072a2d4452bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:20:04Z" - latency: 8.045769ms message: 'load-balancer-api-internal: resolved host name aeb34d65779734456abc71354725fca2-f1d7072a2d4452bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T00:20:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T23:42:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-167-to-network-check-target-ip-10-0-128-174 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-167.ec2.internal uid: 6c36ac42-d1bb-49c3-9ae3-d9341aa10a41 resourceVersion: "62084" uid: 12ef4562-26f4-4e1e-8797-3d19f20ff490 spec: sourcePod: network-check-source-869dcfcdcd-68xxd targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-13T23:49:04Z" message: 'network-check-target-ip-10-0-128-174: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.420906ms message: 'network-check-target-ip-10-0-128-174: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:24:04Z" - latency: 2.347349ms message: 'network-check-target-ip-10-0-128-174: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:23:04Z" - latency: 2.34282ms message: 'network-check-target-ip-10-0-128-174: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:22:04Z" - latency: 2.291232ms message: 'network-check-target-ip-10-0-128-174: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:21:04Z" - latency: 1.994123ms message: 'network-check-target-ip-10-0-128-174: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:20:04Z" - latency: 2.263414ms message: 'network-check-target-ip-10-0-128-174: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:19:04Z" - latency: 1.925857ms message: 'network-check-target-ip-10-0-128-174: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:18:04Z" - latency: 2.525111ms message: 'network-check-target-ip-10-0-128-174: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:17:04Z" - latency: 2.703423ms message: 'network-check-target-ip-10-0-128-174: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:16:04Z" - latency: 2.393037ms message: 'network-check-target-ip-10-0-128-174: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:15:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T23:42:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-167-to-network-check-target-ip-10-0-136-62 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-167.ec2.internal uid: 6c36ac42-d1bb-49c3-9ae3-d9341aa10a41 resourceVersion: "62083" uid: 4b074433-6677-44ce-983a-5b6450093ade spec: sourcePod: network-check-source-869dcfcdcd-68xxd targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-13T23:49:04Z" message: 'network-check-target-ip-10-0-136-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.047944ms message: 'network-check-target-ip-10-0-136-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:24:04Z" - latency: 2.24192ms message: 'network-check-target-ip-10-0-136-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:23:04Z" - latency: 2.250731ms message: 'network-check-target-ip-10-0-136-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:22:04Z" - latency: 2.062508ms message: 'network-check-target-ip-10-0-136-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:21:04Z" - latency: 2.068652ms message: 'network-check-target-ip-10-0-136-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:20:04Z" - latency: 2.487047ms message: 'network-check-target-ip-10-0-136-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:19:04Z" - latency: 1.837726ms message: 'network-check-target-ip-10-0-136-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:18:04Z" - latency: 2.126235ms message: 'network-check-target-ip-10-0-136-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:17:04Z" - latency: 2.393456ms message: 'network-check-target-ip-10-0-136-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:16:04Z" - latency: 2.209058ms message: 'network-check-target-ip-10-0-136-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:15:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T23:42:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-167-to-network-check-target-ip-10-0-137-167 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-167.ec2.internal uid: 6c36ac42-d1bb-49c3-9ae3-d9341aa10a41 resourceVersion: "62082" uid: 261decc8-c6bb-4158-baad-3d79fe4750e2 spec: sourcePod: network-check-source-869dcfcdcd-68xxd targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-13T23:49:04Z" message: 'network-check-target-ip-10-0-137-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.011725ms message: 'network-check-target-ip-10-0-137-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:24:04Z" - latency: 936.74µs message: 'network-check-target-ip-10-0-137-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:23:04Z" - latency: 931.93µs message: 'network-check-target-ip-10-0-137-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:22:04Z" - latency: 954.643µs message: 'network-check-target-ip-10-0-137-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:21:04Z" - latency: 969.15µs message: 'network-check-target-ip-10-0-137-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:20:04Z" - latency: 867.623µs message: 'network-check-target-ip-10-0-137-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:19:04Z" - latency: 766.949µs message: 'network-check-target-ip-10-0-137-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:18:04Z" - latency: 876.37µs message: 'network-check-target-ip-10-0-137-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:17:04Z" - latency: 993.559µs message: 'network-check-target-ip-10-0-137-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:16:04Z" - latency: 1.42307ms message: 'network-check-target-ip-10-0-137-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:15:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T23:42:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-167-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-167.ec2.internal uid: 6c36ac42-d1bb-49c3-9ae3-d9341aa10a41 resourceVersion: "62085" uid: bc2e955a-d6d7-4a80-9dba-7e7ea237d008 spec: sourcePod: network-check-source-869dcfcdcd-68xxd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-13T23:48:04Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 953.847µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:24:04Z" - latency: 2.35145ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T00:24:04Z" - latency: 870.702µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:23:04Z" - latency: 1.699399ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T00:23:04Z" - latency: 1.337947ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:22:04Z" - latency: 1.752407ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T00:22:04Z" - latency: 1.224198ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:21:04Z" - latency: 1.712202ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T00:21:04Z" - latency: 889.492µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T00:20:04Z" - latency: 1.969499ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T00:20:04Z" kind: List metadata: resourceVersion: ""