apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T17:12:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-180-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-180.ec2.internal uid: 3b2e45b5-a933-40b1-8825-1dd3904f4579 resourceVersion: "48561" uid: 98e05e7d-993a-4c6c-bd15-527e7ce25e3d spec: sourcePod: network-check-source-989f8b8dc-98mqm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T17:19:49Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.042427ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:47:49Z" - latency: 1.019106ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:46:49Z" - latency: 783.155µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:45:49Z" - latency: 866.128µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:44:49Z" - latency: 1.062943ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:43:49Z" - latency: 918.179µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:42:49Z" - latency: 988.847µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:41:49Z" - latency: 1.260632ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:40:49Z" - latency: 870.922µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:39:49Z" - latency: 1.063665ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:38:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T17:12:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-180-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-180.ec2.internal uid: 3b2e45b5-a933-40b1-8825-1dd3904f4579 resourceVersion: "49164" uid: 22b0a50d-5c0b-489f-86d2-8df0bada94d2 spec: sourcePod: network-check-source-989f8b8dc-98mqm targetEndpoint: a22a3ce9001d947f6a39970b972572e7-4e5be8981bf6edf0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T17:18:49Z" message: 'load-balancer-api-external: tcp connection to a22a3ce9001d947f6a39970b972572e7-4e5be8981bf6edf0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.54357ms message: 'load-balancer-api-external: tcp connection to a22a3ce9001d947f6a39970b972572e7-4e5be8981bf6edf0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:48:49Z" - latency: 7.289246ms message: 'load-balancer-api-external: resolved host name a22a3ce9001d947f6a39970b972572e7-4e5be8981bf6edf0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T17:48:49Z" - latency: 4.443191ms message: 'load-balancer-api-external: tcp connection to a22a3ce9001d947f6a39970b972572e7-4e5be8981bf6edf0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:47:49Z" - latency: 8.392273ms message: 'load-balancer-api-external: resolved host name a22a3ce9001d947f6a39970b972572e7-4e5be8981bf6edf0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T17:47:49Z" - latency: 4.446898ms message: 'load-balancer-api-external: tcp connection to a22a3ce9001d947f6a39970b972572e7-4e5be8981bf6edf0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:46:49Z" - latency: 7.339103ms message: 'load-balancer-api-external: resolved host name a22a3ce9001d947f6a39970b972572e7-4e5be8981bf6edf0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T17:46:49Z" - latency: 4.160776ms message: 'load-balancer-api-external: tcp connection to a22a3ce9001d947f6a39970b972572e7-4e5be8981bf6edf0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:45:49Z" - latency: 7.6242ms message: 'load-balancer-api-external: resolved host name a22a3ce9001d947f6a39970b972572e7-4e5be8981bf6edf0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T17:45:49Z" - latency: 4.053371ms message: 'load-balancer-api-external: tcp connection to a22a3ce9001d947f6a39970b972572e7-4e5be8981bf6edf0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:44:49Z" - latency: 7.325046ms message: 'load-balancer-api-external: resolved host name a22a3ce9001d947f6a39970b972572e7-4e5be8981bf6edf0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T17:44:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T17:12:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-180-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-180.ec2.internal uid: 3b2e45b5-a933-40b1-8825-1dd3904f4579 resourceVersion: "49165" uid: cc21ba75-ab15-44c2-bacc-4e25c1384624 spec: sourcePod: network-check-source-989f8b8dc-98mqm targetEndpoint: a22a3ce9001d947f6a39970b972572e7-4e5be8981bf6edf0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T17:18:49Z" message: 'load-balancer-api-internal: tcp connection to a22a3ce9001d947f6a39970b972572e7-4e5be8981bf6edf0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.400645ms message: 'load-balancer-api-internal: tcp connection to a22a3ce9001d947f6a39970b972572e7-4e5be8981bf6edf0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:48:49Z" - latency: 7.362401ms message: 'load-balancer-api-internal: resolved host name a22a3ce9001d947f6a39970b972572e7-4e5be8981bf6edf0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T17:48:49Z" - latency: 4.4489ms message: 'load-balancer-api-internal: tcp connection to a22a3ce9001d947f6a39970b972572e7-4e5be8981bf6edf0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:47:49Z" - latency: 8.448417ms message: 'load-balancer-api-internal: resolved host name a22a3ce9001d947f6a39970b972572e7-4e5be8981bf6edf0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T17:47:49Z" - latency: 3.629279ms message: 'load-balancer-api-internal: tcp connection to a22a3ce9001d947f6a39970b972572e7-4e5be8981bf6edf0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:46:49Z" - latency: 7.372778ms message: 'load-balancer-api-internal: resolved host name a22a3ce9001d947f6a39970b972572e7-4e5be8981bf6edf0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T17:46:49Z" - latency: 4.167611ms message: 'load-balancer-api-internal: tcp connection to a22a3ce9001d947f6a39970b972572e7-4e5be8981bf6edf0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:45:49Z" - latency: 7.604893ms message: 'load-balancer-api-internal: resolved host name a22a3ce9001d947f6a39970b972572e7-4e5be8981bf6edf0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T17:45:49Z" - latency: 4.653047ms message: 'load-balancer-api-internal: tcp connection to a22a3ce9001d947f6a39970b972572e7-4e5be8981bf6edf0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:44:49Z" - latency: 7.376217ms message: 'load-balancer-api-internal: resolved host name a22a3ce9001d947f6a39970b972572e7-4e5be8981bf6edf0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T17:44:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T17:12:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-180-to-network-check-target-ip-10-0-128-145 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-180.ec2.internal uid: 3b2e45b5-a933-40b1-8825-1dd3904f4579 resourceVersion: "48560" uid: c850888c-a774-47e6-bfcb-fe14614b13ea spec: sourcePod: network-check-source-989f8b8dc-98mqm targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T17:19:49Z" message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.041606ms message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:47:49Z" - latency: 1.920741ms message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:46:49Z" - latency: 2.163005ms message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:45:49Z" - latency: 1.707136ms message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:44:49Z" - latency: 1.850382ms message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:43:49Z" - latency: 1.77428ms message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:42:49Z" - latency: 1.905006ms message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:41:49Z" - latency: 2.034214ms message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:40:49Z" - latency: 2.082504ms message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:39:49Z" - latency: 1.947437ms message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:38:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T17:12:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-180-to-network-check-target-ip-10-0-138-180 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-180.ec2.internal uid: 3b2e45b5-a933-40b1-8825-1dd3904f4579 resourceVersion: "48558" uid: 578691dc-28ac-40ed-97aa-46b60042e9bf spec: sourcePod: network-check-source-989f8b8dc-98mqm targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T17:19:49Z" message: 'network-check-target-ip-10-0-138-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 982.245µs message: 'network-check-target-ip-10-0-138-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:47:49Z" - latency: 862.357µs message: 'network-check-target-ip-10-0-138-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:46:49Z" - latency: 1.324974ms message: 'network-check-target-ip-10-0-138-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:45:49Z" - latency: 921.407µs message: 'network-check-target-ip-10-0-138-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:44:49Z" - latency: 962.875µs message: 'network-check-target-ip-10-0-138-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:43:49Z" - latency: 1.529767ms message: 'network-check-target-ip-10-0-138-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:42:49Z" - latency: 908.845µs message: 'network-check-target-ip-10-0-138-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:41:49Z" - latency: 1.333508ms message: 'network-check-target-ip-10-0-138-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:40:49Z" - latency: 893.951µs message: 'network-check-target-ip-10-0-138-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:39:49Z" - latency: 915.578µs message: 'network-check-target-ip-10-0-138-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:38:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T17:12:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-180-to-network-check-target-ip-10-0-142-41 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-180.ec2.internal uid: 3b2e45b5-a933-40b1-8825-1dd3904f4579 resourceVersion: "48559" uid: fe662114-5e9c-40bf-a865-deae7787408c spec: sourcePod: network-check-source-989f8b8dc-98mqm targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T17:19:49Z" message: 'network-check-target-ip-10-0-142-41: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.341238ms message: 'network-check-target-ip-10-0-142-41: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:47:49Z" - latency: 2.130745ms message: 'network-check-target-ip-10-0-142-41: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:46:49Z" - latency: 2.353631ms message: 'network-check-target-ip-10-0-142-41: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:45:49Z" - latency: 1.867644ms message: 'network-check-target-ip-10-0-142-41: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:44:49Z" - latency: 2.192808ms message: 'network-check-target-ip-10-0-142-41: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:43:49Z" - latency: 2.095791ms message: 'network-check-target-ip-10-0-142-41: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:42:49Z" - latency: 2.338781ms message: 'network-check-target-ip-10-0-142-41: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:41:49Z" - latency: 2.369448ms message: 'network-check-target-ip-10-0-142-41: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:40:49Z" - latency: 2.078562ms message: 'network-check-target-ip-10-0-142-41: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:39:49Z" - latency: 2.308103ms message: 'network-check-target-ip-10-0-142-41: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:38:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T17:12:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-180-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-180.ec2.internal uid: 3b2e45b5-a933-40b1-8825-1dd3904f4579 resourceVersion: "49163" uid: 8bce6082-bb74-492c-b3ac-b56c52f14065 spec: sourcePod: network-check-source-989f8b8dc-98mqm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T17:18:49Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 912.092µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:48:49Z" - latency: 1.931007ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T17:48:49Z" - latency: 1.002422ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:47:49Z" - latency: 1.74479ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T17:47:49Z" - latency: 1.036033ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:46:49Z" - latency: 2.27692ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T17:46:49Z" - latency: 952.606µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:45:49Z" - latency: 2.040337ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T17:45:49Z" - latency: 660.121µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:44:49Z" - latency: 1.697673ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T17:44:49Z" kind: List metadata: resourceVersion: ""