apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T13:08:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-71-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-71.ec2.internal uid: 6b23b438-152e-4ad4-a296-67ad68318150 resourceVersion: "52607" uid: 5664e959-fc4f-47f1-b841-2ef0f2b66bbb spec: sourcePod: network-check-source-7f44b6dd87-dlmmr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-25T13:15:48Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 750.31µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:04:48Z" - latency: 1.215787ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:03:48Z" - latency: 1.352936ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:02:48Z" - latency: 926.041µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:01:48Z" - latency: 1.695561ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:00:48Z" - latency: 988.973µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:59:48Z" - latency: 1.144903ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:58:48Z" - latency: 962.448µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:57:48Z" - latency: 722.695µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:56:48Z" - latency: 1.199872ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:55:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T13:08:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-71-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-71.ec2.internal uid: 6b23b438-152e-4ad4-a296-67ad68318150 resourceVersion: "55423" uid: 721fbd0f-fd72-43f3-ba79-4eb37b0b61ca spec: sourcePod: network-check-source-7f44b6dd87-dlmmr targetEndpoint: a0f3ec9b156f74b159ffa4916f17245c-4ffc446a6907e801.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T13:14:48Z" message: 'load-balancer-api-external: tcp connection to a0f3ec9b156f74b159ffa4916f17245c-4ffc446a6907e801.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.058373ms message: 'load-balancer-api-external: tcp connection to a0f3ec9b156f74b159ffa4916f17245c-4ffc446a6907e801.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:08:48Z" - latency: 8.341523ms message: 'load-balancer-api-external: resolved host name a0f3ec9b156f74b159ffa4916f17245c-4ffc446a6907e801.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T14:08:48Z" - latency: 6.409896ms message: 'load-balancer-api-external: tcp connection to a0f3ec9b156f74b159ffa4916f17245c-4ffc446a6907e801.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:07:48Z" - latency: 8.941637ms message: 'load-balancer-api-external: resolved host name a0f3ec9b156f74b159ffa4916f17245c-4ffc446a6907e801.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T14:07:48Z" - latency: 4.694552ms message: 'load-balancer-api-external: tcp connection to a0f3ec9b156f74b159ffa4916f17245c-4ffc446a6907e801.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:06:48Z" - latency: 10.567229ms message: 'load-balancer-api-external: resolved host name a0f3ec9b156f74b159ffa4916f17245c-4ffc446a6907e801.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T14:06:48Z" - latency: 4.623906ms message: 'load-balancer-api-external: tcp connection to a0f3ec9b156f74b159ffa4916f17245c-4ffc446a6907e801.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:05:48Z" - latency: 8.520051ms message: 'load-balancer-api-external: resolved host name a0f3ec9b156f74b159ffa4916f17245c-4ffc446a6907e801.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T14:05:48Z" - latency: 4.883314ms message: 'load-balancer-api-external: tcp connection to a0f3ec9b156f74b159ffa4916f17245c-4ffc446a6907e801.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:04:48Z" - latency: 10.06392ms message: 'load-balancer-api-external: resolved host name a0f3ec9b156f74b159ffa4916f17245c-4ffc446a6907e801.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T14:04:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T13:08:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-71-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-71.ec2.internal uid: 6b23b438-152e-4ad4-a296-67ad68318150 resourceVersion: "55424" uid: a00ab310-bd66-4e24-bd79-b14ec29fd365 spec: sourcePod: network-check-source-7f44b6dd87-dlmmr targetEndpoint: a0f3ec9b156f74b159ffa4916f17245c-4ffc446a6907e801.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T13:14:48Z" message: 'load-balancer-api-internal: tcp connection to a0f3ec9b156f74b159ffa4916f17245c-4ffc446a6907e801.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.003058ms message: 'load-balancer-api-internal: tcp connection to a0f3ec9b156f74b159ffa4916f17245c-4ffc446a6907e801.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:08:48Z" - latency: 8.436564ms message: 'load-balancer-api-internal: resolved host name a0f3ec9b156f74b159ffa4916f17245c-4ffc446a6907e801.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T14:08:48Z" - latency: 6.744031ms message: 'load-balancer-api-internal: tcp connection to a0f3ec9b156f74b159ffa4916f17245c-4ffc446a6907e801.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:07:48Z" - latency: 9.035127ms message: 'load-balancer-api-internal: resolved host name a0f3ec9b156f74b159ffa4916f17245c-4ffc446a6907e801.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T14:07:48Z" - latency: 4.711262ms message: 'load-balancer-api-internal: tcp connection to a0f3ec9b156f74b159ffa4916f17245c-4ffc446a6907e801.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:06:48Z" - latency: 10.611118ms message: 'load-balancer-api-internal: resolved host name a0f3ec9b156f74b159ffa4916f17245c-4ffc446a6907e801.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T14:06:48Z" - latency: 3.889661ms message: 'load-balancer-api-internal: tcp connection to a0f3ec9b156f74b159ffa4916f17245c-4ffc446a6907e801.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:05:48Z" - latency: 8.598509ms message: 'load-balancer-api-internal: resolved host name a0f3ec9b156f74b159ffa4916f17245c-4ffc446a6907e801.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T14:05:48Z" - latency: 5.011947ms message: 'load-balancer-api-internal: tcp connection to a0f3ec9b156f74b159ffa4916f17245c-4ffc446a6907e801.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:04:48Z" - latency: 10.099402ms message: 'load-balancer-api-internal: resolved host name a0f3ec9b156f74b159ffa4916f17245c-4ffc446a6907e801.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T14:04:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T13:08:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-71-to-network-check-target-ip-10-0-129-151 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-71.ec2.internal uid: 6b23b438-152e-4ad4-a296-67ad68318150 resourceVersion: "52605" uid: 724be0cc-d9d7-4fd7-ac40-fea156b1c209 spec: sourcePod: network-check-source-7f44b6dd87-dlmmr targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-25T13:15:48Z" message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.197305ms message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:04:48Z" - latency: 2.324529ms message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:03:48Z" - latency: 2.239193ms message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:02:48Z" - latency: 1.961311ms message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:01:48Z" - latency: 2.378235ms message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:00:48Z" - latency: 2.195918ms message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:59:48Z" - latency: 2.415855ms message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:58:48Z" - latency: 2.192166ms message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:57:48Z" - latency: 2.062653ms message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:56:48Z" - latency: 2.085267ms message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:55:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T13:08:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-71-to-network-check-target-ip-10-0-135-71 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-71.ec2.internal uid: 6b23b438-152e-4ad4-a296-67ad68318150 resourceVersion: "52604" uid: 2721b5ce-1508-4876-864f-ae56471c5706 spec: sourcePod: network-check-source-7f44b6dd87-dlmmr targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-25T13:15:48Z" message: 'network-check-target-ip-10-0-135-71: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.474625ms message: 'network-check-target-ip-10-0-135-71: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:04:48Z" - latency: 858.432µs message: 'network-check-target-ip-10-0-135-71: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:03:48Z" - latency: 907.097µs message: 'network-check-target-ip-10-0-135-71: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:02:48Z" - latency: 1.016028ms message: 'network-check-target-ip-10-0-135-71: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:01:48Z" - latency: 977.735µs message: 'network-check-target-ip-10-0-135-71: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:00:48Z" - latency: 1.123583ms message: 'network-check-target-ip-10-0-135-71: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:59:48Z" - latency: 845.447µs message: 'network-check-target-ip-10-0-135-71: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:58:48Z" - latency: 1.386515ms message: 'network-check-target-ip-10-0-135-71: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:57:48Z" - latency: 970.241µs message: 'network-check-target-ip-10-0-135-71: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:56:48Z" - latency: 730.916µs message: 'network-check-target-ip-10-0-135-71: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:55:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T13:08:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-71-to-network-check-target-ip-10-0-143-235 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-71.ec2.internal uid: 6b23b438-152e-4ad4-a296-67ad68318150 resourceVersion: "52606" uid: b94c73ea-a955-42c5-a02e-942189465e5f spec: sourcePod: network-check-source-7f44b6dd87-dlmmr targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-25T13:15:48Z" message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.812552ms message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:04:48Z" - latency: 1.958357ms message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:03:48Z" - latency: 1.700997ms message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:02:48Z" - latency: 1.878357ms message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:01:48Z" - latency: 2.009862ms message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:00:48Z" - latency: 1.809602ms message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:59:48Z" - latency: 2.002232ms message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:58:48Z" - latency: 2.164745ms message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:57:48Z" - latency: 1.75233ms message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:56:48Z" - latency: 1.847782ms message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:55:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T13:08:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-71-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-71.ec2.internal uid: 6b23b438-152e-4ad4-a296-67ad68318150 resourceVersion: "55422" uid: 81c7c934-3ea7-4d31-ad4c-7ede5d8f6d68 spec: sourcePod: network-check-source-7f44b6dd87-dlmmr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-25T13:14:48Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 862.813µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:08:48Z" - latency: 1.703616ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T14:08:48Z" - latency: 914.005µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:07:48Z" - latency: 2.314057ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T14:07:48Z" - latency: 979.079µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:06:48Z" - latency: 3.202996ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T14:06:48Z" - latency: 971.729µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:05:48Z" - latency: 1.87549ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T14:05:48Z" - latency: 931.473µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:04:48Z" - latency: 1.678332ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T14:04:48Z" kind: List metadata: resourceVersion: ""