apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T21:34:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-246-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-246.ec2.internal uid: ba570dc2-ba23-482f-b887-75c7ad8f5c14 resourceVersion: "43312" uid: 5ba03c0f-ba3e-49d2-81ec-fddad3873242 spec: sourcePod: network-check-source-7f44b6dd87-krplr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-27T21:41:01Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 882.693µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:02:01Z" - latency: 983.366µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:01:01Z" - latency: 1.000316ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:00:01Z" - latency: 1.176841ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:59:01Z" - latency: 974.985µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:58:01Z" - latency: 917.101µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:57:01Z" - latency: 1.176582ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:56:01Z" - latency: 1.101103ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:55:01Z" - latency: 1.387024ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:54:01Z" - latency: 758.229µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:53:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T21:34:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-246-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-246.ec2.internal uid: ba570dc2-ba23-482f-b887-75c7ad8f5c14 resourceVersion: "45621" uid: 4994503b-9b58-4f6f-b26d-bef07f9e800b spec: sourcePod: network-check-source-7f44b6dd87-krplr targetEndpoint: abddbf6e36af14088a4f4a06e07eedc5-58a2f1f8fa10efbf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-27T21:40:01Z" message: 'load-balancer-api-external: tcp connection to abddbf6e36af14088a4f4a06e07eedc5-58a2f1f8fa10efbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.695307ms message: 'load-balancer-api-external: tcp connection to abddbf6e36af14088a4f4a06e07eedc5-58a2f1f8fa10efbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:04:01Z" - latency: 6.311256ms message: 'load-balancer-api-external: resolved host name abddbf6e36af14088a4f4a06e07eedc5-58a2f1f8fa10efbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T22:04:01Z" - latency: 3.65792ms message: 'load-balancer-api-external: tcp connection to abddbf6e36af14088a4f4a06e07eedc5-58a2f1f8fa10efbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:03:01Z" - latency: 6.04908ms message: 'load-balancer-api-external: resolved host name abddbf6e36af14088a4f4a06e07eedc5-58a2f1f8fa10efbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T22:03:01Z" - latency: 3.287443ms message: 'load-balancer-api-external: tcp connection to abddbf6e36af14088a4f4a06e07eedc5-58a2f1f8fa10efbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:02:01Z" - latency: 6.918229ms message: 'load-balancer-api-external: resolved host name abddbf6e36af14088a4f4a06e07eedc5-58a2f1f8fa10efbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T22:02:01Z" - latency: 4.020657ms message: 'load-balancer-api-external: tcp connection to abddbf6e36af14088a4f4a06e07eedc5-58a2f1f8fa10efbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:01:01Z" - latency: 6.324482ms message: 'load-balancer-api-external: resolved host name abddbf6e36af14088a4f4a06e07eedc5-58a2f1f8fa10efbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T22:01:01Z" - latency: 4.868435ms message: 'load-balancer-api-external: tcp connection to abddbf6e36af14088a4f4a06e07eedc5-58a2f1f8fa10efbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:00:01Z" - latency: 8.591229ms message: 'load-balancer-api-external: resolved host name abddbf6e36af14088a4f4a06e07eedc5-58a2f1f8fa10efbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T22:00:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T21:34:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-246-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-246.ec2.internal uid: ba570dc2-ba23-482f-b887-75c7ad8f5c14 resourceVersion: "45620" uid: 13d7da44-2c31-4519-a801-d6bbc83ce781 spec: sourcePod: network-check-source-7f44b6dd87-krplr targetEndpoint: abddbf6e36af14088a4f4a06e07eedc5-58a2f1f8fa10efbf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-27T21:40:01Z" message: 'load-balancer-api-internal: tcp connection to abddbf6e36af14088a4f4a06e07eedc5-58a2f1f8fa10efbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.710068ms message: 'load-balancer-api-internal: tcp connection to abddbf6e36af14088a4f4a06e07eedc5-58a2f1f8fa10efbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:04:01Z" - latency: 6.425603ms message: 'load-balancer-api-internal: resolved host name abddbf6e36af14088a4f4a06e07eedc5-58a2f1f8fa10efbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T22:04:01Z" - latency: 4.36584ms message: 'load-balancer-api-internal: tcp connection to abddbf6e36af14088a4f4a06e07eedc5-58a2f1f8fa10efbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:03:01Z" - latency: 6.021036ms message: 'load-balancer-api-internal: resolved host name abddbf6e36af14088a4f4a06e07eedc5-58a2f1f8fa10efbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T22:03:01Z" - latency: 6.056476ms message: 'load-balancer-api-internal: tcp connection to abddbf6e36af14088a4f4a06e07eedc5-58a2f1f8fa10efbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:02:01Z" - latency: 6.939513ms message: 'load-balancer-api-internal: resolved host name abddbf6e36af14088a4f4a06e07eedc5-58a2f1f8fa10efbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T22:02:01Z" - latency: 4.9824ms message: 'load-balancer-api-internal: tcp connection to abddbf6e36af14088a4f4a06e07eedc5-58a2f1f8fa10efbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:01:01Z" - latency: 6.422191ms message: 'load-balancer-api-internal: resolved host name abddbf6e36af14088a4f4a06e07eedc5-58a2f1f8fa10efbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T22:01:01Z" - latency: 4.976844ms message: 'load-balancer-api-internal: tcp connection to abddbf6e36af14088a4f4a06e07eedc5-58a2f1f8fa10efbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:00:01Z" - latency: 8.754298ms message: 'load-balancer-api-internal: resolved host name abddbf6e36af14088a4f4a06e07eedc5-58a2f1f8fa10efbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T22:00:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T21:34:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-246-to-network-check-target-ip-10-0-130-246 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-246.ec2.internal uid: ba570dc2-ba23-482f-b887-75c7ad8f5c14 resourceVersion: "43309" uid: d5f878cf-b7b6-4aa4-a1cf-e5a17d9392f4 spec: sourcePod: network-check-source-7f44b6dd87-krplr targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-27T21:41:01Z" message: 'network-check-target-ip-10-0-130-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.103532ms message: 'network-check-target-ip-10-0-130-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:02:01Z" - latency: 949.533µs message: 'network-check-target-ip-10-0-130-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:01:01Z" - latency: 1.356341ms message: 'network-check-target-ip-10-0-130-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:00:01Z" - latency: 889.524µs message: 'network-check-target-ip-10-0-130-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:59:01Z" - latency: 1.150522ms message: 'network-check-target-ip-10-0-130-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:58:01Z" - latency: 888.884µs message: 'network-check-target-ip-10-0-130-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:57:01Z" - latency: 814.935µs message: 'network-check-target-ip-10-0-130-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:56:01Z" - latency: 1.248546ms message: 'network-check-target-ip-10-0-130-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:55:01Z" - latency: 868.879µs message: 'network-check-target-ip-10-0-130-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:54:01Z" - latency: 1.050602ms message: 'network-check-target-ip-10-0-130-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:53:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T21:34:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-246-to-network-check-target-ip-10-0-133-190 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-246.ec2.internal uid: ba570dc2-ba23-482f-b887-75c7ad8f5c14 resourceVersion: "43310" uid: 098a7f7d-ce48-4834-8330-e119f3968a27 spec: sourcePod: network-check-source-7f44b6dd87-krplr targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-27T21:41:01Z" message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.114159ms message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:02:01Z" - latency: 1.953332ms message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:01:01Z" - latency: 2.488614ms message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:00:01Z" - latency: 1.93395ms message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:59:01Z" - latency: 1.857367ms message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:58:01Z" - latency: 1.95865ms message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:57:01Z" - latency: 1.98242ms message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:56:01Z" - latency: 2.02419ms message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:55:01Z" - latency: 1.843958ms message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:54:01Z" - latency: 1.915374ms message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:53:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T21:34:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-246-to-network-check-target-ip-10-0-138-159 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-246.ec2.internal uid: ba570dc2-ba23-482f-b887-75c7ad8f5c14 resourceVersion: "43311" uid: c4cca0fd-3faf-47a5-abc7-dff3589eeb98 spec: sourcePod: network-check-source-7f44b6dd87-krplr targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-27T21:41:01Z" message: 'network-check-target-ip-10-0-138-159: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.46061ms message: 'network-check-target-ip-10-0-138-159: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:02:01Z" - latency: 2.182997ms message: 'network-check-target-ip-10-0-138-159: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:01:01Z" - latency: 2.462327ms message: 'network-check-target-ip-10-0-138-159: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:00:01Z" - latency: 2.163964ms message: 'network-check-target-ip-10-0-138-159: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:59:01Z" - latency: 1.95624ms message: 'network-check-target-ip-10-0-138-159: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:58:01Z" - latency: 1.909576ms message: 'network-check-target-ip-10-0-138-159: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:57:01Z" - latency: 1.882282ms message: 'network-check-target-ip-10-0-138-159: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:56:01Z" - latency: 2.125414ms message: 'network-check-target-ip-10-0-138-159: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:55:01Z" - latency: 2.324255ms message: 'network-check-target-ip-10-0-138-159: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:54:01Z" - latency: 2.202276ms message: 'network-check-target-ip-10-0-138-159: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:53:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T21:34:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-246-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-246.ec2.internal uid: ba570dc2-ba23-482f-b887-75c7ad8f5c14 resourceVersion: "45619" uid: 302cc9ed-5479-454c-93d4-92c8fe07fe29 spec: sourcePod: network-check-source-7f44b6dd87-krplr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-27T21:40:01Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.08347ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:04:01Z" - latency: 1.710864ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T22:04:01Z" - latency: 770.818µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:03:01Z" - latency: 1.688972ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T22:03:01Z" - latency: 875.043µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:02:01Z" - latency: 1.882857ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T22:02:01Z" - latency: 1.303017ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:01:01Z" - latency: 1.763591ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T22:01:01Z" - latency: 1.399137ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T22:00:01Z" - latency: 2.218742ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T22:00:01Z" kind: List metadata: resourceVersion: ""