apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T14:19:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-18-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-18.ec2.internal uid: 9755f474-9f86-436a-877d-d911116c436f resourceVersion: "33301" uid: c1ff3235-60e3-4fd9-9e44-9cc3ec16c5f5 spec: sourcePod: network-check-source-8894fc9bd-9m6vn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-22T14:26:45Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 768.172µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:40:45Z" - latency: 1.193079ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:39:45Z" - latency: 945.666µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:38:45Z" - latency: 988.597µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:37:45Z" - latency: 1.00518ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:36:45Z" - latency: 1.115999ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:35:45Z" - latency: 1.008772ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:34:45Z" - latency: 775.196µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:33:45Z" - latency: 733.905µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:32:45Z" - latency: 1.068251ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:31:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T14:19:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-18-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-18.ec2.internal uid: 9755f474-9f86-436a-877d-d911116c436f resourceVersion: "35754" uid: 4c072aa4-3711-41e0-8254-71265357faa1 spec: sourcePod: network-check-source-8894fc9bd-9m6vn targetEndpoint: a19ff6f1976b64b6999d4f91c65b36a8-3e9bb43239f9bee8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T14:25:45Z" message: 'load-balancer-api-external: tcp connection to a19ff6f1976b64b6999d4f91c65b36a8-3e9bb43239f9bee8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.265079ms message: 'load-balancer-api-external: tcp connection to a19ff6f1976b64b6999d4f91c65b36a8-3e9bb43239f9bee8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:43:45Z" - latency: 8.292667ms message: 'load-balancer-api-external: resolved host name a19ff6f1976b64b6999d4f91c65b36a8-3e9bb43239f9bee8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:43:45Z" - latency: 3.795557ms message: 'load-balancer-api-external: tcp connection to a19ff6f1976b64b6999d4f91c65b36a8-3e9bb43239f9bee8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:42:45Z" - latency: 10.948277ms message: 'load-balancer-api-external: resolved host name a19ff6f1976b64b6999d4f91c65b36a8-3e9bb43239f9bee8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:42:45Z" - latency: 3.253243ms message: 'load-balancer-api-external: tcp connection to a19ff6f1976b64b6999d4f91c65b36a8-3e9bb43239f9bee8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:41:45Z" - latency: 6.735809ms message: 'load-balancer-api-external: resolved host name a19ff6f1976b64b6999d4f91c65b36a8-3e9bb43239f9bee8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:41:45Z" - latency: 3.761874ms message: 'load-balancer-api-external: tcp connection to a19ff6f1976b64b6999d4f91c65b36a8-3e9bb43239f9bee8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:40:45Z" - latency: 13.799655ms message: 'load-balancer-api-external: resolved host name a19ff6f1976b64b6999d4f91c65b36a8-3e9bb43239f9bee8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:40:45Z" - latency: 5.037157ms message: 'load-balancer-api-external: tcp connection to a19ff6f1976b64b6999d4f91c65b36a8-3e9bb43239f9bee8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:39:45Z" - latency: 8.647958ms message: 'load-balancer-api-external: resolved host name a19ff6f1976b64b6999d4f91c65b36a8-3e9bb43239f9bee8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:39:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T14:19:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-18-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-18.ec2.internal uid: 9755f474-9f86-436a-877d-d911116c436f resourceVersion: "35753" uid: 45b5d47e-a031-4869-99c1-4e84d6e6b7aa spec: sourcePod: network-check-source-8894fc9bd-9m6vn targetEndpoint: a19ff6f1976b64b6999d4f91c65b36a8-3e9bb43239f9bee8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T14:25:45Z" message: 'load-balancer-api-internal: tcp connection to a19ff6f1976b64b6999d4f91c65b36a8-3e9bb43239f9bee8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.233711ms message: 'load-balancer-api-internal: tcp connection to a19ff6f1976b64b6999d4f91c65b36a8-3e9bb43239f9bee8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:43:45Z" - latency: 8.359448ms message: 'load-balancer-api-internal: resolved host name a19ff6f1976b64b6999d4f91c65b36a8-3e9bb43239f9bee8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:43:45Z" - latency: 3.835141ms message: 'load-balancer-api-internal: tcp connection to a19ff6f1976b64b6999d4f91c65b36a8-3e9bb43239f9bee8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:42:45Z" - latency: 10.839613ms message: 'load-balancer-api-internal: resolved host name a19ff6f1976b64b6999d4f91c65b36a8-3e9bb43239f9bee8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:42:45Z" - latency: 3.287289ms message: 'load-balancer-api-internal: tcp connection to a19ff6f1976b64b6999d4f91c65b36a8-3e9bb43239f9bee8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:41:45Z" - latency: 6.677963ms message: 'load-balancer-api-internal: resolved host name a19ff6f1976b64b6999d4f91c65b36a8-3e9bb43239f9bee8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:41:45Z" - latency: 3.828875ms message: 'load-balancer-api-internal: tcp connection to a19ff6f1976b64b6999d4f91c65b36a8-3e9bb43239f9bee8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:40:45Z" - latency: 13.615183ms message: 'load-balancer-api-internal: resolved host name a19ff6f1976b64b6999d4f91c65b36a8-3e9bb43239f9bee8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:40:45Z" - latency: 4.407267ms message: 'load-balancer-api-internal: tcp connection to a19ff6f1976b64b6999d4f91c65b36a8-3e9bb43239f9bee8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:39:45Z" - latency: 8.747145ms message: 'load-balancer-api-internal: resolved host name a19ff6f1976b64b6999d4f91c65b36a8-3e9bb43239f9bee8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:39:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T14:19:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-18-to-network-check-target-ip-10-0-132-130 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-18.ec2.internal uid: 9755f474-9f86-436a-877d-d911116c436f resourceVersion: "33299" uid: 411cb653-b4ce-4eed-b2ae-4c6b667b20cd spec: sourcePod: network-check-source-8894fc9bd-9m6vn targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T14:26:45Z" message: 'network-check-target-ip-10-0-132-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.319256ms message: 'network-check-target-ip-10-0-132-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:40:45Z" - latency: 2.273436ms message: 'network-check-target-ip-10-0-132-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:39:45Z" - latency: 2.079034ms message: 'network-check-target-ip-10-0-132-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:38:45Z" - latency: 2.471866ms message: 'network-check-target-ip-10-0-132-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:37:45Z" - latency: 2.14271ms message: 'network-check-target-ip-10-0-132-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:36:45Z" - latency: 1.987588ms message: 'network-check-target-ip-10-0-132-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:35:45Z" - latency: 2.382791ms message: 'network-check-target-ip-10-0-132-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:34:45Z" - latency: 2.552481ms message: 'network-check-target-ip-10-0-132-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:33:45Z" - latency: 1.717337ms message: 'network-check-target-ip-10-0-132-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:32:45Z" - latency: 2.31631ms message: 'network-check-target-ip-10-0-132-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:31:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T14:19:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-18-to-network-check-target-ip-10-0-133-31 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-18.ec2.internal uid: 9755f474-9f86-436a-877d-d911116c436f resourceVersion: "33300" uid: b2b6ed27-d4ab-4974-9200-6d4d2a02a98d spec: sourcePod: network-check-source-8894fc9bd-9m6vn targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-22T14:26:45Z" message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.366547ms message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:40:45Z" - latency: 2.378216ms message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:39:45Z" - latency: 2.288239ms message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:38:45Z" - latency: 2.146752ms message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:37:45Z" - latency: 2.559504ms message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:36:45Z" - latency: 2.227066ms message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:35:45Z" - latency: 2.221738ms message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:34:45Z" - latency: 2.693947ms message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:33:45Z" - latency: 2.063648ms message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:32:45Z" - latency: 2.275274ms message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:31:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T14:19:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-18-to-network-check-target-ip-10-0-136-18 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-18.ec2.internal uid: 9755f474-9f86-436a-877d-d911116c436f resourceVersion: "33298" uid: 0ef33516-26be-4328-9e9c-79ff30cb1553 spec: sourcePod: network-check-source-8894fc9bd-9m6vn targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T14:26:45Z" message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 858.051µs message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:40:45Z" - latency: 864.75µs message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:39:45Z" - latency: 873.964µs message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:38:45Z" - latency: 818.838µs message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:37:45Z" - latency: 780.461µs message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:36:45Z" - latency: 727.902µs message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:35:45Z" - latency: 754.146µs message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:34:45Z" - latency: 1.317092ms message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:33:45Z" - latency: 678.412µs message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:32:45Z" - latency: 936.953µs message: 'network-check-target-ip-10-0-136-18: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:31:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T14:19:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-18-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-18.ec2.internal uid: 9755f474-9f86-436a-877d-d911116c436f resourceVersion: "35752" uid: 2a5656ed-a33e-43a2-8fd2-3b3067ce79ac spec: sourcePod: network-check-source-8894fc9bd-9m6vn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-22T14:25:45Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 956.918µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:43:45Z" - latency: 1.568223ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T14:43:45Z" - latency: 737.331µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:42:45Z" - latency: 1.610538ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T14:42:45Z" - latency: 930.424µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:41:45Z" - latency: 2.173028ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T14:41:45Z" - latency: 1.537485ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:40:45Z" - latency: 1.888419ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T14:40:45Z" - latency: 826.654µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:39:45Z" - latency: 1.588093ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T14:39:45Z" kind: List metadata: resourceVersion: ""