apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:43:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-99-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-99.ec2.internal uid: 8afb0ce8-6976-4db5-8b45-b81b306ab3b5 resourceVersion: "30274" uid: 2cd165d2-0298-4564-baf0-b762e79fe3fc spec: sourcePod: network-check-source-dbd9cf844-lvkbn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-10T12:50:11Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.307056ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:57:11Z" - latency: 1.144484ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:56:11Z" - latency: 932.014µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:55:11Z" - latency: 1.75021ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:54:11Z" - latency: 1.254753ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:53:11Z" - latency: 757.343µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:52:11Z" - latency: 1.316785ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:51:11Z" - latency: 1.228469ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:50:11Z" - latency: 1.150992ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:49:11Z" - latency: 1.032883ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:48:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:43:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-99-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-99.ec2.internal uid: 8afb0ce8-6976-4db5-8b45-b81b306ab3b5 resourceVersion: "28980" uid: c6d14917-8cda-4362-a058-be3edc6163b3 spec: sourcePod: network-check-source-dbd9cf844-lvkbn targetEndpoint: ac5acfd83676a4b2ab281e779f6c26da-6ed3249dd116d5fb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T12:49:11Z" message: 'load-balancer-api-external: tcp connection to ac5acfd83676a4b2ab281e779f6c26da-6ed3249dd116d5fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.692441ms message: 'load-balancer-api-external: tcp connection to ac5acfd83676a4b2ab281e779f6c26da-6ed3249dd116d5fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:55:11Z" - latency: 10.080793ms message: 'load-balancer-api-external: resolved host name ac5acfd83676a4b2ab281e779f6c26da-6ed3249dd116d5fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:55:11Z" - latency: 5.343515ms message: 'load-balancer-api-external: tcp connection to ac5acfd83676a4b2ab281e779f6c26da-6ed3249dd116d5fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:54:11Z" - latency: 6.357289ms message: 'load-balancer-api-external: resolved host name ac5acfd83676a4b2ab281e779f6c26da-6ed3249dd116d5fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:54:11Z" - latency: 5.426261ms message: 'load-balancer-api-external: tcp connection to ac5acfd83676a4b2ab281e779f6c26da-6ed3249dd116d5fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:53:11Z" - latency: 7.243749ms message: 'load-balancer-api-external: resolved host name ac5acfd83676a4b2ab281e779f6c26da-6ed3249dd116d5fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:53:11Z" - latency: 6.29767ms message: 'load-balancer-api-external: tcp connection to ac5acfd83676a4b2ab281e779f6c26da-6ed3249dd116d5fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:52:11Z" - latency: 6.951707ms message: 'load-balancer-api-external: resolved host name ac5acfd83676a4b2ab281e779f6c26da-6ed3249dd116d5fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:52:11Z" - latency: 4.596747ms message: 'load-balancer-api-external: tcp connection to ac5acfd83676a4b2ab281e779f6c26da-6ed3249dd116d5fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:51:11Z" - latency: 6.872757ms message: 'load-balancer-api-external: resolved host name ac5acfd83676a4b2ab281e779f6c26da-6ed3249dd116d5fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:51:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:43:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-99-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-99.ec2.internal uid: 8afb0ce8-6976-4db5-8b45-b81b306ab3b5 resourceVersion: "28979" uid: 9ebcd17e-49b2-4e11-903e-8dacd8c736f2 spec: sourcePod: network-check-source-dbd9cf844-lvkbn targetEndpoint: ac5acfd83676a4b2ab281e779f6c26da-6ed3249dd116d5fb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T12:49:11Z" message: 'load-balancer-api-internal: tcp connection to ac5acfd83676a4b2ab281e779f6c26da-6ed3249dd116d5fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.202504ms message: 'load-balancer-api-internal: tcp connection to ac5acfd83676a4b2ab281e779f6c26da-6ed3249dd116d5fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:55:11Z" - latency: 10.163354ms message: 'load-balancer-api-internal: resolved host name ac5acfd83676a4b2ab281e779f6c26da-6ed3249dd116d5fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:55:11Z" - latency: 5.325737ms message: 'load-balancer-api-internal: tcp connection to ac5acfd83676a4b2ab281e779f6c26da-6ed3249dd116d5fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:54:11Z" - latency: 6.38104ms message: 'load-balancer-api-internal: resolved host name ac5acfd83676a4b2ab281e779f6c26da-6ed3249dd116d5fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:54:11Z" - latency: 5.761025ms message: 'load-balancer-api-internal: tcp connection to ac5acfd83676a4b2ab281e779f6c26da-6ed3249dd116d5fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:53:11Z" - latency: 7.304491ms message: 'load-balancer-api-internal: resolved host name ac5acfd83676a4b2ab281e779f6c26da-6ed3249dd116d5fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:53:11Z" - latency: 6.163489ms message: 'load-balancer-api-internal: tcp connection to ac5acfd83676a4b2ab281e779f6c26da-6ed3249dd116d5fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:52:11Z" - latency: 6.989021ms message: 'load-balancer-api-internal: resolved host name ac5acfd83676a4b2ab281e779f6c26da-6ed3249dd116d5fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:52:11Z" - latency: 5.414457ms message: 'load-balancer-api-internal: tcp connection to ac5acfd83676a4b2ab281e779f6c26da-6ed3249dd116d5fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:51:11Z" - latency: 6.915777ms message: 'load-balancer-api-internal: resolved host name ac5acfd83676a4b2ab281e779f6c26da-6ed3249dd116d5fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:51:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:43:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-99-to-network-check-target-ip-10-0-130-175 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-99.ec2.internal uid: 8afb0ce8-6976-4db5-8b45-b81b306ab3b5 resourceVersion: "30273" uid: 1691482a-e1d7-41e2-bb1e-fbb4b05841ae spec: sourcePod: network-check-source-dbd9cf844-lvkbn targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-10T12:50:11Z" message: 'network-check-target-ip-10-0-130-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.076686ms message: 'network-check-target-ip-10-0-130-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:57:11Z" - latency: 1.754684ms message: 'network-check-target-ip-10-0-130-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:56:11Z" - latency: 2.654919ms message: 'network-check-target-ip-10-0-130-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:55:11Z" - latency: 2.054867ms message: 'network-check-target-ip-10-0-130-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:54:11Z" - latency: 1.962149ms message: 'network-check-target-ip-10-0-130-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:53:11Z" - latency: 3.877114ms message: 'network-check-target-ip-10-0-130-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:52:11Z" - latency: 1.546364ms message: 'network-check-target-ip-10-0-130-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:51:11Z" - latency: 1.513624ms message: 'network-check-target-ip-10-0-130-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:50:11Z" - latency: 1.699679ms message: 'network-check-target-ip-10-0-130-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:49:11Z" - latency: 1.559038ms message: 'network-check-target-ip-10-0-130-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:48:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:43:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-99-to-network-check-target-ip-10-0-133-72 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-99.ec2.internal uid: 8afb0ce8-6976-4db5-8b45-b81b306ab3b5 resourceVersion: "30272" uid: 72dc72e6-f616-4fc7-9bfa-3852219bf905 spec: sourcePod: network-check-source-dbd9cf844-lvkbn targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-10T12:50:11Z" message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.419105ms message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:57:11Z" - latency: 2.298378ms message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:56:11Z" - latency: 2.760259ms message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:55:11Z" - latency: 2.394846ms message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:54:11Z" - latency: 2.253307ms message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:53:11Z" - latency: 2.062726ms message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:52:11Z" - latency: 2.23329ms message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:51:11Z" - latency: 2.011586ms message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:50:11Z" - latency: 2.258228ms message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:49:11Z" - latency: 2.133732ms message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:48:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:43:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-99-to-network-check-target-ip-10-0-138-99 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-99.ec2.internal uid: 8afb0ce8-6976-4db5-8b45-b81b306ab3b5 resourceVersion: "30271" uid: 12c91a03-82a9-4b74-a6f9-126c2dcbc8f4 spec: sourcePod: network-check-source-dbd9cf844-lvkbn targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-10T12:50:11Z" message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.241867ms message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:57:11Z" - latency: 963.917µs message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:56:11Z" - latency: 1.42425ms message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:55:11Z" - latency: 1.125397ms message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:54:11Z" - latency: 1.015564ms message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:53:11Z" - latency: 1.48572ms message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:52:11Z" - latency: 906.622µs message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:51:11Z" - latency: 968.552µs message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:50:11Z" - latency: 974.938µs message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:49:11Z" - latency: 1.404189ms message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:48:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:43:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-99-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-99.ec2.internal uid: 8afb0ce8-6976-4db5-8b45-b81b306ab3b5 resourceVersion: "28978" uid: a66b3b9f-426f-425b-8546-bc893939e09e spec: sourcePod: network-check-source-dbd9cf844-lvkbn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-10T12:49:11Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.338356ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:55:11Z" - latency: 1.924844ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T12:55:11Z" - latency: 1.08805ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:54:11Z" - latency: 1.987255ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T12:54:11Z" - latency: 1.280078ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:53:11Z" - latency: 2.119563ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T12:53:11Z" - latency: 1.972503ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:52:11Z" - latency: 1.962141ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T12:52:11Z" - latency: 827.693µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:51:11Z" - latency: 2.145789ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T12:51:11Z" kind: List metadata: resourceVersion: ""