apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:51:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-200-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-200.ec2.internal uid: 02954635-75d4-49e4-bc87-6d97db1838e6 resourceVersion: "55108" uid: 3fc8e54a-0f14-4a34-b12f-3197e63d6c32 spec: sourcePod: network-check-source-989f8b8dc-jcw86 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T23:58:05Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 971.322µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:05Z" - latency: 1.003222ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:05Z" - latency: 1.093623ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:24:05Z" - latency: 961.01µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:23:05Z" - latency: 1.450906ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:22:05Z" - latency: 1.108085ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:21:05Z" - latency: 1.255745ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:05Z" - latency: 1.097098ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:05Z" - latency: 1.020195ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:18:05Z" - latency: 1.08789ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:17:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:51:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-200-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-200.ec2.internal uid: 02954635-75d4-49e4-bc87-6d97db1838e6 resourceVersion: "55998" uid: 35f881c7-582c-4e7a-b6ef-9cb312215ae5 spec: sourcePod: network-check-source-989f8b8dc-jcw86 targetEndpoint: a832dee14678044028bee890fef522f8-7d89c7b4812bd7af.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T23:57:05Z" message: 'load-balancer-api-external: tcp connection to a832dee14678044028bee890fef522f8-7d89c7b4812bd7af.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.983198ms message: 'load-balancer-api-external: tcp connection to a832dee14678044028bee890fef522f8-7d89c7b4812bd7af.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:27:05Z" - latency: 10.135162ms message: 'load-balancer-api-external: resolved host name a832dee14678044028bee890fef522f8-7d89c7b4812bd7af.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:27:05Z" - latency: 4.595768ms message: 'load-balancer-api-external: tcp connection to a832dee14678044028bee890fef522f8-7d89c7b4812bd7af.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:05Z" - latency: 8.374074ms message: 'load-balancer-api-external: resolved host name a832dee14678044028bee890fef522f8-7d89c7b4812bd7af.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:26:05Z" - latency: 3.63908ms message: 'load-balancer-api-external: tcp connection to a832dee14678044028bee890fef522f8-7d89c7b4812bd7af.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:05Z" - latency: 9.390234ms message: 'load-balancer-api-external: resolved host name a832dee14678044028bee890fef522f8-7d89c7b4812bd7af.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:25:05Z" - latency: 5.199153ms message: 'load-balancer-api-external: tcp connection to a832dee14678044028bee890fef522f8-7d89c7b4812bd7af.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:24:05Z" - latency: 8.076846ms message: 'load-balancer-api-external: resolved host name a832dee14678044028bee890fef522f8-7d89c7b4812bd7af.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:24:05Z" - latency: 4.051859ms message: 'load-balancer-api-external: tcp connection to a832dee14678044028bee890fef522f8-7d89c7b4812bd7af.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:23:05Z" - latency: 10.198959ms message: 'load-balancer-api-external: resolved host name a832dee14678044028bee890fef522f8-7d89c7b4812bd7af.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:23:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:51:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-200-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-200.ec2.internal uid: 02954635-75d4-49e4-bc87-6d97db1838e6 resourceVersion: "55997" uid: 02fac0dc-a651-433e-b57e-494a3d2737f5 spec: sourcePod: network-check-source-989f8b8dc-jcw86 targetEndpoint: a832dee14678044028bee890fef522f8-7d89c7b4812bd7af.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T23:57:05Z" message: 'load-balancer-api-internal: tcp connection to a832dee14678044028bee890fef522f8-7d89c7b4812bd7af.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.999978ms message: 'load-balancer-api-internal: tcp connection to a832dee14678044028bee890fef522f8-7d89c7b4812bd7af.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:27:05Z" - latency: 10.193ms message: 'load-balancer-api-internal: resolved host name a832dee14678044028bee890fef522f8-7d89c7b4812bd7af.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:27:05Z" - latency: 3.311834ms message: 'load-balancer-api-internal: tcp connection to a832dee14678044028bee890fef522f8-7d89c7b4812bd7af.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:05Z" - latency: 8.52661ms message: 'load-balancer-api-internal: resolved host name a832dee14678044028bee890fef522f8-7d89c7b4812bd7af.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:26:05Z" - latency: 3.522202ms message: 'load-balancer-api-internal: tcp connection to a832dee14678044028bee890fef522f8-7d89c7b4812bd7af.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:05Z" - latency: 9.525614ms message: 'load-balancer-api-internal: resolved host name a832dee14678044028bee890fef522f8-7d89c7b4812bd7af.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:25:05Z" - latency: 5.084807ms message: 'load-balancer-api-internal: tcp connection to a832dee14678044028bee890fef522f8-7d89c7b4812bd7af.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:24:05Z" - latency: 8.126776ms message: 'load-balancer-api-internal: resolved host name a832dee14678044028bee890fef522f8-7d89c7b4812bd7af.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:24:05Z" - latency: 3.947892ms message: 'load-balancer-api-internal: tcp connection to a832dee14678044028bee890fef522f8-7d89c7b4812bd7af.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:23:05Z" - latency: 10.165152ms message: 'load-balancer-api-internal: resolved host name a832dee14678044028bee890fef522f8-7d89c7b4812bd7af.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:23:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:51:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-200-to-network-check-target-ip-10-0-130-92 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-200.ec2.internal uid: 02954635-75d4-49e4-bc87-6d97db1838e6 resourceVersion: "55106" uid: 515b0758-fc42-43a8-adae-1387b9d15fe2 spec: sourcePod: network-check-source-989f8b8dc-jcw86 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T23:58:05Z" message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.250696ms message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:05Z" - latency: 1.924718ms message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:05Z" - latency: 2.201896ms message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:24:05Z" - latency: 2.101183ms message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:23:05Z" - latency: 2.050038ms message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:22:05Z" - latency: 2.241243ms message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:21:05Z" - latency: 2.160756ms message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:05Z" - latency: 2.60316ms message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:05Z" - latency: 2.051391ms message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:18:05Z" - latency: 1.864544ms message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:17:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:51:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-200-to-network-check-target-ip-10-0-135-200 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-200.ec2.internal uid: 02954635-75d4-49e4-bc87-6d97db1838e6 resourceVersion: "55105" uid: e2a53aa7-2a7d-400d-9ec6-bba7fff3b6d7 spec: sourcePod: network-check-source-989f8b8dc-jcw86 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T23:58:05Z" message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.301261ms message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:05Z" - latency: 723.345µs message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:05Z" - latency: 1.242914ms message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:24:05Z" - latency: 1.078019ms message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:23:05Z" - latency: 1.720797ms message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:22:05Z" - latency: 848.155µs message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:21:05Z" - latency: 1.437622ms message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:05Z" - latency: 860.446µs message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:05Z" - latency: 816.163µs message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:18:05Z" - latency: 836.812µs message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:17:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:51:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-200-to-network-check-target-ip-10-0-137-188 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-200.ec2.internal uid: 02954635-75d4-49e4-bc87-6d97db1838e6 resourceVersion: "55107" uid: ac30a311-9311-4f2e-9cb5-864d7281375c spec: sourcePod: network-check-source-989f8b8dc-jcw86 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T23:58:05Z" message: 'network-check-target-ip-10-0-137-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.270444ms message: 'network-check-target-ip-10-0-137-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:05Z" - latency: 3.031027ms message: 'network-check-target-ip-10-0-137-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:05Z" - latency: 1.900542ms message: 'network-check-target-ip-10-0-137-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:24:05Z" - latency: 2.092497ms message: 'network-check-target-ip-10-0-137-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:23:05Z" - latency: 1.933372ms message: 'network-check-target-ip-10-0-137-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:22:05Z" - latency: 2.187811ms message: 'network-check-target-ip-10-0-137-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:21:05Z" - latency: 2.541652ms message: 'network-check-target-ip-10-0-137-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:05Z" - latency: 2.165038ms message: 'network-check-target-ip-10-0-137-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:05Z" - latency: 2.26855ms message: 'network-check-target-ip-10-0-137-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:18:05Z" - latency: 1.992082ms message: 'network-check-target-ip-10-0-137-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:17:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:51:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-200-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-200.ec2.internal uid: 02954635-75d4-49e4-bc87-6d97db1838e6 resourceVersion: "55996" uid: 0590d9a0-56b7-4f31-adc1-b4576d5d94f7 spec: sourcePod: network-check-source-989f8b8dc-jcw86 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T23:57:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.058702ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:27:05Z" - latency: 1.822108ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:27:05Z" - latency: 1.394731ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:05Z" - latency: 1.680122ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:26:05Z" - latency: 766.791µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:05Z" - latency: 1.835772ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:25:05Z" - latency: 879.672µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:24:05Z" - latency: 1.870188ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:24:05Z" - latency: 970.23µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:23:05Z" - latency: 1.996321ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:23:05Z" kind: List metadata: resourceVersion: ""