apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T00:24:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-30-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-30.ec2.internal uid: 7dd6894e-8a8f-4390-942f-87841b250720 resourceVersion: "23951" uid: c6fdbf0a-c88d-47ab-94d3-3a6ed03ed9b2 spec: sourcePod: network-check-source-56499946bc-ggbp5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-02T00:31:18Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.096699ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:31:18Z" - latency: 1.122746ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:30:18Z" - latency: 1.390344ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:29:18Z" - latency: 1.065536ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:28:18Z" - latency: 921.259µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:27:18Z" - latency: 1.036553ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:26:18Z" - latency: 954.522µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:25:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T00:24:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-30-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-30.ec2.internal uid: 7dd6894e-8a8f-4390-942f-87841b250720 resourceVersion: "28590" uid: b6da81a7-3edf-4bbb-8e84-55c80cd34c0c spec: sourcePod: network-check-source-56499946bc-ggbp5 targetEndpoint: a2679a3f8b9534569b9205cf99d29b90-7571bc9324b92f34.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T00:30:18Z" message: 'load-balancer-api-external: tcp connection to a2679a3f8b9534569b9205cf99d29b90-7571bc9324b92f34.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.386131ms message: 'load-balancer-api-external: tcp connection to a2679a3f8b9534569b9205cf99d29b90-7571bc9324b92f34.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:36:18Z" - latency: 6.27678ms message: 'load-balancer-api-external: resolved host name a2679a3f8b9534569b9205cf99d29b90-7571bc9324b92f34.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T00:36:18Z" - latency: 4.37334ms message: 'load-balancer-api-external: tcp connection to a2679a3f8b9534569b9205cf99d29b90-7571bc9324b92f34.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:35:18Z" - latency: 7.095923ms message: 'load-balancer-api-external: resolved host name a2679a3f8b9534569b9205cf99d29b90-7571bc9324b92f34.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T00:35:18Z" - latency: 4.755869ms message: 'load-balancer-api-external: tcp connection to a2679a3f8b9534569b9205cf99d29b90-7571bc9324b92f34.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:34:18Z" - latency: 7.425046ms message: 'load-balancer-api-external: resolved host name a2679a3f8b9534569b9205cf99d29b90-7571bc9324b92f34.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T00:34:18Z" - latency: 5.87457ms message: 'load-balancer-api-external: tcp connection to a2679a3f8b9534569b9205cf99d29b90-7571bc9324b92f34.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:33:18Z" - latency: 7.227568ms message: 'load-balancer-api-external: resolved host name a2679a3f8b9534569b9205cf99d29b90-7571bc9324b92f34.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T00:33:18Z" - latency: 4.374346ms message: 'load-balancer-api-external: tcp connection to a2679a3f8b9534569b9205cf99d29b90-7571bc9324b92f34.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:32:18Z" - latency: 7.118215ms message: 'load-balancer-api-external: resolved host name a2679a3f8b9534569b9205cf99d29b90-7571bc9324b92f34.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T00:32:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T00:24:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-30-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-30.ec2.internal uid: 7dd6894e-8a8f-4390-942f-87841b250720 resourceVersion: "28589" uid: 7ca792e5-1d5f-45e0-a312-5e69f43a6834 spec: sourcePod: network-check-source-56499946bc-ggbp5 targetEndpoint: a2679a3f8b9534569b9205cf99d29b90-7571bc9324b92f34.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T00:30:18Z" message: 'load-balancer-api-internal: tcp connection to a2679a3f8b9534569b9205cf99d29b90-7571bc9324b92f34.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.115116ms message: 'load-balancer-api-internal: tcp connection to a2679a3f8b9534569b9205cf99d29b90-7571bc9324b92f34.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:36:18Z" - latency: 6.221325ms message: 'load-balancer-api-internal: resolved host name a2679a3f8b9534569b9205cf99d29b90-7571bc9324b92f34.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T00:36:18Z" - latency: 3.907058ms message: 'load-balancer-api-internal: tcp connection to a2679a3f8b9534569b9205cf99d29b90-7571bc9324b92f34.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:35:18Z" - latency: 7.173664ms message: 'load-balancer-api-internal: resolved host name a2679a3f8b9534569b9205cf99d29b90-7571bc9324b92f34.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T00:35:18Z" - latency: 4.504413ms message: 'load-balancer-api-internal: tcp connection to a2679a3f8b9534569b9205cf99d29b90-7571bc9324b92f34.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:34:18Z" - latency: 7.333985ms message: 'load-balancer-api-internal: resolved host name a2679a3f8b9534569b9205cf99d29b90-7571bc9324b92f34.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T00:34:18Z" - latency: 5.884517ms message: 'load-balancer-api-internal: tcp connection to a2679a3f8b9534569b9205cf99d29b90-7571bc9324b92f34.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:33:18Z" - latency: 7.178719ms message: 'load-balancer-api-internal: resolved host name a2679a3f8b9534569b9205cf99d29b90-7571bc9324b92f34.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T00:33:18Z" - latency: 5.143422ms message: 'load-balancer-api-internal: tcp connection to a2679a3f8b9534569b9205cf99d29b90-7571bc9324b92f34.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:32:18Z" - latency: 7.062625ms message: 'load-balancer-api-internal: resolved host name a2679a3f8b9534569b9205cf99d29b90-7571bc9324b92f34.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T00:32:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T00:24:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-30-to-network-check-target-ip-10-0-130-30 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-30.ec2.internal uid: 7dd6894e-8a8f-4390-942f-87841b250720 resourceVersion: "23948" uid: f984906f-d0cf-4a5d-82c7-d31210320558 spec: sourcePod: network-check-source-56499946bc-ggbp5 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T00:31:18Z" message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 885.453µs message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:31:18Z" - latency: 833.13µs message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:30:18Z" - latency: 995.921µs message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:29:18Z" - latency: 970.963µs message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:28:18Z" - latency: 675.5µs message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:27:18Z" - latency: 1.066114ms message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:26:18Z" - latency: 1.40749ms message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:25:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T00:24:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-30-to-network-check-target-ip-10-0-131-137 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-30.ec2.internal uid: 7dd6894e-8a8f-4390-942f-87841b250720 resourceVersion: "23950" uid: f523dc4e-8139-4947-b28b-0002606b30c1 spec: sourcePod: network-check-source-56499946bc-ggbp5 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T00:31:18Z" message: 'network-check-target-ip-10-0-131-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.539413ms message: 'network-check-target-ip-10-0-131-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:31:18Z" - latency: 2.375462ms message: 'network-check-target-ip-10-0-131-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:30:18Z" - latency: 2.384442ms message: 'network-check-target-ip-10-0-131-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:29:18Z" - latency: 2.711866ms message: 'network-check-target-ip-10-0-131-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:28:18Z" - latency: 2.326116ms message: 'network-check-target-ip-10-0-131-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:27:18Z" - latency: 2.277949ms message: 'network-check-target-ip-10-0-131-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:26:18Z" - latency: 2.361931ms message: 'network-check-target-ip-10-0-131-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:25:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T00:24:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-30-to-network-check-target-ip-10-0-133-139 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-30.ec2.internal uid: 7dd6894e-8a8f-4390-942f-87841b250720 resourceVersion: "23949" uid: 84d5a2b6-7add-4db6-9f70-b2f2a3b3fb18 spec: sourcePod: network-check-source-56499946bc-ggbp5 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-02T00:31:18Z" message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.309628ms message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:31:18Z" - latency: 2.338267ms message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:30:18Z" - latency: 2.210532ms message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:29:18Z" - latency: 2.34597ms message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:28:18Z" - latency: 2.426661ms message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:27:18Z" - latency: 2.059492ms message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:26:18Z" - latency: 2.57545ms message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:25:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T00:24:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-30-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-30.ec2.internal uid: 7dd6894e-8a8f-4390-942f-87841b250720 resourceVersion: "28588" uid: 3e493652-8890-44e3-887c-a0732778ff24 spec: sourcePod: network-check-source-56499946bc-ggbp5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-02T00:30:18Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.012618ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:36:18Z" - latency: 1.590645ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T00:36:18Z" - latency: 854.962µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:35:18Z" - latency: 1.929825ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T00:35:18Z" - latency: 771.71µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:34:18Z" - latency: 1.800454ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T00:34:18Z" - latency: 804.101µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:33:18Z" - latency: 1.981123ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T00:33:18Z" - latency: 953.543µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T00:32:18Z" - latency: 2.175701ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T00:32:18Z" kind: List metadata: resourceVersion: ""