apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T17:48:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-45-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-45.ec2.internal uid: 2f5d4fd2-45e3-42cf-bed5-3f6157394f5c resourceVersion: "34021" uid: 5ad122a7-027d-4131-aa24-ad3438b45f26 spec: sourcePod: network-check-source-7b678d77c7-dn2q5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T17:55:04Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.346607ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:09:04Z" - latency: 942.02µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:08:04Z" - latency: 829.441µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:07:04Z" - latency: 1.042105ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:06:04Z" - latency: 987.096µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:05:04Z" - latency: 1.290613ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:04:04Z" - latency: 1.229939ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:03:04Z" - latency: 1.125128ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:02:04Z" - latency: 1.172684ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:01:04Z" - latency: 1.199682ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:00:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T17:48:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-45-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-45.ec2.internal uid: 2f5d4fd2-45e3-42cf-bed5-3f6157394f5c resourceVersion: "36645" uid: 0893eebf-b2bb-44e5-9954-ca44d0a9c892 spec: sourcePod: network-check-source-7b678d77c7-dn2q5 targetEndpoint: afd63d871c5834e7cb914cacc85bcad6-cc8af45565b4d1e3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T17:54:04Z" message: 'load-balancer-api-external: tcp connection to afd63d871c5834e7cb914cacc85bcad6-cc8af45565b4d1e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 8.348268ms message: 'load-balancer-api-external: tcp connection to afd63d871c5834e7cb914cacc85bcad6-cc8af45565b4d1e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:12:04Z" - latency: 6.681234ms message: 'load-balancer-api-external: resolved host name afd63d871c5834e7cb914cacc85bcad6-cc8af45565b4d1e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:12:04Z" - latency: 5.384249ms message: 'load-balancer-api-external: tcp connection to afd63d871c5834e7cb914cacc85bcad6-cc8af45565b4d1e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:11:04Z" - latency: 6.10163ms message: 'load-balancer-api-external: resolved host name afd63d871c5834e7cb914cacc85bcad6-cc8af45565b4d1e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:11:04Z" - latency: 4.914528ms message: 'load-balancer-api-external: tcp connection to afd63d871c5834e7cb914cacc85bcad6-cc8af45565b4d1e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:10:04Z" - latency: 6.990762ms message: 'load-balancer-api-external: resolved host name afd63d871c5834e7cb914cacc85bcad6-cc8af45565b4d1e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:10:04Z" - latency: 5.36292ms message: 'load-balancer-api-external: tcp connection to afd63d871c5834e7cb914cacc85bcad6-cc8af45565b4d1e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:09:04Z" - latency: 7.467954ms message: 'load-balancer-api-external: resolved host name afd63d871c5834e7cb914cacc85bcad6-cc8af45565b4d1e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:09:04Z" - latency: 6.00691ms message: 'load-balancer-api-external: tcp connection to afd63d871c5834e7cb914cacc85bcad6-cc8af45565b4d1e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:08:04Z" - latency: 8.35329ms message: 'load-balancer-api-external: resolved host name afd63d871c5834e7cb914cacc85bcad6-cc8af45565b4d1e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:08:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T17:48:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-45-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-45.ec2.internal uid: 2f5d4fd2-45e3-42cf-bed5-3f6157394f5c resourceVersion: "36646" uid: d1f21952-ae78-4347-aa11-d7bee13a4d3b spec: sourcePod: network-check-source-7b678d77c7-dn2q5 targetEndpoint: afd63d871c5834e7cb914cacc85bcad6-cc8af45565b4d1e3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T17:54:04Z" message: 'load-balancer-api-internal: tcp connection to afd63d871c5834e7cb914cacc85bcad6-cc8af45565b4d1e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 8.330531ms message: 'load-balancer-api-internal: tcp connection to afd63d871c5834e7cb914cacc85bcad6-cc8af45565b4d1e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:12:04Z" - latency: 6.742615ms message: 'load-balancer-api-internal: resolved host name afd63d871c5834e7cb914cacc85bcad6-cc8af45565b4d1e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:12:04Z" - latency: 4.951213ms message: 'load-balancer-api-internal: tcp connection to afd63d871c5834e7cb914cacc85bcad6-cc8af45565b4d1e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:11:04Z" - latency: 6.051913ms message: 'load-balancer-api-internal: resolved host name afd63d871c5834e7cb914cacc85bcad6-cc8af45565b4d1e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:11:04Z" - latency: 4.432389ms message: 'load-balancer-api-internal: tcp connection to afd63d871c5834e7cb914cacc85bcad6-cc8af45565b4d1e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:10:04Z" - latency: 6.88474ms message: 'load-balancer-api-internal: resolved host name afd63d871c5834e7cb914cacc85bcad6-cc8af45565b4d1e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:10:04Z" - latency: 5.342333ms message: 'load-balancer-api-internal: tcp connection to afd63d871c5834e7cb914cacc85bcad6-cc8af45565b4d1e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:09:04Z" - latency: 7.491516ms message: 'load-balancer-api-internal: resolved host name afd63d871c5834e7cb914cacc85bcad6-cc8af45565b4d1e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:09:04Z" - latency: 5.103535ms message: 'load-balancer-api-internal: tcp connection to afd63d871c5834e7cb914cacc85bcad6-cc8af45565b4d1e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:08:04Z" - latency: 8.392218ms message: 'load-balancer-api-internal: resolved host name afd63d871c5834e7cb914cacc85bcad6-cc8af45565b4d1e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:08:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T17:48:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-45-to-network-check-target-ip-10-0-138-45 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-45.ec2.internal uid: 2f5d4fd2-45e3-42cf-bed5-3f6157394f5c resourceVersion: "34019" uid: 418fbadc-dd62-47b9-8994-180421e69bd9 spec: sourcePod: network-check-source-7b678d77c7-dn2q5 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T17:55:04Z" message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.330798ms message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:09:04Z" - latency: 893.756µs message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:08:04Z" - latency: 987.983µs message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:07:04Z" - latency: 815.56µs message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:06:04Z" - latency: 994.384µs message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:05:04Z" - latency: 989.9µs message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:04:04Z" - latency: 927.054µs message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:03:04Z" - latency: 1.011642ms message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:02:04Z" - latency: 996.17µs message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:01:04Z" - latency: 1.133946ms message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:00:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T17:48:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-45-to-network-check-target-ip-10-0-141-32 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-45.ec2.internal uid: 2f5d4fd2-45e3-42cf-bed5-3f6157394f5c resourceVersion: "34020" uid: 80b51cbf-f0e4-405b-bd89-2f19cdd724ae spec: sourcePod: network-check-source-7b678d77c7-dn2q5 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T17:55:04Z" message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.666264ms message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:09:04Z" - latency: 2.333295ms message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:08:04Z" - latency: 2.107149ms message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:07:04Z" - latency: 2.59274ms message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:06:04Z" - latency: 2.156498ms message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:05:04Z" - latency: 2.217411ms message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:04:04Z" - latency: 2.296579ms message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:03:04Z" - latency: 2.17604ms message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:02:04Z" - latency: 2.276131ms message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:01:04Z" - latency: 2.364506ms message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:00:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T17:48:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-45-to-network-check-target-ip-10-0-143-216 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-45.ec2.internal uid: 2f5d4fd2-45e3-42cf-bed5-3f6157394f5c resourceVersion: "34018" uid: 40a78e8e-2fec-4e2a-98c4-8e9e095b429e spec: sourcePod: network-check-source-7b678d77c7-dn2q5 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T17:55:04Z" message: 'network-check-target-ip-10-0-143-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.963157ms message: 'network-check-target-ip-10-0-143-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:09:04Z" - latency: 2.063448ms message: 'network-check-target-ip-10-0-143-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:08:04Z" - latency: 1.731797ms message: 'network-check-target-ip-10-0-143-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:07:04Z" - latency: 1.839795ms message: 'network-check-target-ip-10-0-143-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:06:04Z" - latency: 1.99463ms message: 'network-check-target-ip-10-0-143-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:05:04Z" - latency: 1.84507ms message: 'network-check-target-ip-10-0-143-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:04:04Z" - latency: 1.69506ms message: 'network-check-target-ip-10-0-143-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:03:04Z" - latency: 2.192482ms message: 'network-check-target-ip-10-0-143-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:02:04Z" - latency: 1.85496ms message: 'network-check-target-ip-10-0-143-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:01:04Z" - latency: 1.958028ms message: 'network-check-target-ip-10-0-143-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:00:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T17:48:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-45-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-45.ec2.internal uid: 2f5d4fd2-45e3-42cf-bed5-3f6157394f5c resourceVersion: "36644" uid: a97f8fb1-f81f-4539-b54f-e02690009bd1 spec: sourcePod: network-check-source-7b678d77c7-dn2q5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T17:54:04Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 879.703µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:12:04Z" - latency: 1.565452ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:12:04Z" - latency: 887.152µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:11:04Z" - latency: 1.595999ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:11:04Z" - latency: 849.946µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:10:04Z" - latency: 1.663314ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:10:04Z" - latency: 907.251µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:09:04Z" - latency: 2.363041ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:09:04Z" - latency: 1.103981ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:08:04Z" - latency: 2.090614ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:08:04Z" kind: List metadata: resourceVersion: ""