apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T21:21:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-9-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-9.ec2.internal uid: e9bdc329-f47f-4305-860b-1d1085b8ee21 resourceVersion: "20313" uid: 9b6eb859-d5d9-454c-a950-368fb067905f spec: sourcePod: network-check-source-6947749cfc-lqv8n targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T21:28:28Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 857.579µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:42:28Z" - latency: 829.09µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:41:28Z" - latency: 846.156µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:40:28Z" - latency: 894.531µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:39:28Z" - latency: 995.679µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:38:28Z" - latency: 915.992µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:37:28Z" - latency: 834.677µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:36:28Z" - latency: 1.154785ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:35:28Z" - latency: 955.313µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:34:28Z" - latency: 860.978µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:33:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T21:21:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-9-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-9.ec2.internal uid: e9bdc329-f47f-4305-860b-1d1085b8ee21 resourceVersion: "21733" uid: f4fe2e7b-1be5-4201-a12c-5cd17de01537 spec: sourcePod: network-check-source-6947749cfc-lqv8n targetEndpoint: a43301ab8885a4ade94da2bbb4b81c2b-b47e8c45520ffd0d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T21:27:28Z" message: 'load-balancer-api-external: tcp connection to a43301ab8885a4ade94da2bbb4b81c2b-b47e8c45520ffd0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.566254ms message: 'load-balancer-api-external: tcp connection to a43301ab8885a4ade94da2bbb4b81c2b-b47e8c45520ffd0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:45:28Z" - latency: 6.004317ms message: 'load-balancer-api-external: resolved host name a43301ab8885a4ade94da2bbb4b81c2b-b47e8c45520ffd0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T21:45:28Z" - latency: 4.701773ms message: 'load-balancer-api-external: tcp connection to a43301ab8885a4ade94da2bbb4b81c2b-b47e8c45520ffd0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:44:28Z" - latency: 7.245701ms message: 'load-balancer-api-external: resolved host name a43301ab8885a4ade94da2bbb4b81c2b-b47e8c45520ffd0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T21:44:28Z" - latency: 3.70889ms message: 'load-balancer-api-external: tcp connection to a43301ab8885a4ade94da2bbb4b81c2b-b47e8c45520ffd0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:43:28Z" - latency: 7.243246ms message: 'load-balancer-api-external: resolved host name a43301ab8885a4ade94da2bbb4b81c2b-b47e8c45520ffd0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T21:43:28Z" - latency: 4.725973ms message: 'load-balancer-api-external: tcp connection to a43301ab8885a4ade94da2bbb4b81c2b-b47e8c45520ffd0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:42:28Z" - latency: 9.35999ms message: 'load-balancer-api-external: resolved host name a43301ab8885a4ade94da2bbb4b81c2b-b47e8c45520ffd0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T21:42:28Z" - latency: 5.0753ms message: 'load-balancer-api-external: tcp connection to a43301ab8885a4ade94da2bbb4b81c2b-b47e8c45520ffd0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:41:28Z" - latency: 7.763593ms message: 'load-balancer-api-external: resolved host name a43301ab8885a4ade94da2bbb4b81c2b-b47e8c45520ffd0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T21:41:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T21:21:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-9-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-9.ec2.internal uid: e9bdc329-f47f-4305-860b-1d1085b8ee21 resourceVersion: "21734" uid: 800bcb6c-db30-4d83-9fd6-666ecb9b0623 spec: sourcePod: network-check-source-6947749cfc-lqv8n targetEndpoint: a43301ab8885a4ade94da2bbb4b81c2b-b47e8c45520ffd0d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T21:27:28Z" message: 'load-balancer-api-internal: tcp connection to a43301ab8885a4ade94da2bbb4b81c2b-b47e8c45520ffd0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.636062ms message: 'load-balancer-api-internal: tcp connection to a43301ab8885a4ade94da2bbb4b81c2b-b47e8c45520ffd0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:45:28Z" - latency: 5.945637ms message: 'load-balancer-api-internal: resolved host name a43301ab8885a4ade94da2bbb4b81c2b-b47e8c45520ffd0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T21:45:28Z" - latency: 4.604195ms message: 'load-balancer-api-internal: tcp connection to a43301ab8885a4ade94da2bbb4b81c2b-b47e8c45520ffd0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:44:28Z" - latency: 7.296133ms message: 'load-balancer-api-internal: resolved host name a43301ab8885a4ade94da2bbb4b81c2b-b47e8c45520ffd0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T21:44:28Z" - latency: 5.008405ms message: 'load-balancer-api-internal: tcp connection to a43301ab8885a4ade94da2bbb4b81c2b-b47e8c45520ffd0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:43:28Z" - latency: 7.122513ms message: 'load-balancer-api-internal: resolved host name a43301ab8885a4ade94da2bbb4b81c2b-b47e8c45520ffd0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T21:43:28Z" - latency: 4.38898ms message: 'load-balancer-api-internal: tcp connection to a43301ab8885a4ade94da2bbb4b81c2b-b47e8c45520ffd0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:42:28Z" - latency: 9.346658ms message: 'load-balancer-api-internal: resolved host name a43301ab8885a4ade94da2bbb4b81c2b-b47e8c45520ffd0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T21:42:28Z" - latency: 5.054631ms message: 'load-balancer-api-internal: tcp connection to a43301ab8885a4ade94da2bbb4b81c2b-b47e8c45520ffd0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:41:28Z" - latency: 7.810395ms message: 'load-balancer-api-internal: resolved host name a43301ab8885a4ade94da2bbb4b81c2b-b47e8c45520ffd0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T21:41:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T21:21:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-9-to-network-check-target-ip-10-0-133-9 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-9.ec2.internal uid: e9bdc329-f47f-4305-860b-1d1085b8ee21 resourceVersion: "20310" uid: 235ab4ec-8ac9-409a-8ac8-cba6c8127fee spec: sourcePod: network-check-source-6947749cfc-lqv8n targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-11T21:28:28Z" message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.160647ms message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:42:28Z" - latency: 821.974µs message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:41:28Z" - latency: 814.014µs message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:40:28Z" - latency: 1.259157ms message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:39:28Z" - latency: 879.185µs message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:38:28Z" - latency: 879.398µs message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:37:28Z" - latency: 739.558µs message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:36:28Z" - latency: 956.867µs message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:35:28Z" - latency: 1.206307ms message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:34:28Z" - latency: 1.000709ms message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:33:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T21:21:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-9-to-network-check-target-ip-10-0-142-82 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-9.ec2.internal uid: e9bdc329-f47f-4305-860b-1d1085b8ee21 resourceVersion: "20311" uid: b5eb1667-2be4-47eb-8755-e22afb3665b7 spec: sourcePod: network-check-source-6947749cfc-lqv8n targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T21:28:28Z" message: 'network-check-target-ip-10-0-142-82: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.890847ms message: 'network-check-target-ip-10-0-142-82: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:42:28Z" - latency: 2.475046ms message: 'network-check-target-ip-10-0-142-82: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:41:28Z" - latency: 2.053687ms message: 'network-check-target-ip-10-0-142-82: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:40:28Z" - latency: 2.007936ms message: 'network-check-target-ip-10-0-142-82: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:39:28Z" - latency: 2.324614ms message: 'network-check-target-ip-10-0-142-82: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:38:28Z" - latency: 2.044641ms message: 'network-check-target-ip-10-0-142-82: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:37:28Z" - latency: 2.34799ms message: 'network-check-target-ip-10-0-142-82: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:36:28Z" - latency: 2.404314ms message: 'network-check-target-ip-10-0-142-82: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:35:28Z" - latency: 2.395064ms message: 'network-check-target-ip-10-0-142-82: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:34:28Z" - latency: 2.346413ms message: 'network-check-target-ip-10-0-142-82: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:33:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T21:21:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-9-to-network-check-target-ip-10-0-143-6 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-9.ec2.internal uid: e9bdc329-f47f-4305-860b-1d1085b8ee21 resourceVersion: "20312" uid: a50f6940-ddd3-475a-9b3c-2e276bce05fa spec: sourcePod: network-check-source-6947749cfc-lqv8n targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-11T21:28:28Z" message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.084603ms message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:42:28Z" - latency: 2.521808ms message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:41:28Z" - latency: 2.127377ms message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:40:28Z" - latency: 2.127773ms message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:39:28Z" - latency: 2.225179ms message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:38:28Z" - latency: 2.025463ms message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:37:28Z" - latency: 2.493101ms message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:36:28Z" - latency: 2.278766ms message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:35:28Z" - latency: 2.702679ms message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:34:28Z" - latency: 2.150374ms message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:33:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T21:21:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-9-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-9.ec2.internal uid: e9bdc329-f47f-4305-860b-1d1085b8ee21 resourceVersion: "21732" uid: c58f2d9e-1008-4a5e-8a8e-b7ac131f1d4a spec: sourcePod: network-check-source-6947749cfc-lqv8n targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T21:27:28Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 736.529µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:45:28Z" - latency: 1.459437ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T21:45:28Z" - latency: 1.001674ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:44:28Z" - latency: 1.711413ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T21:44:28Z" - latency: 841.786µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:43:28Z" - latency: 1.443997ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T21:43:28Z" - latency: 1.150624ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:42:28Z" - latency: 1.488482ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T21:42:28Z" - latency: 1.027709ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T21:41:28Z" - latency: 1.389929ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T21:41:28Z" kind: List metadata: resourceVersion: ""