apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T19:18:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-180-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-180.ec2.internal uid: 0f3900fd-15f5-43da-a8f7-8c9602db46d0 resourceVersion: "45875" uid: 2280b8f1-3904-44b5-bfec-4a71cd72ab3e spec: sourcePod: network-check-source-6947749cfc-c7lsh targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-12T19:25:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.186855ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:46:35Z" - latency: 1.339746ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:45:35Z" - latency: 1.249002ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:44:35Z" - latency: 1.363039ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:43:35Z" - latency: 1.443188ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:42:35Z" - latency: 1.312877ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:41:35Z" - latency: 1.305389ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:40:35Z" - latency: 996.094µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:39:35Z" - latency: 1.154213ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:38:35Z" - latency: 999.634µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:37:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T19:18:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-180-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-180.ec2.internal uid: 0f3900fd-15f5-43da-a8f7-8c9602db46d0 resourceVersion: "47894" uid: 04f59c7e-3928-4f27-af8c-228f48949a88 spec: sourcePod: network-check-source-6947749cfc-c7lsh targetEndpoint: a94d636234d104dd5a8ff11def709bb7-e786d95764a823ea.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T19:24:35Z" message: 'load-balancer-api-external: tcp connection to a94d636234d104dd5a8ff11def709bb7-e786d95764a823ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.183442ms message: 'load-balancer-api-external: tcp connection to a94d636234d104dd5a8ff11def709bb7-e786d95764a823ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:48:35Z" - latency: 8.891296ms message: 'load-balancer-api-external: resolved host name a94d636234d104dd5a8ff11def709bb7-e786d95764a823ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:48:35Z" - latency: 4.074201ms message: 'load-balancer-api-external: tcp connection to a94d636234d104dd5a8ff11def709bb7-e786d95764a823ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:47:35Z" - latency: 9.070682ms message: 'load-balancer-api-external: resolved host name a94d636234d104dd5a8ff11def709bb7-e786d95764a823ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:47:35Z" - latency: 4.70096ms message: 'load-balancer-api-external: tcp connection to a94d636234d104dd5a8ff11def709bb7-e786d95764a823ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:46:35Z" - latency: 12.107635ms message: 'load-balancer-api-external: resolved host name a94d636234d104dd5a8ff11def709bb7-e786d95764a823ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:46:35Z" - latency: 4.178812ms message: 'load-balancer-api-external: tcp connection to a94d636234d104dd5a8ff11def709bb7-e786d95764a823ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:45:35Z" - latency: 10.208269ms message: 'load-balancer-api-external: resolved host name a94d636234d104dd5a8ff11def709bb7-e786d95764a823ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:45:35Z" - latency: 4.07323ms message: 'load-balancer-api-external: tcp connection to a94d636234d104dd5a8ff11def709bb7-e786d95764a823ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:44:35Z" - latency: 8.900219ms message: 'load-balancer-api-external: resolved host name a94d636234d104dd5a8ff11def709bb7-e786d95764a823ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:44:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T19:18:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-180-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-180.ec2.internal uid: 0f3900fd-15f5-43da-a8f7-8c9602db46d0 resourceVersion: "47893" uid: 2ad05a42-4040-4825-93d5-602f33d5a5f7 spec: sourcePod: network-check-source-6947749cfc-c7lsh targetEndpoint: a94d636234d104dd5a8ff11def709bb7-e786d95764a823ea.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T19:24:35Z" message: 'load-balancer-api-internal: tcp connection to a94d636234d104dd5a8ff11def709bb7-e786d95764a823ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.189361ms message: 'load-balancer-api-internal: tcp connection to a94d636234d104dd5a8ff11def709bb7-e786d95764a823ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:48:35Z" - latency: 8.938805ms message: 'load-balancer-api-internal: resolved host name a94d636234d104dd5a8ff11def709bb7-e786d95764a823ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:48:35Z" - latency: 4.193956ms message: 'load-balancer-api-internal: tcp connection to a94d636234d104dd5a8ff11def709bb7-e786d95764a823ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:47:35Z" - latency: 9.200246ms message: 'load-balancer-api-internal: resolved host name a94d636234d104dd5a8ff11def709bb7-e786d95764a823ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:47:35Z" - latency: 4.677968ms message: 'load-balancer-api-internal: tcp connection to a94d636234d104dd5a8ff11def709bb7-e786d95764a823ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:46:35Z" - latency: 12.192523ms message: 'load-balancer-api-internal: resolved host name a94d636234d104dd5a8ff11def709bb7-e786d95764a823ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:46:35Z" - latency: 3.766127ms message: 'load-balancer-api-internal: tcp connection to a94d636234d104dd5a8ff11def709bb7-e786d95764a823ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:45:35Z" - latency: 10.143405ms message: 'load-balancer-api-internal: resolved host name a94d636234d104dd5a8ff11def709bb7-e786d95764a823ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:45:35Z" - latency: 3.791524ms message: 'load-balancer-api-internal: tcp connection to a94d636234d104dd5a8ff11def709bb7-e786d95764a823ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:44:35Z" - latency: 8.917175ms message: 'load-balancer-api-internal: resolved host name a94d636234d104dd5a8ff11def709bb7-e786d95764a823ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:44:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T19:18:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-180-to-network-check-target-ip-10-0-132-53 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-180.ec2.internal uid: 0f3900fd-15f5-43da-a8f7-8c9602db46d0 resourceVersion: "45873" uid: a1fe21a8-1b75-4220-9c35-7e5e57c8f140 spec: sourcePod: network-check-source-6947749cfc-c7lsh targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-12T19:25:35Z" message: 'network-check-target-ip-10-0-132-53: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.153313ms message: 'network-check-target-ip-10-0-132-53: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:46:35Z" - latency: 2.383605ms message: 'network-check-target-ip-10-0-132-53: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:45:35Z" - latency: 2.24957ms message: 'network-check-target-ip-10-0-132-53: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:44:35Z" - latency: 2.056737ms message: 'network-check-target-ip-10-0-132-53: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:43:35Z" - latency: 2.248905ms message: 'network-check-target-ip-10-0-132-53: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:42:35Z" - latency: 2.282446ms message: 'network-check-target-ip-10-0-132-53: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:41:35Z" - latency: 2.132431ms message: 'network-check-target-ip-10-0-132-53: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:40:35Z" - latency: 2.140835ms message: 'network-check-target-ip-10-0-132-53: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:39:35Z" - latency: 2.303355ms message: 'network-check-target-ip-10-0-132-53: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:38:35Z" - latency: 2.361034ms message: 'network-check-target-ip-10-0-132-53: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:37:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T19:18:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-180-to-network-check-target-ip-10-0-133-180 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-180.ec2.internal uid: 0f3900fd-15f5-43da-a8f7-8c9602db46d0 resourceVersion: "45871" uid: 298fd18a-2db5-41b3-aa62-1857942ad5e0 spec: sourcePod: network-check-source-6947749cfc-c7lsh targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-12T19:25:35Z" message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.144972ms message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:46:35Z" - latency: 932.516µs message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:45:35Z" - latency: 1.522471ms message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:44:35Z" - latency: 1.082571ms message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:43:35Z" - latency: 891.869µs message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:42:35Z" - latency: 1.034869ms message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:41:35Z" - latency: 935.255µs message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:40:35Z" - latency: 1.316584ms message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:39:35Z" - latency: 794.868µs message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:38:35Z" - latency: 1.396691ms message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:37:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T19:18:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-180-to-network-check-target-ip-10-0-136-61 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-180.ec2.internal uid: 0f3900fd-15f5-43da-a8f7-8c9602db46d0 resourceVersion: "45874" uid: 15012a76-982b-48e3-bb1a-759e6ff89fbe spec: sourcePod: network-check-source-6947749cfc-c7lsh targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-12T19:25:35Z" message: 'network-check-target-ip-10-0-136-61: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.137638ms message: 'network-check-target-ip-10-0-136-61: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:46:35Z" - latency: 1.972819ms message: 'network-check-target-ip-10-0-136-61: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:45:35Z" - latency: 2.207241ms message: 'network-check-target-ip-10-0-136-61: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:44:35Z" - latency: 2.273711ms message: 'network-check-target-ip-10-0-136-61: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:43:35Z" - latency: 2.137577ms message: 'network-check-target-ip-10-0-136-61: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:42:35Z" - latency: 1.971133ms message: 'network-check-target-ip-10-0-136-61: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:41:35Z" - latency: 2.416987ms message: 'network-check-target-ip-10-0-136-61: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:40:35Z" - latency: 2.10221ms message: 'network-check-target-ip-10-0-136-61: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:39:35Z" - latency: 2.058162ms message: 'network-check-target-ip-10-0-136-61: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:38:35Z" - latency: 2.056474ms message: 'network-check-target-ip-10-0-136-61: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:37:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T19:18:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-180-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-180.ec2.internal uid: 0f3900fd-15f5-43da-a8f7-8c9602db46d0 resourceVersion: "47892" uid: e84be2de-155f-48fe-abc8-ddfcf991a718 spec: sourcePod: network-check-source-6947749cfc-c7lsh targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-12T19:24:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 792.54µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:48:35Z" - latency: 2.113776ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T19:48:35Z" - latency: 868.18µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:47:35Z" - latency: 2.074938ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T19:47:35Z" - latency: 927.095µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:46:35Z" - latency: 2.289032ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T19:46:35Z" - latency: 1.042462ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:45:35Z" - latency: 2.637167ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T19:45:35Z" - latency: 920.928µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:44:35Z" - latency: 2.075219ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T19:44:35Z" kind: List metadata: resourceVersion: ""