apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-03T20:35:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-62-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-62.ec2.internal uid: 5e30a674-fa8b-4b2d-a84a-77928da3c7a3 resourceVersion: "33291" uid: babea862-60ff-418e-8b55-949d5b21365f spec: sourcePod: network-check-source-989f8b8dc-6k479 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-03T20:42:31Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.695759ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:56:31Z" - latency: 900.928µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:55:31Z" - latency: 1.003548ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:54:31Z" - latency: 912.332µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:53:31Z" - latency: 925.018µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:52:31Z" - latency: 854.145µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:51:31Z" - latency: 1.301907ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:50:31Z" - latency: 1.051705ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:49:31Z" - latency: 942.049µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:48:31Z" - latency: 1.312244ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:47:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-03T20:35:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-62-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-62.ec2.internal uid: 5e30a674-fa8b-4b2d-a84a-77928da3c7a3 resourceVersion: "31271" uid: 289c2fa3-2ac5-42b9-8c00-46d70a63d3e4 spec: sourcePod: network-check-source-989f8b8dc-6k479 targetEndpoint: af3c1e3b7423f46d39463abcc0ca2ac7-96f66ea204b0fd6f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-03T20:41:31Z" message: 'load-balancer-api-external: tcp connection to af3c1e3b7423f46d39463abcc0ca2ac7-96f66ea204b0fd6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.1259ms message: 'load-balancer-api-external: tcp connection to af3c1e3b7423f46d39463abcc0ca2ac7-96f66ea204b0fd6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:53:31Z" - latency: 8.34207ms message: 'load-balancer-api-external: resolved host name af3c1e3b7423f46d39463abcc0ca2ac7-96f66ea204b0fd6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T20:53:31Z" - latency: 5.194126ms message: 'load-balancer-api-external: tcp connection to af3c1e3b7423f46d39463abcc0ca2ac7-96f66ea204b0fd6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:52:31Z" - latency: 8.25303ms message: 'load-balancer-api-external: resolved host name af3c1e3b7423f46d39463abcc0ca2ac7-96f66ea204b0fd6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T20:52:31Z" - latency: 4.747807ms message: 'load-balancer-api-external: tcp connection to af3c1e3b7423f46d39463abcc0ca2ac7-96f66ea204b0fd6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:51:31Z" - latency: 9.100263ms message: 'load-balancer-api-external: resolved host name af3c1e3b7423f46d39463abcc0ca2ac7-96f66ea204b0fd6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T20:51:31Z" - latency: 5.342851ms message: 'load-balancer-api-external: tcp connection to af3c1e3b7423f46d39463abcc0ca2ac7-96f66ea204b0fd6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:50:31Z" - latency: 11.066602ms message: 'load-balancer-api-external: resolved host name af3c1e3b7423f46d39463abcc0ca2ac7-96f66ea204b0fd6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T20:50:31Z" - latency: 3.89683ms message: 'load-balancer-api-external: tcp connection to af3c1e3b7423f46d39463abcc0ca2ac7-96f66ea204b0fd6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:49:31Z" - latency: 8.079533ms message: 'load-balancer-api-external: resolved host name af3c1e3b7423f46d39463abcc0ca2ac7-96f66ea204b0fd6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T20:49:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-03T20:35:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-62-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-62.ec2.internal uid: 5e30a674-fa8b-4b2d-a84a-77928da3c7a3 resourceVersion: "31270" uid: 1e1e4a3b-528c-45c5-869d-7d7f4328147c spec: sourcePod: network-check-source-989f8b8dc-6k479 targetEndpoint: af3c1e3b7423f46d39463abcc0ca2ac7-96f66ea204b0fd6f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-03T20:41:31Z" message: 'load-balancer-api-internal: tcp connection to af3c1e3b7423f46d39463abcc0ca2ac7-96f66ea204b0fd6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.888698ms message: 'load-balancer-api-internal: tcp connection to af3c1e3b7423f46d39463abcc0ca2ac7-96f66ea204b0fd6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:53:31Z" - latency: 8.201106ms message: 'load-balancer-api-internal: resolved host name af3c1e3b7423f46d39463abcc0ca2ac7-96f66ea204b0fd6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T20:53:31Z" - latency: 5.104987ms message: 'load-balancer-api-internal: tcp connection to af3c1e3b7423f46d39463abcc0ca2ac7-96f66ea204b0fd6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:52:31Z" - latency: 8.344958ms message: 'load-balancer-api-internal: resolved host name af3c1e3b7423f46d39463abcc0ca2ac7-96f66ea204b0fd6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T20:52:31Z" - latency: 5.38422ms message: 'load-balancer-api-internal: tcp connection to af3c1e3b7423f46d39463abcc0ca2ac7-96f66ea204b0fd6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:51:31Z" - latency: 9.043112ms message: 'load-balancer-api-internal: resolved host name af3c1e3b7423f46d39463abcc0ca2ac7-96f66ea204b0fd6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T20:51:31Z" - latency: 5.341346ms message: 'load-balancer-api-internal: tcp connection to af3c1e3b7423f46d39463abcc0ca2ac7-96f66ea204b0fd6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:50:31Z" - latency: 11.093243ms message: 'load-balancer-api-internal: resolved host name af3c1e3b7423f46d39463abcc0ca2ac7-96f66ea204b0fd6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T20:50:31Z" - latency: 3.903895ms message: 'load-balancer-api-internal: tcp connection to af3c1e3b7423f46d39463abcc0ca2ac7-96f66ea204b0fd6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:49:31Z" - latency: 7.99223ms message: 'load-balancer-api-internal: resolved host name af3c1e3b7423f46d39463abcc0ca2ac7-96f66ea204b0fd6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T20:49:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-03T20:35:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-62-to-network-check-target-ip-10-0-128-211 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-62.ec2.internal uid: 5e30a674-fa8b-4b2d-a84a-77928da3c7a3 resourceVersion: "33290" uid: 580cd545-d456-4f90-a2a5-980c23af23c7 spec: sourcePod: network-check-source-989f8b8dc-6k479 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-03T20:42:31Z" message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.347448ms message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:56:31Z" - latency: 2.546402ms message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:55:31Z" - latency: 2.420776ms message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:54:31Z" - latency: 2.346437ms message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:53:31Z" - latency: 2.555151ms message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:52:31Z" - latency: 2.325741ms message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:51:31Z" - latency: 2.34041ms message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:50:31Z" - latency: 2.334189ms message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:49:31Z" - latency: 2.202921ms message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:48:31Z" - latency: 2.7551ms message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:47:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-03T20:35:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-62-to-network-check-target-ip-10-0-131-62 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-62.ec2.internal uid: 5e30a674-fa8b-4b2d-a84a-77928da3c7a3 resourceVersion: "33288" uid: 30836c58-4ac5-4bd5-9005-d717403ea469 spec: sourcePod: network-check-source-989f8b8dc-6k479 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-03T20:42:31Z" message: 'network-check-target-ip-10-0-131-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 816.569µs message: 'network-check-target-ip-10-0-131-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:56:31Z" - latency: 807.207µs message: 'network-check-target-ip-10-0-131-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:55:31Z" - latency: 1.441426ms message: 'network-check-target-ip-10-0-131-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:54:31Z" - latency: 1.054082ms message: 'network-check-target-ip-10-0-131-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:53:31Z" - latency: 871.185µs message: 'network-check-target-ip-10-0-131-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:52:31Z" - latency: 912.987µs message: 'network-check-target-ip-10-0-131-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:51:31Z" - latency: 1.442047ms message: 'network-check-target-ip-10-0-131-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:50:31Z" - latency: 1.221314ms message: 'network-check-target-ip-10-0-131-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:49:31Z" - latency: 902.26µs message: 'network-check-target-ip-10-0-131-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:48:31Z" - latency: 1.486734ms message: 'network-check-target-ip-10-0-131-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:47:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-03T20:35:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-62-to-network-check-target-ip-10-0-139-68 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-62.ec2.internal uid: 5e30a674-fa8b-4b2d-a84a-77928da3c7a3 resourceVersion: "33289" uid: 78830ac6-b4fa-4608-b224-55f298e9d246 spec: sourcePod: network-check-source-989f8b8dc-6k479 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-03T20:42:31Z" message: 'network-check-target-ip-10-0-139-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.983612ms message: 'network-check-target-ip-10-0-139-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:56:31Z" - latency: 2.227211ms message: 'network-check-target-ip-10-0-139-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:55:31Z" - latency: 2.304334ms message: 'network-check-target-ip-10-0-139-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:54:31Z" - latency: 2.396018ms message: 'network-check-target-ip-10-0-139-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:53:31Z" - latency: 2.351546ms message: 'network-check-target-ip-10-0-139-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:52:31Z" - latency: 1.770896ms message: 'network-check-target-ip-10-0-139-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:51:31Z" - latency: 2.134692ms message: 'network-check-target-ip-10-0-139-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:50:31Z" - latency: 2.412661ms message: 'network-check-target-ip-10-0-139-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:49:31Z" - latency: 2.520279ms message: 'network-check-target-ip-10-0-139-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:48:31Z" - latency: 2.804976ms message: 'network-check-target-ip-10-0-139-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:47:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-03T20:35:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-62-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-62.ec2.internal uid: 5e30a674-fa8b-4b2d-a84a-77928da3c7a3 resourceVersion: "31269" uid: 2c1330ad-b39b-47be-86a0-3960e49ac2eb spec: sourcePod: network-check-source-989f8b8dc-6k479 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-03T20:41:31Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 805.027µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:53:31Z" - latency: 1.796583ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-03T20:53:31Z" - latency: 897.663µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:52:31Z" - latency: 1.784182ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-03T20:52:31Z" - latency: 927.258µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:51:31Z" - latency: 1.827765ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-03T20:51:31Z" - latency: 997.287µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:50:31Z" - latency: 2.037225ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-03T20:50:31Z" - latency: 991.113µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-03T20:49:31Z" - latency: 1.656916ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-03T20:49:31Z" kind: List metadata: resourceVersion: ""