apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T19:59:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-12-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-12.ec2.internal uid: e3c935fe-7f90-4441-a783-048816b4a6b0 resourceVersion: "61327" uid: 0d9a49b7-fa07-4ed7-8bb7-b7673a17001f spec: sourcePod: network-check-source-869dcfcdcd-j4t2j targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-15T20:06:14Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 968.345µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:41:14Z" - latency: 1.042422ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:40:14Z" - latency: 1.224084ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:39:14Z" - latency: 782.543µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:38:14Z" - latency: 1.170902ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:37:14Z" - latency: 1.098887ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:36:14Z" - latency: 1.011877ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:35:14Z" - latency: 986.023µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:34:14Z" - latency: 1.047057ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:33:14Z" - latency: 1.025057ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:32:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T19:59:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-12-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-12.ec2.internal uid: e3c935fe-7f90-4441-a783-048816b4a6b0 resourceVersion: "61328" uid: f632e8fc-3a84-4725-bb53-0d198870efd8 spec: sourcePod: network-check-source-869dcfcdcd-j4t2j targetEndpoint: a00847e8c24b148fb916e445e35c240d-a65effec53139088.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T20:05:14Z" message: 'load-balancer-api-external: tcp connection to a00847e8c24b148fb916e445e35c240d-a65effec53139088.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.145442ms message: 'load-balancer-api-external: tcp connection to a00847e8c24b148fb916e445e35c240d-a65effec53139088.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:41:14Z" - latency: 8.23502ms message: 'load-balancer-api-external: resolved host name a00847e8c24b148fb916e445e35c240d-a65effec53139088.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T20:41:14Z" - latency: 4.721714ms message: 'load-balancer-api-external: tcp connection to a00847e8c24b148fb916e445e35c240d-a65effec53139088.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:40:14Z" - latency: 10.688822ms message: 'load-balancer-api-external: resolved host name a00847e8c24b148fb916e445e35c240d-a65effec53139088.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T20:40:14Z" - latency: 4.35779ms message: 'load-balancer-api-external: tcp connection to a00847e8c24b148fb916e445e35c240d-a65effec53139088.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:39:14Z" - latency: 6.87729ms message: 'load-balancer-api-external: resolved host name a00847e8c24b148fb916e445e35c240d-a65effec53139088.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T20:39:14Z" - latency: 4.506978ms message: 'load-balancer-api-external: tcp connection to a00847e8c24b148fb916e445e35c240d-a65effec53139088.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:38:14Z" - latency: 8.227968ms message: 'load-balancer-api-external: resolved host name a00847e8c24b148fb916e445e35c240d-a65effec53139088.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T20:38:14Z" - latency: 3.886077ms message: 'load-balancer-api-external: tcp connection to a00847e8c24b148fb916e445e35c240d-a65effec53139088.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:37:14Z" - latency: 7.372932ms message: 'load-balancer-api-external: resolved host name a00847e8c24b148fb916e445e35c240d-a65effec53139088.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T20:37:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T19:59:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-12-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-12.ec2.internal uid: e3c935fe-7f90-4441-a783-048816b4a6b0 resourceVersion: "61329" uid: 94191e75-1a65-4ca4-8d22-4371942e1828 spec: sourcePod: network-check-source-869dcfcdcd-j4t2j targetEndpoint: a00847e8c24b148fb916e445e35c240d-a65effec53139088.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T20:05:14Z" message: 'load-balancer-api-internal: tcp connection to a00847e8c24b148fb916e445e35c240d-a65effec53139088.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.341264ms message: 'load-balancer-api-internal: tcp connection to a00847e8c24b148fb916e445e35c240d-a65effec53139088.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:41:14Z" - latency: 8.202648ms message: 'load-balancer-api-internal: resolved host name a00847e8c24b148fb916e445e35c240d-a65effec53139088.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T20:41:14Z" - latency: 4.514749ms message: 'load-balancer-api-internal: tcp connection to a00847e8c24b148fb916e445e35c240d-a65effec53139088.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:40:14Z" - latency: 10.677442ms message: 'load-balancer-api-internal: resolved host name a00847e8c24b148fb916e445e35c240d-a65effec53139088.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T20:40:14Z" - latency: 4.621995ms message: 'load-balancer-api-internal: tcp connection to a00847e8c24b148fb916e445e35c240d-a65effec53139088.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:39:14Z" - latency: 6.855209ms message: 'load-balancer-api-internal: resolved host name a00847e8c24b148fb916e445e35c240d-a65effec53139088.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T20:39:14Z" - latency: 4.500875ms message: 'load-balancer-api-internal: tcp connection to a00847e8c24b148fb916e445e35c240d-a65effec53139088.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:38:14Z" - latency: 8.197055ms message: 'load-balancer-api-internal: resolved host name a00847e8c24b148fb916e445e35c240d-a65effec53139088.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T20:38:14Z" - latency: 4.639167ms message: 'load-balancer-api-internal: tcp connection to a00847e8c24b148fb916e445e35c240d-a65effec53139088.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:37:14Z" - latency: 7.232636ms message: 'load-balancer-api-internal: resolved host name a00847e8c24b148fb916e445e35c240d-a65effec53139088.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T20:37:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T19:59:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-12-to-network-check-target-ip-10-0-132-12 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-12.ec2.internal uid: e3c935fe-7f90-4441-a783-048816b4a6b0 resourceVersion: "61323" uid: 549e4e84-d9c3-4c1f-b6d4-ed68c4ec88a5 spec: sourcePod: network-check-source-869dcfcdcd-j4t2j targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T20:06:14Z" message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 923.144µs message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:41:14Z" - latency: 871.68µs message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:40:14Z" - latency: 1.527169ms message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:39:14Z" - latency: 1.021077ms message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:38:14Z" - latency: 1.436193ms message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:37:14Z" - latency: 1.039935ms message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:36:14Z" - latency: 1.02731ms message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:35:14Z" - latency: 985.628µs message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:34:14Z" - latency: 1.135936ms message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:33:14Z" - latency: 952.158µs message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:32:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T19:59:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-12-to-network-check-target-ip-10-0-135-197 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-12.ec2.internal uid: e3c935fe-7f90-4441-a783-048816b4a6b0 resourceVersion: "61324" uid: 7cb4297b-a488-48a1-ad85-8b1fe6a9e8cc spec: sourcePod: network-check-source-869dcfcdcd-j4t2j targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T20:06:14Z" message: 'network-check-target-ip-10-0-135-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.956274ms message: 'network-check-target-ip-10-0-135-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:41:14Z" - latency: 2.25838ms message: 'network-check-target-ip-10-0-135-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:40:14Z" - latency: 1.97409ms message: 'network-check-target-ip-10-0-135-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:39:14Z" - latency: 1.71932ms message: 'network-check-target-ip-10-0-135-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:38:14Z" - latency: 2.292625ms message: 'network-check-target-ip-10-0-135-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:37:14Z" - latency: 2.081799ms message: 'network-check-target-ip-10-0-135-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:36:14Z" - latency: 2.454859ms message: 'network-check-target-ip-10-0-135-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:35:14Z" - latency: 2.249356ms message: 'network-check-target-ip-10-0-135-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:34:14Z" - latency: 2.227845ms message: 'network-check-target-ip-10-0-135-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:33:14Z" - latency: 2.021237ms message: 'network-check-target-ip-10-0-135-197: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:32:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T19:59:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-12-to-network-check-target-ip-10-0-141-81 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-12.ec2.internal uid: e3c935fe-7f90-4441-a783-048816b4a6b0 resourceVersion: "61325" uid: 1e082220-5832-4e52-8a1c-b9a8ab24019a spec: sourcePod: network-check-source-869dcfcdcd-j4t2j targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T20:06:14Z" message: 'network-check-target-ip-10-0-141-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.30653ms message: 'network-check-target-ip-10-0-141-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:41:14Z" - latency: 2.413978ms message: 'network-check-target-ip-10-0-141-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:40:14Z" - latency: 2.56175ms message: 'network-check-target-ip-10-0-141-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:39:14Z" - latency: 2.055721ms message: 'network-check-target-ip-10-0-141-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:38:14Z" - latency: 2.513176ms message: 'network-check-target-ip-10-0-141-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:37:14Z" - latency: 2.403358ms message: 'network-check-target-ip-10-0-141-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:36:14Z" - latency: 2.606623ms message: 'network-check-target-ip-10-0-141-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:35:14Z" - latency: 2.588319ms message: 'network-check-target-ip-10-0-141-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:34:14Z" - latency: 2.605624ms message: 'network-check-target-ip-10-0-141-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:33:14Z" - latency: 2.368696ms message: 'network-check-target-ip-10-0-141-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:32:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T19:59:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-12-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-12.ec2.internal uid: e3c935fe-7f90-4441-a783-048816b4a6b0 resourceVersion: "61326" uid: 22f1876e-d1de-4688-b07a-da6d741816cd spec: sourcePod: network-check-source-869dcfcdcd-j4t2j targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-15T20:05:14Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 926.035µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:41:14Z" - latency: 2.856135ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T20:41:14Z" - latency: 829.06µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:40:14Z" - latency: 1.811031ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T20:40:14Z" - latency: 868.272µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:39:14Z" - latency: 1.667686ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T20:39:14Z" - latency: 822.418µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:38:14Z" - latency: 1.900875ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T20:38:14Z" - latency: 1.098738ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T20:37:14Z" - latency: 1.792851ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T20:37:14Z" kind: List metadata: resourceVersion: ""